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 target/99767] New: [9/10/11 Regression] ICE in expand_direct_optab_fn, at internal-fn.c:3360 Date: Thu, 25 Mar 2021 11:19:18 +0000 [thread overview] Message-ID: <bug-99767-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99767 Bug ID: 99767 Summary: [9/10/11 Regression] ICE in expand_direct_optab_fn, at internal-fn.c:3360 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: aarch64-linux-gnu gcc-11.0.1-alpha20210321 snapshot (g:fc24ea2374259d401a46ce3526688b7e79d4cc13) ICEs when compiling the following testcase w/ -march=armv8-a+sve -O1 -fno-tree-dce: int __attribute__ ((simd)) foo (void) { int v = 1 / 0; return 0; } % aarch64-linux-gnu-gcc-11.0.1 -march=armv8-a+sve -O1 -fno-tree-dce -w -c yiptql8b.c during RTL pass: expand yiptql8b.c: In function 'foo.simdclone.1': yiptql8b.c:4:7: internal compiler error: in expand_direct_optab_fn, at internal-fn.c:3360 4 | int v = 1 / 0; | ^ 0x70a2a1 expand_direct_optab_fn /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/internal-fn.c:3360 0xa15697 expand_call_stmt /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/cfgexpand.c:2749 0xa15697 expand_gimple_stmt_1 /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/cfgexpand.c:3844 0xa15697 expand_gimple_stmt /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/cfgexpand.c:4008 0xa1b41a expand_gimple_basic_block /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/cfgexpand.c:6045 0xa1cfbf execute /var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/cfgexpand.c:6729
next reply other threads:[~2021-03-25 11:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 11:19 asolokha at gmx dot com [this message] 2021-03-25 11:57 ` [Bug target/99767] " rguenth at gcc dot gnu.org 2021-03-25 11:57 ` rguenth at gcc dot gnu.org 2021-03-25 15:22 ` jakub at gcc dot gnu.org 2021-03-25 15:27 ` jakub at gcc dot gnu.org 2021-04-15 13:09 ` rguenth at gcc dot gnu.org 2021-04-15 14:58 ` jakub at gcc dot gnu.org 2021-04-15 15:32 ` jakub at gcc dot gnu.org 2021-04-16 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-16 9:58 ` [Bug target/99767] [9/10 " jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:53 ` [Bug target/99767] [9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 15:01 ` 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-99767-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).