[lldb-dev] (no subject)
tfiala at google.com
Sat Apr 5 12:22:23 PDT 2014
I suspect one way to handle is to disable on gcc and just expect the clang
builds to catch the real issues in that case.
On Saturday, April 5, 2014, Todd Fiala <tfiala at google.com> wrote:
> I think the issue there is that sometimes the warning is appropriate.
>> On Sat, Apr 05, 2014 at 11:04:46AM -0700, Saleem Abdulrasool wrote:
>> > On Wed, Mar 26, 2014 at 12:40 PM, Todd Fiala <tfiala at google.com> wrote:
>> > > I'm not against it.
>> > >
>> > > Locally I've occasionally done the static_cast<void*> (something_p)
>> > > that shuts up the gcc %p warning. (And in the process have found
>> > > interesting things like enum cases being ignored, etc.).
>> > >
>> > > One negative of all that IMHO is that it adds clutter, but if it
>> helps us
>> > > find real warnings, my vote would be to do it.
>> > >
>> > Just an FYI in case people missed it, I pushed the change to quiet up
>> > warning. There are still a few other warnings that are floating around,
>> > but, it is a much more happy build now.
>> I don't think this is the correct approach, the warning should just be
>> disabled for GCC as lame...
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
> | 650-943-3180
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev