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/60014] Bad warning suppression caused by track-macro-expansion when not using integrated cpp Date: Wed, 12 Oct 2022 22:17:53 +0000 [thread overview] Message-ID: <bug-60014-4-VfHG8cRWQH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60014-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60014 Lewis Hyatt <lhyatt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Lewis Hyatt <lhyatt at gcc dot gnu.org> --- The underlying issue is fixed for GCC 13 now.
prev parent reply other threads:[~2022-10-12 22:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-31 21:27 [Bug c/60014] New: Bad warning suppression megahallon at gmail dot com 2014-06-10 6:30 ` [Bug preprocessor/60014] Bad warning suppression caused by track-macro-expansion when not using integrated cpp peff at peff dot net 2014-06-10 10:24 ` manu at gcc dot gnu.org 2015-04-28 19:47 ` megahallon at gmail dot com 2022-10-06 21:51 ` lhyatt at gcc dot gnu.org 2022-10-12 22:16 ` cvs-commit at gcc dot gnu.org 2022-10-12 22:17 ` 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-60014-4-VfHG8cRWQH@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).