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 bootstrap/101379] libatomic arm build failure after r12-2132 due -Warray-bounds on a constant address
Date: Wed, 21 Jul 2021 16:55:01 +0000 [thread overview]
Message-ID: <bug-101379-4-LbOpFVnA6E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101379-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101379
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch committed in r12-2438.
prev parent reply other threads:[~2021-07-21 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:34 [Bug tree-optimization/101379] New: libatomic build failure on arm after r12-2132 clyon at gcc dot gnu.org
2021-07-08 14:47 ` [Bug tree-optimization/101379] " schwab@linux-m68k.org
2021-07-08 19:06 ` msebor at gcc dot gnu.org
2021-07-08 22:40 ` msebor at gcc dot gnu.org
2021-07-09 7:07 ` [Bug bootstrap/101379] libatomic arm build failure after r12-2132 due -Warray-bounds on a constant address rguenth at gcc dot gnu.org
2021-07-09 13:46 ` clyon at gcc dot gnu.org
2021-07-09 17:11 ` msebor at gcc dot gnu.org
2021-07-09 21:23 ` clyon at gcc dot gnu.org
2021-07-09 23:12 ` msebor at gcc dot gnu.org
2021-07-21 15:55 ` msebor at gcc dot gnu.org
2021-07-21 16:52 ` cvs-commit at gcc dot gnu.org
2021-07-21 16:55 ` msebor 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-101379-4-LbOpFVnA6E@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).