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 ipa/114290] [11/12/13/14 regression] GCC output incorrect output with -O2 since r9-7460-g9f2cfe108f75de
Date: Sat, 09 Mar 2024 21:04:54 +0000 [thread overview]
Message-ID: <bug-114290-4-ija8j3zm3h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114290-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114290
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Yes this is a dup of bug 113907.
What is happening is fnsplit happens and splits off from both f and g:
return {A / B + (A % B != 0)};
and
return {C / D + (C % D != 0)};
into a new 2 functions and the range information is still there for A/B (C/D).
Which is fine.
And then ICF comes along and sees this 2 new functions are the same (which they
are) but since the range information is there still from one version of the
function (which in this case the bad one), the wrong result happens.
This is all described in PR 113907 too.
*** This bug has been marked as a duplicate of bug 113907 ***
prev parent reply other threads:[~2024-03-09 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 9:52 [Bug c++/114290] New: GCC output incorrect output with -O2 jlame646 at gmail dot com
2024-03-09 18:34 ` [Bug ipa/114290] " i at rvalue dot moe
2024-03-09 18:39 ` [Bug ipa/114290] [11/12/13/14 regression] GCC output incorrect output with -O2 since r9-7460-g9f2cfe108f75de sjames at gcc dot gnu.org
2024-03-09 18:41 ` sjames at gcc dot gnu.org
2024-03-09 20:53 ` pinskia at gcc dot gnu.org
2024-03-09 21:04 ` pinskia at gcc dot gnu.org [this message]
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-114290-4-ija8j3zm3h@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).