Re: [PATCH] Trace: initialize variable to clear warning

From: Zhengwang Ruan
Date: Wed Feb 29 2012 - 21:06:22 EST





-------- Original Message --------
From: Steven Rostedt
Sent: 2012年02月29日 星期三 20时09分18秒
To: Valdis.Kletnieks
Subject: Re: [PATCH] Trace: initialize variable to clear warning
> On Wed, 2012-02-29 at 17:40 -0500, Valdis.Kletnieks@xxxxxx wrote:
>> On Tue, 28 Feb 2012 09:16:31 EST, Steven Rostedt said:
>>
>>> This is a bug in gcc that's fixed in 4.6 and beyond. I don't want to
>>> remove this warning because it will hide a real bug if page2 really does
>>> become uninitialized. If 4.6 gives a warning here, then I'll fix it.
>>>> - void *page2;
>>>> + void *uninitialized_var(page2);
>> How would you feel about this?
>>
>> - void *page2;
>> + void *page2; /* gcc 4.5 bug causes incorrect "uninitialized" warning */
>>
>> or something similar?
> /* if you get a warning here, upgrade your gcc to 4.6 */
>

OK, I will resend this patch.

Thanks,
-Zhengwang

> -- Steve
>
>
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/