public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108639] ]13 Regression] ICE on valid code at -O1 and above: in decompose, at wide-int.h:984 since r13-5578 Date: Thu, 02 Feb 2023 15:11:04 +0000 [thread overview] Message-ID: <bug-108639-4-RKbMJ3bb1A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108639-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108639 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amacleod at redhat dot com --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The problem is in 271 if (relation_equiv_p (rel) && lh == rh) We see # RANGE [irange] int [0, 1] NONZERO 0x1 # iftmp.0_6 = PHI <_10(3), 0(2)> # RANGE [irange] long int [0, 1] NONZERO 0x1 _3 = (long int) iftmp.0_6; # RANGE [irange] unsigned int [0, 1] NONZERO 0x1 _4 = (unsigned int) iftmp.0_6; # RANGE [irange] long int [-INF, +INF] NONZERO 0x3 _5 = _3 << _4; so lhs and rhs indeed have the same range, but unlike most binary operations, shifts/rotates have the same type between lhs and rhs1, but rhs2 can have different type. So, the lh == rh comparison ICEs because the wide_ints have different precision (but same values).
next prev parent reply other threads:[~2023-02-02 15:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-02 14:29 [Bug tree-optimization/108639] New: ICE on valid code at -O1 and above: in decompose, at wide-int.h:984 zhendong.su at inf dot ethz.ch 2023-02-02 14:43 ` [Bug tree-optimization/108639] ]13 Regression] ICE on valid code at -O1 and above: in decompose, at wide-int.h:984 since r13-5578 jakub at gcc dot gnu.org 2023-02-02 15:11 ` jakub at gcc dot gnu.org [this message] 2023-02-02 15:31 ` jakub at gcc dot gnu.org 2023-02-02 15:47 ` jakub at gcc dot gnu.org 2023-02-02 17:13 ` [Bug tree-optimization/108639] [13 " aldyh at gcc dot gnu.org 2023-02-02 17:14 ` aldyh at gcc dot gnu.org 2023-02-02 17:15 ` aldyh at gcc dot gnu.org 2023-02-02 18:07 ` jakub at gcc dot gnu.org 2023-02-02 19:09 ` amacleod at redhat dot com 2023-02-02 19:56 ` jakub at gcc dot gnu.org 2023-02-03 7:56 ` rguenth at gcc dot gnu.org 2023-02-03 8:49 ` aldyh at gcc dot gnu.org 2023-02-03 20:33 ` cvs-commit at gcc dot gnu.org 2023-02-03 20:43 ` jakub at gcc dot gnu.org 2023-02-03 22:56 ` pinskia 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-108639-4-RKbMJ3bb1A@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: linkBe 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).