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/107541] [13 Regression] wrong code at -O1, -O2 and -O3 on x86_64-linux-gnu
Date: Sun, 06 Nov 2022 18:30:26 +0000 [thread overview]
Message-ID: <bug-107541-4-deKTQVHjis@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107541-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107541
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-06
Ever confirmed|0 |1
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
ccp3 does:
Visiting statement:
# RANGE [irange] short int [1909, 1909][31001, 31001] NONZERO 0x7fff
_19 = (short intD.25) _18;
which is likely CONSTANT
Match-and-simplified (short int) _18 to 1909
Lattice value changed to CONSTANT 1909. Adding SSA edges to worklist.
marking stmt to be not simulated again
That is due to rhs side of the divisor being a constant ...
Someone else has to look into why it is one.
next prev parent reply other threads:[~2022-11-06 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 12:56 [Bug tree-optimization/107541] New: " zhendong.su at inf dot ethz.ch
2022-11-06 18:20 ` [Bug tree-optimization/107541] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-06 18:28 ` franckbehaghel_gcc at protonmail dot com
2022-11-06 18:30 ` pinskia at gcc dot gnu.org [this message]
2022-11-06 21:51 ` franckbehaghel_gcc at protonmail dot com
2022-11-07 7:03 ` rguenth at gcc dot gnu.org
2022-11-07 7:57 ` aldyh at gcc dot gnu.org
2022-11-07 9:18 ` aldyh at gcc dot gnu.org
2022-11-07 11:42 ` cvs-commit at gcc dot gnu.org
2022-11-07 11:43 ` aldyh 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-107541-4-deKTQVHjis@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).