Re: cc1.exe: warnings being treated as errors

[Jon Grant <jg at jguk dot org>]

Hi Jonathan

Jonathan Wakely wrote, On 24/09/11 15:55:
> On 24 September 2011 15:40, Jon Grant wrote:
> > It's kind of re-iterating the command line options, that the user will
> > choose to be aware of already. I don't recall seeing that text output before
> > about ~1 year ago.
>
> It was there in GCC 4.1, maybe earlier, I didn't check.

However, coming back to my query: Is there a need to remind the user 
that warnings on the build are being treated as errors? Is this a 
special case because it would cause the build to stop?

For example: -Wall means I see "control reaches end of non-void 
function" messages, but doesn't output "cc1.exe: all warnings turned on"

> > I'd thought because the previous line of output said "gcc -Werror -Wall -o
> > main main.c", the options clear.
>
> Not if you run "make" and it doesn't echo the compiler command, or run
> the compiler from an IDE, or anything else which shows the errors but
> not the command.

I would have though that it's not GCC's responsibility to echo the 
options passed to it. Like the IDE example, the IDE can inform the user 
of what compiler options are in use; I don't see why GCC can't keep 
quiet about -Werror.

Best regards, Jon