public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98512] [11 Regression] “#pragma GCC diagnostic ignored” ineffective in conjunction with alias attribute
Date: Tue, 05 Jan 2021 00:34:33 +0000 [thread overview]
Message-ID: <bug-98512-4-OIEfP9XvDE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98512-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |11.0
Status|UNCONFIRMED |NEW
Summary|“#pragma GCC diagnostic |[11 Regression] “#pragma
|ignored” ineffective in |GCC diagnostic ignored”
|conjunction with alias |ineffective in conjunction
|attribute |with alias attribute
Last reconfirmed| |2021-01-05
Ever confirmed|0 |1
Known to work| |10.2.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning looks for the location into which the memchr caller was inlined (to
see if the caller is defined in a system header but itself called from user
code). Without the alias it doesn't find one (because the caller isn't called
from anywhere) but with the alias it finds the memchr caller, __rawmemchr_ppc.
next prev parent reply other threads:[~2021-01-05 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 13:47 [Bug tree-optimization/98512] New: " fw at gcc dot gnu.org
2021-01-05 0:34 ` msebor at gcc dot gnu.org [this message]
2021-01-05 0:35 ` [Bug tree-optimization/98512] [11 Regression] " msebor at gcc dot gnu.org
2021-01-05 11:20 ` rguenth at gcc dot gnu.org
2021-01-18 23:54 ` msebor at gcc dot gnu.org
2021-01-19 19:02 ` msebor at gcc dot gnu.org
2021-01-25 19:44 ` fw at gcc dot gnu.org
2021-02-19 23:42 ` msebor at gcc dot gnu.org
2021-05-27 13:55 ` [Bug tree-optimization/98512] [11/12 " marxin at gcc dot gnu.org
2021-05-27 14:01 ` fw at gcc dot gnu.org
2021-05-27 14:08 ` marxin at gcc dot gnu.org
2021-06-10 23:31 ` msebor at gcc dot gnu.org
2021-07-02 22:20 ` cvs-commit at gcc dot gnu.org
2021-07-06 19:43 ` cvs-commit at gcc dot gnu.org
2021-11-12 19:45 ` msebor 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-98512-4-OIEfP9XvDE@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).