public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/7029: preprocessor should ignore #warning with -M Date: Mon, 01 Jul 2002 14:36:00 -0000 [thread overview] Message-ID: <20020701213607.19116.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/7029; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.co.uk> Cc: wolfgang.bangerth@iwr.uni-heidelberg.de, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: preprocessor/7029: preprocessor should ignore #warning with -M Date: Mon, 1 Jul 2002 14:33:20 -0700 On Mon, Jul 01, 2002 at 10:20:29PM +0100, Neil Booth wrote: > Zack Weinberg wrote:- > > > > Warnings are sent to stderr and the dpendency information isn't; so if > > > you don't want the warnings you are free to pipe stderr to /dev/null. > > > If you still wanted to retain errors but not warnings you can use -w, > > > or check the compiler return code. > > > > > > So I disagree that there is any reason to change the existing behaviour, > > > and want to close this PR. Do you agree, Zack? > > > > Well, I think it might be reasonable for -M switches that inhibit > > compilation to imply -w. Presumably the user will get all the > > warnings in due course as part of the real compilation. > > Fair enough; I'll create a patch. Thanks. zw
next reply other threads:[~2002-07-01 21:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-01 14:36 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-02 15:35 neil 2002-07-01 22:56 Neil Booth 2002-07-01 15:56 Zack Weinberg 2002-07-01 14:56 Neil Booth 2002-07-01 14:26 Zack Weinberg 2002-07-01 14:26 Neil Booth 2002-07-01 14:16 Neil Booth 2002-06-14 6:06 wolfgang.bangerth
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=20020701213607.19116.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).