public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111249] [12/13 Regression] Aggressive loop optimization reports "iteration 2147483645 invokes undefined behavior"
Date: Wed, 25 Oct 2023 06:51:42 +0000 [thread overview]
Message-ID: <bug-111249-4-DAkR9o8fQv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111249-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111249
--- Comment #3 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Sam James from comment #2)
> Bisecting from 11 (good) -> 12 (bad) gave r12-4871-g502ffb1f389011 as the
> breaking commit.
>
> Bisecting from 13 (bad) -> 14 (good) gave r14-2926-gee20be8325f7f2 as the
> fix commit.
sorry I mean r14-2927-g399c8dd44ff44f for the last one
next prev parent reply other threads:[~2023-10-25 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 22:04 [Bug c/111249] New: " jonathan.leffler at gmail dot com
2023-08-31 10:55 ` [Bug tree-optimization/111249] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-10-25 6:51 ` sjames at gcc dot gnu.org
2023-10-25 6:51 ` sjames at gcc dot gnu.org [this message]
2024-05-13 11:31 ` rguenth at gcc dot gnu.org
2024-06-20 9:13 ` 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-111249-4-DAkR9o8fQv@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).