From 4ffa9f3635b6584d67076f506926f13d6cce4030 Mon Sep 17 00:00:00 2001 From: Kenneth Graunke Date: Thu, 17 Aug 2017 12:09:41 -0700 Subject: i965: Stop using wm_prog_data->binding_table.render_target_start. Render target surfaces always start at binding table index 0. This is required for us to use headerless FB writes, which we really want to do. So, we'll never change that. Given that, it's not necessary to look up a wm_prog_data field which we already know contains 0. We can drop the dependency in brw_renderbuffer_surfaces (Gen4-5)...which was already confusingly missing from gen6_renderbuffer_surfaces. Reviewed-by: Topi Pohjolainen --- src/intel/compiler/brw_fs_generator.cpp | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'src/intel/compiler/brw_fs_generator.cpp') diff --git a/src/intel/compiler/brw_fs_generator.cpp b/src/intel/compiler/brw_fs_generator.cpp index 2ade486705b..afaec5c9497 100644 --- a/src/intel/compiler/brw_fs_generator.cpp +++ b/src/intel/compiler/brw_fs_generator.cpp @@ -277,8 +277,13 @@ fs_generator::fire_fb_write(fs_inst *inst, else msg_control = BRW_DATAPORT_RENDER_TARGET_WRITE_SIMD8_SINGLE_SOURCE_SUBSPAN01; - uint32_t surf_index = - prog_data->binding_table.render_target_start + inst->target; + /* We assume render targets start at 0, because headerless FB write + * messages set "Render Target Index" to 0. Using a different binding + * table index would make it impossible to use headerless messages. + */ + assert(prog_data->binding_table.render_target_start == 0); + + const uint32_t surf_index = inst->target; bool last_render_target = inst->eot || (prog_data->dual_src_blend && dispatch_width == 16); -- cgit v1.2.3