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 middle-end/102630] [12 Regression] Spurious -Warray-bounds with named address space
Date: Wed, 06 Oct 2021 17:01:32 +0000 [thread overview]
Message-ID: <bug-102630-4-lI9vHPV3uu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102630-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102630
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Blocks| |56456
Ever confirmed|0 |1
Keywords|rejects-valid |diagnostic
Last reconfirmed| |2021-10-06
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Thanks for filing this. It's been on my list of things to look into but it
helps to have a bug tracking it. For what it's worth, it hasn't been a
priority for me since I posted a simple patch to suppress the Glibc warning
(https://sourceware.org/pipermail/libc-alpha/2021-July/128829.html).
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
[Bug 56456] [meta-bug] bogus/missing -Warray-bounds
next prev parent reply other threads:[~2021-10-06 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 16:15 [Bug middle-end/102630] New: " jsm28 at gcc dot gnu.org
2021-10-06 17:01 ` msebor at gcc dot gnu.org [this message]
2021-10-06 17:18 ` [Bug middle-end/102630] " joseph at codesourcery dot com
2021-10-06 17:55 ` msebor at gcc dot gnu.org
2021-10-06 22:53 ` msebor at gcc dot gnu.org
2021-10-06 23:10 ` msebor at gcc dot gnu.org
2021-10-07 2:00 ` msebor at gcc dot gnu.org
2021-10-09 18:44 ` msebor at gcc dot gnu.org
2021-10-13 16:34 ` cvs-commit at gcc dot gnu.org
2021-10-13 17:09 ` 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-102630-4-lI9vHPV3uu@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).