public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107920] New: [13 Regression] ICE in execute_todo, at passes.cc:2140 Date: Tue, 29 Nov 2022 16:53:23 +0000 [thread overview] Message-ID: <bug-107920-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920 Bug ID: 107920 Summary: [13 Regression] ICE in execute_todo, at passes.cc:2140 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: aarch64-linux-gnu gcc 13.0.0 20221127 snapshot (g:4ac789789ea866ced24613e4778725d8ec6b0ecf) ICEs when compiling the following testcase, reduced from gcc/testsuite/gcc.target/aarch64/sve/acle/general/pr96463-2.c, w/ -march=armv8-a+sve2 -O1 -fno-tree-ccp -fno-tree-forwprop: #include "arm_sve.h" svint8_t test_s8(int8_t *x) { return svld1rq_s8 (svptrue_b8 (), &x[0]); } % aarch64-linux-gnu-gcc-13 -march=armv8-a+sve2 -O1 -fno-tree-ccp -fno-tree-forwprop -c xgdgkm2d.c during GIMPLE pass: fre xgdgkm2d.c: In function 'test_s8': xgdgkm2d.c:7:1: internal compiler error: in execute_todo, at passes.cc:2140 7 | } | ^ 0x751734 execute_todo /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221127/work/gcc-13-20221127/gcc/passes.cc:2140
next reply other threads:[~2022-11-29 16:53 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 16:53 asolokha at gmx dot com [this message] 2022-11-29 18:42 ` [Bug tree-optimization/107920] " pinskia at gcc dot gnu.org 2022-11-29 18:46 ` pinskia at gcc dot gnu.org 2022-11-29 18:50 ` pinskia at gcc dot gnu.org 2022-11-29 18:51 ` pinskia at gcc dot gnu.org 2022-11-29 19:18 ` pinskia at gcc dot gnu.org 2022-11-29 19:54 ` pinskia at gcc dot gnu.org 2022-11-29 19:59 ` [Bug target/107920] " pinskia at gcc dot gnu.org 2022-11-29 20:12 ` pinskia at gcc dot gnu.org 2022-11-29 20:36 ` pinskia at gcc dot gnu.org 2022-11-30 11:48 ` rguenth at gcc dot gnu.org 2022-11-30 11:51 ` rguenth at gcc dot gnu.org 2022-11-30 16:56 ` prathamesh3492 at gcc dot gnu.org 2022-12-01 12:22 ` jakub at gcc dot gnu.org 2022-12-01 18:06 ` prathamesh3492 at gcc dot gnu.org 2022-12-02 9:13 ` prathamesh3492 at gcc dot gnu.org 2022-12-07 8:06 ` cvs-commit at gcc dot gnu.org 2022-12-08 15:55 ` jakub 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-107920-4@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).