public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/16358] -Wno-system-headers hides warning caused by user header vs system header conflict [i.e. add -Wmacro-redefined]
Date: Wed, 27 Oct 2021 05:09:42 +0000 [thread overview]
Message-ID: <bug-16358-4-qVnIwDceEj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-16358-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16358
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
Summary|-Wno-system-headers hides |-Wno-system-headers hides
|warning caused by user |warning caused by user
|header vs system header |header vs system header
|conflict |conflict [i.e. add
| |-Wmacro-redefined]
--- Comment #12 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to niva from comment #11)
> (in reply to Martin Sebor in comment #10)
>
> Implementation of -Wmacro-redefined (with possibility of turning this
> warning to error) would solve the problem of our users.
Retitling accordingly
parent reply other threads:[~2021-10-27 5:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-16358-4@http.gcc.gnu.org/bugzilla/>]
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=bug-16358-4-qVnIwDceEj@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).