On Tue, Jan 10, 2012 at 2:40 AM, Jakob Bornecrantz wrote:
> On Tue, Jan 10, 2012 at 12:01 AM, Alan Coopersmith
> wrote:
>> On 01/ 9/12 02:53 PM, Jakob Bornecrantz wrote:
>>>
>>> - struct pipe_shader_state pss = { 0 };
>>> + struct pipe_shader_state pss;
>>> + memset(&pss, 0, sizeof(pss));
>
On Tue, Jan 10, 2012 at 12:01 AM, Alan Coopersmith
wrote:
> On 01/ 9/12 02:53 PM, Jakob Bornecrantz wrote:
>>
>> - struct pipe_shader_state pss = { 0 };
>> + struct pipe_shader_state pss;
>> + memset(&pss, 0, sizeof(pss));
>
>
> Those do the same thing, just via a function call instead of co
On 01/ 9/12 02:53 PM, Jakob Bornecrantz wrote:
- struct pipe_shader_state pss = { 0 };
+ struct pipe_shader_state pss;
+ memset(&pss, 0, sizeof(pss));
Those do the same thing, just via a function call instead of compiler builtin.
What warning is being silenced by that change?
--
Signed-off-by: Jakob Bornecrantz
---
src/gallium/drivers/rbug/rbug_core.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/src/gallium/drivers/rbug/rbug_core.c
b/src/gallium/drivers/rbug/rbug_core.c
index b80bcd4..253d21b 100644
--- a/src/gallium/drivers/rbug/rbug_core.
