i965: Switch ip_record to the non-zeroing allocator.
authorFrancisco Jerez <currojerez@riseup.net>
Fri, 20 Sep 2013 23:31:16 +0000 (16:31 -0700)
committerFrancisco Jerez <currojerez@riseup.net>
Wed, 2 Oct 2013 00:30:51 +0000 (17:30 -0700)
commita5d843ebdf771cb0a2ac46512679f19dd5550535
tree6cc8b09b440d79c653758a685a89b5b2cb169093
parentddd694293ad610f8ef80750d0f50e97d4909fb53
i965: Switch ip_record to the non-zeroing allocator.

All member variables of ip_record 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>
src/mesa/drivers/dri/i965/brw_fs.h