[LLVMdev] Build Failure
Caldarale, Charles R
Chuck.Caldarale at unisys.com
Wed Jan 2 22:19:14 PST 2013
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of greened at obbligato.org
> Subject: Re: [LLVMdev] Build Failure
> It seems a better option than simply ignoring warnings and then missing
> a real bug in the haystack of warning messages.
Definitely agree with that. Our project coding standards require _zero_ warnings at commit time (but that only applies to our code, not imported libraries).
> I've committed fixes to lots of -Wuninitialized warnings in my tree.
> It's all just initializing local variables, which shouldn't result in
> extra stores.
What do you think the initialization is? Something has to write the initial value, and that write is frequently pointless.
The real problem with this specific warning is that gcc doesn't properly track that a variable is used only under the same conditions in which it is set.
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
More information about the llvm-dev