diff options
author | Kenneth Graunke <[email protected]> | 2018-01-02 23:59:06 -0800 |
---|---|---|
committer | Kenneth Graunke <[email protected]> | 2018-01-22 10:03:52 -0800 |
commit | 60f15477dad1fa752a91ecf1c2bf0aabbccbf2e5 (patch) | |
tree | a4de71da29d707b9cab1bf0f6f7556f314e8bca5 /src/mesa | |
parent | a9bb067e27cd1d249cede580c50e7e2fc1eef372 (diff) |
i965: Drop render_target_start from binding table struct.
We have to start render targets at binding table index 0 in order to use
headerless FB write messages, and in fact already assume this in a bunch
of places in the code. Let's finish that off, and not bother storing 0
in a struct to pretend to add it in a few places.
Reviewed-by: Iago Toral Quiroga <[email protected]>
Diffstat (limited to 'src/mesa')
-rw-r--r-- | src/mesa/drivers/dri/i965/brw_wm.c | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/src/mesa/drivers/dri/i965/brw_wm.c b/src/mesa/drivers/dri/i965/brw_wm.c index 942fb04a804..0072bdd0fb4 100644 --- a/src/mesa/drivers/dri/i965/brw_wm.c +++ b/src/mesa/drivers/dri/i965/brw_wm.c @@ -46,13 +46,11 @@ assign_fs_binding_table_offsets(const struct gen_device_info *devinfo, const struct brw_wm_prog_key *key, struct brw_wm_prog_data *prog_data) { - uint32_t next_binding_table_offset = 0; - - /* If there are no color regions, we still perform an FB write to a null - * renderbuffer, which we place at surface index 0. + /* Render targets implicitly start at surface index 0. Even if there are + * no color regions, we still perform an FB write to a null render target, + * which will be surface 0. */ - prog_data->binding_table.render_target_start = next_binding_table_offset; - next_binding_table_offset += MAX2(key->nr_color_regions, 1); + uint32_t next_binding_table_offset = MAX2(key->nr_color_regions, 1); next_binding_table_offset = brw_assign_common_binding_table_offsets(devinfo, prog, &prog_data->base, |