From 23e8673afb56f10f8301fa86e4c2cdfd864eaaf7 Mon Sep 17 00:00:00 2001 From: Francisco Jerez Date: Fri, 20 Sep 2013 16:37:55 -0700 Subject: [PATCH] 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 --- src/mesa/drivers/dri/i965/brw_vec4_live_variables.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 b8ab95a1d99..296468a2d34 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(); -- 2.30.2