public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113551] [13 Regression] Miscompilation with -O1 -funswitch-loops -fno-strict-overflow
Date: Tue, 14 May 2024 13:56:05 +0000 [thread overview]
Message-ID: <bug-113551-4-dLeu4QxP0w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113551-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113551
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #20 from Mikael Pettersson <mikpelinux at gmail dot com> ---
For gcc-14 this test case was fixed by
dc48d1d1d4458773f89f21b2f019f66ddf88f2e5 is the first new commit
commit dc48d1d1d4458773f89f21b2f019f66ddf88f2e5
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Thu Aug 17 11:13:14 2023 -0400
Fix range-ops operator_addr.
Lack of symbolic information prevents op1_range from beig able to draw
the same conclusions as fold_range can.
PR tree-optimization/111009
gcc/
* range-op.cc (operator_addr_expr::op1_range): Be more restrictive.
That commit was backported to gcc-13 in
421311a31a12b96143eb901fde0e020771fe71d4, and that fixed this test case there
too.
Not sure if this is the proper fix or just makes the issue latent.
next prev parent reply other threads:[~2024-05-14 13:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 2:25 [Bug rtl-optimization/113551] New: " yshuiv7 at gmail dot com
2024-01-23 2:28 ` [Bug rtl-optimization/113551] " yshuiv7 at gmail dot com
2024-01-23 2:31 ` yshuiv7 at gmail dot com
2024-01-23 2:31 ` [Bug tree-optimization/113551] " pinskia at gcc dot gnu.org
2024-01-23 2:32 ` pinskia at gcc dot gnu.org
2024-01-23 4:29 ` [Bug tree-optimization/113551] [13/14 Regression] " pinskia at gcc dot gnu.org
2024-01-23 7:54 ` rguenth at gcc dot gnu.org
2024-01-23 8:03 ` [Bug tree-optimization/113551] [13 " rguenth at gcc dot gnu.org
2024-01-23 8:06 ` rguenth at gcc dot gnu.org
2024-01-23 23:23 ` [Bug tree-optimization/113551] [13 Regression] Miscompilation with -O1 -fno-strict-overflow yshuiv7 at gmail dot com
2024-01-23 23:24 ` yshuiv7 at gmail dot com
2024-01-23 23:28 ` yshuiv7 at gmail dot com
2024-01-23 23:34 ` yshuiv7 at gmail dot com
2024-01-23 23:40 ` pinskia at gcc dot gnu.org
2024-01-23 23:42 ` mpolacek at gcc dot gnu.org
2024-01-24 0:19 ` yshuiv7 at gmail dot com
2024-01-24 0:21 ` yshuiv7 at gmail dot com
2024-01-24 0:27 ` pinskia at gcc dot gnu.org
2024-01-24 0:39 ` yshuiv7 at gmail dot com
2024-01-24 8:17 ` [Bug tree-optimization/113551] [13 Regression] Miscompilation with -O1 -funswitch-loops -fno-strict-overflow rguenther at suse dot de
2024-05-14 13:56 ` mikpelinux at gmail dot com [this message]
2024-05-14 14:31 ` 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-113551-4-dLeu4QxP0w@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).