[cfe-commits] [PATCH] Fix analysis based warnings so that all warnings are emitted with -Werror.

Delesley Hutchins delesley at google.com
Wed Dec 5 08:12:24 PST 2012


I'm happy with uncompilable.  It's not quite accurate; there are some
errors that are technically compilable, but treated as errors for
other reasons, but it captures the spirit of what I'm trying to do,
and I don't have a better name.  Anybody else want to weigh in?

  -DeLesley

On Tue, Dec 4, 2012 at 8:21 PM, Richard Smith <richard at metafoo.co.uk> wrote:
> On Tue, Dec 4, 2012 at 8:02 PM, Delesley Hutchins <delesley at google.com>
> wrote:
>>
>> This patch fixes analysis based warnings so that all warnings are
>> emitted when compiling with -Werror.  Previously, compiling with
>> -Werror would emit only the first warning in a compilation unit,
>> because clang assumes that once an error occurs, further analysis is
>> unlikely to return valid results.  However, warnings that have been
>> upgraded to errors should not be treated as "errors" in this sense.
>
>
> This makes sense to me, but I wonder if there's a better term than
> "TrueError". We've just spent a couple of minutes throwing around adjectives
> and the best we found was "UncompilableError" (an error which means we can't
> compile the program because we didn't understand all the code). It would
> seem reasonable to classify errors with warning flags as 'compilable'
> errors, in addition to the -Werror'd warnings.



-- 
DeLesley Hutchins | Software Engineer | delesley at google.com | 505-206-0315



More information about the cfe-commits mailing list