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 19:56:07 +0000 [thread overview] Message-ID: <bug-108639-4-VYfADIL0Z8@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 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ok then. I won't test my patch then, the testcases from it were: --- gcc/testsuite/gcc.c-torture/compile/pr108638.c.jj 2022-11-21 10:04:00.210677046 +0100 +++ gcc/testsuite/gcc.c-torture/compile/pr108638.c 2023-02-02 16:51:06.082371450 +0100 @@ -0,0 +1,12 @@ +/* PR tree-optimization/108638 */ + +long long a; +int b; + +void +foo (void) +{ + for (a = 0; a < __SIZEOF_LONG_LONG__ * __CHAR_BIT__; a++) + if (b) + b |= a << a; +} --- gcc/testsuite/gcc.c-torture/compile/pr108639.c.jj 2023-02-02 16:26:44.113600462 +0100 +++ gcc/testsuite/gcc.c-torture/compile/pr108639.c 2023-02-02 16:26:23.309902211 +0100 @@ -0,0 +1,11 @@ +/* PR tree-optimization/108639 */ + +long long a; + +int +main () +{ + a = a ? 0 || 0 % 0 : 0; + a = a << a; + return 0; +}
next prev parent reply other threads:[~2023-02-02 19:56 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 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 [this message] 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-VYfADIL0Z8@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).