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/56456] [meta-bug] bogus/missing -Warray-bounds
Date: Tue, 20 Jul 2021 14:38:07 +0000 [thread overview]
Message-ID: <bug-56456-4-O0TEmUhPCl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56456-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 93437, which changed state.
Bug 93437 Summary: [9 Regression] bogus -Warray-bounds on protobuf generated code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93437
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2021-07-20 14:38 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 9:48 [Bug tree-optimization/56456] New: [meta-bug] bogus warning when inlining: "array subscript is above array bounds" amylaar at gcc dot gnu.org
2013-02-26 10:18 ` [Bug tree-optimization/56456] " rguenth at gcc dot gnu.org
2014-06-12 13:07 ` [Bug tree-optimization/56456] [meta-bug] bogus warning when inlining or unrolling: " rguenth at gcc dot gnu.org
2015-02-24 14:05 ` rguenth at gcc dot gnu.org
2019-03-18 23:49 ` [Bug tree-optimization/56456] [meta-bug] bogus/missing -Warray-bounds msebor at gcc dot gnu.org
2020-04-13 20:27 ` msebor at gcc dot gnu.org
2020-04-18 18:22 ` law at redhat dot com
2020-04-21 17:15 ` msebor at gcc dot gnu.org
2020-05-18 22:06 ` msebor at gcc dot gnu.org
2020-05-19 21:07 ` msebor at gcc dot gnu.org
2020-06-01 17:14 ` msebor at gcc dot gnu.org
2020-06-10 17:41 ` msebor at gcc dot gnu.org
2020-07-21 20:08 ` msebor at gcc dot gnu.org
2020-07-21 21:31 ` msebor at gcc dot gnu.org
2020-07-27 20:09 ` msebor at gcc dot gnu.org
2020-08-20 17:14 ` msebor at gcc dot gnu.org
2020-08-20 17:27 ` msebor at gcc dot gnu.org
2020-09-20 0:09 ` msebor at gcc dot gnu.org
2020-09-27 20:25 ` msebor at gcc dot gnu.org
2020-10-14 21:38 ` msebor at gcc dot gnu.org
2020-11-29 22:35 ` msebor at gcc dot gnu.org
2021-01-04 16:06 ` msebor at gcc dot gnu.org
2021-01-04 16:20 ` w at 1wt dot eu
2021-01-04 17:41 ` msebor at gcc dot gnu.org
2021-01-04 22:43 ` w at 1wt dot eu
2021-01-06 11:15 ` ebotcazou at gcc dot gnu.org
2021-01-14 20:11 ` msebor at gcc dot gnu.org
2021-02-10 21:36 ` msebor at gcc dot gnu.org
2021-03-08 20:39 ` msebor at gcc dot gnu.org
2021-05-05 19:31 ` msebor at gcc dot gnu.org
2021-05-14 11:16 ` jakub at gcc dot gnu.org
2021-05-14 11:38 ` jakub at gcc dot gnu.org
2021-07-06 21:32 ` msebor at gcc dot gnu.org
2021-07-08 22:12 ` msebor at gcc dot gnu.org
2021-07-08 22:42 ` msebor at gcc dot gnu.org
2021-07-13 17:02 ` msebor at gcc dot gnu.org
2021-07-20 14:38 ` msebor at gcc dot gnu.org [this message]
2021-08-24 16:50 ` msebor at gcc dot gnu.org
2021-08-24 16:50 ` msebor at gcc dot gnu.org
2021-09-01 15:02 ` msebor at gcc dot gnu.org
2021-09-15 20:16 ` msebor at gcc dot gnu.org
2021-10-13 17:09 ` msebor at gcc dot gnu.org
2021-10-26 23:02 ` msebor at gcc dot gnu.org
2021-11-23 10:01 ` pinskia at gcc dot gnu.org
2021-12-09 19:59 ` msebor at gcc dot gnu.org
2021-12-15 16:23 ` msebor at gcc dot gnu.org
2021-12-15 17:27 ` msebor at gcc dot gnu.org
2022-01-19 8:55 ` rguenth at gcc dot gnu.org
2022-01-26 17:52 ` msebor at gcc dot gnu.org
2022-02-01 12:54 ` marxin at gcc dot gnu.org
2022-02-16 17:25 ` msebor at gcc dot gnu.org
2022-03-17 20:02 ` msebor at gcc dot gnu.org
2022-03-23 8:31 ` rguenth at gcc dot gnu.org
2022-03-30 8:16 ` jakub at gcc dot gnu.org
2022-04-21 12:36 ` redi at gcc dot gnu.org
2022-05-27 8:15 ` rguenth at gcc dot gnu.org
2022-05-27 8:33 ` rguenth at gcc dot gnu.org
2022-05-31 14:42 ` msebor at gcc dot gnu.org
2022-06-15 9:50 ` rguenth at gcc dot gnu.org
2022-09-12 7:57 ` rguenth at gcc dot gnu.org
2022-09-13 16:48 ` pinskia at gcc dot gnu.org
2022-12-16 14:14 ` marxin at gcc dot gnu.org
2022-12-19 21:38 ` pinskia at gcc dot gnu.org
2022-12-20 14:06 ` rguenth at gcc dot gnu.org
2022-12-24 20:14 ` pinskia at gcc dot gnu.org
2022-12-24 20:35 ` jhaberman at gmail dot com
2022-12-24 20:46 ` pinskia at gcc dot gnu.org
2023-01-27 14:39 ` amacleod at redhat dot com
2023-01-27 15:16 ` rguenth at gcc dot gnu.org
2023-01-30 21:12 ` amacleod at redhat dot com
2023-02-13 9:02 ` rguenth at gcc dot gnu.org
2023-03-09 18:29 ` pinskia at gcc dot gnu.org
2023-04-27 11:45 ` rguenth at gcc dot gnu.org
2023-05-17 15:05 ` pinskia at gcc dot gnu.org
2023-07-07 8:45 ` rguenth at gcc dot gnu.org
2023-07-07 9:25 ` rguenth at gcc dot gnu.org
2023-08-09 18:53 ` gjl at gcc dot gnu.org
2024-01-19 4:34 ` sandra at gcc dot gnu.org
2024-01-20 19:49 ` pinskia 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-56456-4-O0TEmUhPCl@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).