public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lhyatt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/100125] -Wunused-macros generated while should be ignored; if undef is seen? Date: Wed, 29 Jun 2022 16:08:16 +0000 [thread overview] Message-ID: <bug-100125-4-uYqNY1zyQ5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100125-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100125 Lewis Hyatt <lhyatt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lhyatt at gcc dot gnu.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Lewis Hyatt <lhyatt at gcc dot gnu.org> --- The reason it works without #undef is that cpp_finish() is called late by the C++ frontend, after it has processed everything including pragmas. With #undef, the warning is generated immediately by libcpp and so is subject to PR53431. There is a patch waiting for review that will resolve it. *** This bug has been marked as a duplicate of bug 53431 ***
prev parent reply other threads:[~2022-06-29 16:08 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 20:30 [Bug preprocessor/100125] New: " gcc at behdad dot org 2022-06-29 16:08 ` lhyatt at gcc dot gnu.org [this message]
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-100125-4-uYqNY1zyQ5@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: 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).