public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sirl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110458] [14 Regression] -Warray-bounds=2 new false positive
Date: Wed, 09 Aug 2023 09:21:16 +0000	[thread overview]
Message-ID: <bug-110458-4-YwteNU8U6u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110458-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110458

--- Comment #3 from Franz Sirl <sirl at gcc dot gnu.org> ---
Actually Comment 2 is only true for the original testcode (which was quite
fragile to reproduce). The reduced testcode started to fail with the backwards
jump threader rewrite in r12-2591-g2e96b5f14e4025691b57d2301d71aa6092ed44bc and
a simple -Warray-bounds. This is proven by the fact that compiling the testcase
with gcc@r12-2591 with an additional --param=threader-mode=legacy makes the
warning go away.

So this bug maybe a duplicate of the other bugs (couldn't find a metabug)
related to r12-2591.

  parent reply	other threads:[~2023-08-09  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 15:09 [Bug c/110458] New: " sirl at gcc dot gnu.org
2023-06-28 19:21 ` [Bug tree-optimization/110458] " pinskia at gcc dot gnu.org
2023-06-29 10:13 ` sirl at gcc dot gnu.org
2023-06-29 15:54 ` [Bug tree-optimization/110458] [14 Regression] " pinskia at gcc dot gnu.org
2023-08-09  9:21 ` sirl at gcc dot gnu.org [this message]
2024-03-08 15:29 ` law at gcc dot gnu.org
2024-05-07  7:40 ` [Bug tree-optimization/110458] [14/15 " rguenth 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-110458-4-YwteNU8U6u@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).