public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106842] [12 Regression] misleading warning : iteration X invokes undefined behavior
Date: Tue, 06 Sep 2022 04:58:28 +0000	[thread overview]
Message-ID: <bug-106842-4-0bSSb0DebC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106842-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> Fixed on master with r13-2076-g9594e04e4e2abeb4, started with
> r12-5183-ga7753db4a7c071fe.

Would make sense really but that might mean a latent bug in the code in pre for
the comparing of duplicated bbs when the only difference is decl uids too

  parent reply	other threads:[~2022-09-06  4:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 21:43 [Bug c/106842] New: " franckbehaghel_gcc at protonmail dot com
2022-09-05 22:12 ` [Bug tree-optimization/106842] [12 Regression] " pinskia at gcc dot gnu.org
2022-09-05 22:20 ` pinskia at gcc dot gnu.org
2022-09-06  4:51 ` marxin at gcc dot gnu.org
2022-09-06  4:58 ` pinskia at gcc dot gnu.org [this message]
2022-09-06  8:35 ` rguenth at gcc dot gnu.org
2022-09-06  8:36 ` [Bug tree-optimization/106842] [12/13 " rguenth at gcc dot gnu.org
2022-12-20 15:23 ` rguenth at gcc dot gnu.org
2023-05-08 12:25 ` [Bug tree-optimization/106842] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-15  0:50 ` [Bug tree-optimization/106842] [12 " law 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-106842-4-0bSSb0DebC@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).