On Fri, Apr 27, 2012 at 10:46 AM, Arthur O'Dwyer <arthur at push.am> wrote:
> Joerg Sonnenberger <joerg at britannica.bec.de> wrote:
>> It's a bug if a warning does not have a corresponding
>> option to disable it. So what warning are you talking about?
>> Then clang is full of bugs that I assume must be trivial to grep for. ;)
Even easier than greping - we have a list of unnamed warnings & a tool
that checks that we don't ever increase/add things to this list (& if
we ever remove things from it, they stay removed). It's just not an
immediate priority for someone to spend the time to group & name all
these warnings appropriately.
Patches welcome? :) preferably if they're named the same as GCC's
diagnostics, if any match already. (or, if GCC's name is particularly
bad or at odds with Clang's naming conventions, an alias for GCC's
name & another name that matches Clang's can be provided)
- David
> When I feed my example autogenerated code to clang 3.1
> (tags/Apple/clang-318.0.58), I get this output:
>> x.m:2:1: warning: no 'assign', 'retain', or 'copy' attribute is
> specified - 'assign' is assumed
> @property Foo *foo;
> ^
> x.m:2:1: warning: default property attribute 'assign' not appropriate
> for non-gc object
> x.m:4:18: warning: division by zero is undefined
> void f(int x) { x/=0; }
> ^ ~
>> That's three distinct warnings with no options to toggle any of them.
> Unless ToT has addressed these warnings already.
>> -Arthur
> _______________________________________________
> cfe-dev mailing list
>cfe-dev at cs.uiuc.edu>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev