From: Jon Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: cc1.exe: warnings being treated as errors
Date: Mon, 26 Sep 2011 09:08:00 -0000 [thread overview]
Message-ID: <4E8038F6.7060709@jguk.org> (raw)
In-Reply-To: <CAH6eHdQ4djx0B+BZFJuBTS-88fNAWth3Dya8TGVrr4R-zt9VHQ@mail.gmail.com>
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
next prev parent reply other threads:[~2011-09-26 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 18:00 Jon Grant
2011-09-19 18:41 ` Jonathan Wakely
2011-09-24 14:40 ` Jon Grant
2011-09-24 14:55 ` Jonathan Wakely
2011-09-24 15:24 ` Jakub Jelinek
2011-09-26 9:08 ` Jon Grant [this message]
2011-09-26 9:30 ` Jonathan Wakely
2011-10-06 23:46 ` Jon Grant
2011-09-26 10:54 ` Andrew Haley
2011-09-26 16:26 ` Ian Lance Taylor
2011-09-26 16:57 ` Andrew Haley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E8038F6.7060709@jguk.org \
--to=jg@jguk.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).