public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lhyatt at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/97498] #pragma GCC diagnostic ignored "-Wunused-function" inconsistent
Date: Sun, 17 Jul 2022 15:12:23 +0000 [thread overview]
Message-ID: <bug-97498-4-22EqdjaCtz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97498-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97498
Lewis Hyatt <lhyatt at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lhyatt at gmail dot com
--- Comment #8 from Lewis Hyatt <lhyatt at gmail dot com> ---
(In reply to Martin Liška from comment #7)
> We actually speak about 2 modified lines, so can we backport it, please?
It will work fine for any of 10, 11, 12. I'll ask for approval for that on
gcc-patches then.
next prev parent reply other threads:[~2022-07-17 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 23:49 [Bug preprocessor/97498] New: " matthewp515 at gmail dot com
2022-07-07 14:00 ` [Bug preprocessor/97498] " lhyatt at gcc dot gnu.org
2022-07-09 20:53 ` lhyatt at gcc dot gnu.org
2022-07-10 20:50 ` cvs-commit at gcc dot gnu.org
2022-07-10 20:51 ` lhyatt at gcc dot gnu.org
2022-07-12 9:47 ` marxin at gcc dot gnu.org
2022-07-12 9:48 ` marxin at gcc dot gnu.org
2022-07-12 9:55 ` marxin at gcc dot gnu.org
2022-07-17 15:12 ` lhyatt at gmail dot com [this message]
2022-08-01 23:15 ` cvs-commit at gcc dot gnu.org
2022-08-02 22:25 ` cvs-commit at gcc dot gnu.org
2022-08-02 22:26 ` cvs-commit at gcc dot gnu.org
2022-10-19 20:51 ` lhyatt at gcc dot gnu.org
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-97498-4-22EqdjaCtz@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).