summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancisco Jerez <currojerez@riseup.net>2013-09-20 16:37:55 -0700
committerFrancisco Jerez <currojerez@riseup.net>2013-10-01 17:30:52 -0700
commit23e8673afb56f10f8301fa86e4c2cdfd864eaaf7 (patch)
tree833d250085acaa8f744fb842a374f2587d6a8653
parentc307d27c5e83c45d572b593de3497892c24dc178 (diff)
downloadexternal_mesa3d-23e8673afb56f10f8301fa86e4c2cdfd864eaaf7.zip
external_mesa3d-23e8673afb56f10f8301fa86e4c2cdfd864eaaf7.tar.gz
external_mesa3d-23e8673afb56f10f8301fa86e4c2cdfd864eaaf7.tar.bz2
i965: Switch vec4_live_variables to the non-zeroing allocator.
All member variables of vec4_live_variables are already being initialized from its constructor, it's not necessary to use rzalloc to allocate its memory, and doing so makes it more likely that we will start relying on the allocator to zero out all memory if the class is ever extended with new member variables. That's bad because it ties objects to some specific allocation scheme, and gives unpredictable results when an object is created with a different allocator -- Stack allocation, array allocation, or aggregation inside a different object are some of the useful possibilities that come to my mind. Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
-rw-r--r--src/mesa/drivers/dri/i965/brw_vec4_live_variables.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mesa/drivers/dri/i965/brw_vec4_live_variables.h b/src/mesa/drivers/dri/i965/brw_vec4_live_variables.h
index b8ab95a..296468a 100644
--- a/src/mesa/drivers/dri/i965/brw_vec4_live_variables.h
+++ b/src/mesa/drivers/dri/i965/brw_vec4_live_variables.h
@@ -52,7 +52,7 @@ struct block_data {
class vec4_live_variables {
public:
- DECLARE_RZALLOC_CXX_OPERATORS(vec4_live_variables)
+ DECLARE_RALLOC_CXX_OPERATORS(vec4_live_variables)
vec4_live_variables(vec4_visitor *v, cfg_t *cfg);
~vec4_live_variables();