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 testsuite/107830] New: [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813 Date: Wed, 23 Nov 2022 03:54:08 +0000 [thread overview] Message-ID: <bug-107830-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107830 Bug ID: 107830 Summary: [13 Regression] ICE in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openmp Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: aarch64-linux-gnu gcc 13.0.0 20221120 snapshot (g:a16a5460447eaaff0b4468064e4d7b1cc8fc42eb) ICEs when compiling the following testcase, reduced from libgomp/testsuite/libgomp.c-c++-common/for-15.c, w/ -march=armv9-a -Os -fopenmp: void f2 (int *a) { unsigned int i; #pragma omp simd for (i = 0; i < 4; ++i) a[i / 3] -= 4; } % aarch64-linux-gnu-gcc-13 -march=armv9-a -Os -fopenmp -c t3uokd3k.c during RTL pass: expand t3uokd3k.c: In function 'f2': t3uokd3k.c:8:9: internal compiler error: in gen_aarch64_bitmask_udiv3, at ./insn-opinit.h:813 8 | a[i / 3] -= 4; | ~~^~~ 0x7e5c72 gen_aarch64_bitmask_udiv3(machine_mode, rtx_def*, rtx_def*, rtx_def*) ./insn-opinit.h:813 0x7e5c72 gen_aarch64_bitmask_udiv3(machine_mode, rtx_def*, rtx_def*, rtx_def*) ./insn-opinit.h:810 0x7e5c72 aarch64_vectorize_can_special_div_by_constant(tree_code, tree_node*, generic_wide_int<wide_int_storage>, rtx_def**, rtx_def*, rtx_def*) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/config/aarch64/aarch64.cc:24339 0xb26cca expand_divmod(int, tree_code, machine_mode, tree_node*, tree_node*, rtx_def*, rtx_def*, rtx_def*, int, optab_methods) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/expmed.cc:4383 0xb2a706 expand_expr_divmod /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/expr.cc:9198 0xb349ab expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier) /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/expr.cc:9868 0xa0eac0 expand_gimple_stmt_1 /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/cfgexpand.cc:3983 0xa0eac0 expand_gimple_stmt /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/cfgexpand.cc:4044 0xa14e2e expand_gimple_basic_block /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/cfgexpand.cc:6096 0xa16817 execute /var/tmp/portage/cross-aarch64-linux-gnu/gcc-13.0.0_p20221120/work/gcc-13-20221120/gcc/cfgexpand.cc:6822
next reply other threads:[~2022-11-23 3:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-23 3:54 asolokha at gmx dot com [this message] 2022-11-23 10:11 ` [Bug target/107830] " marxin at gcc dot gnu.org 2022-11-23 10:43 ` ktkachov at gcc dot gnu.org 2022-11-23 10:53 ` tnfchris at gcc dot gnu.org 2022-11-23 20:54 ` rguenth at gcc dot gnu.org 2022-11-25 12:58 ` cvs-commit at gcc dot gnu.org 2022-11-25 12:59 ` tnfchris 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-107830-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).