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/99542] New: [9/10/11 Regression] ICE in exact_div, at poly-int.h:2219
Date: Thu, 11 Mar 2021 06:05:46 +0000 [thread overview]
Message-ID: <bug-99542-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99542
Bug ID: 99542
Summary: [9/10/11 Regression] ICE in exact_div, at
poly-int.h:2219
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, openmp
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-alpha20210307 snapshot (g:a18ebd6c439227b048a91fbfa66f5983f884c157)
ICEs when compiling gcc/testsuite/gcc.dg/gomp/pr89246-2.c w/ -fopenmp[-simd]:
% aarch64-linux-gnu-gcc-11.0.1 -fopenmp -c
gcc/testsuite/gcc.dg/gomp/pr89246-2.c
during IPA pass: simdclone
gcc/testsuite/gcc.dg/gomp/pr89246-2.c:13:1: internal compiler error: in
exact_div, at poly-int.h:2219
13 | }
| ^
0x8754e0 poly_int<2u, poly_result<unsigned long, if_nonpoly<unsigned short,
unsigned short, poly_int_traits<unsigned short>::is_poly>::type,
poly_coeff_pair_traits<unsigned long, if_nonpoly<unsigned short, unsigned
short, poly_int_traits<unsigned short>::is_poly>::type>::result_kind>::type>
exact_div<2u, unsigned long, unsigned short>(poly_int_pod<2u, unsigned long>
const&, unsigned short)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/poly-int.h:2219
0x8760a5 poly_int<2u, poly_result<unsigned long, if_nonpoly<unsigned short,
unsigned short, poly_int_traits<unsigned short>::is_poly>::type,
poly_coeff_pair_traits<unsigned long, if_nonpoly<unsigned short, unsigned
short, poly_int_traits<unsigned short>::is_poly>::type>::result_kind>::type>
exact_div<2u, unsigned long, unsigned short>(poly_int_pod<2u, unsigned long>
const&, unsigned short)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/tree.h:3467
0x8760a5 simd_clone_adjust_argument_types
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/omp-simd-clone.c:622
0x1aa6f5b expand_simd_clones(cgraph_node*)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/omp-simd-clone.c:1784
0x1aa7287 ipa_omp_simd_clone
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/omp-simd-clone.c:1798
0x1aa7287 execute
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210307/work/gcc-11-20210307/gcc/omp-simd-clone.c:1826
(Is it the exact reason the testcase has /* { dg-options "-O0 -fno-openmp
-fno-openmp-simd" } */?)
next reply other threads:[~2021-03-11 6:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 6:05 asolokha at gmx dot com [this message]
2021-03-11 8:44 ` [Bug target/99542] " rguenth at gcc dot gnu.org
2021-03-12 11:22 ` jakub at gcc dot gnu.org
2021-03-12 11:23 ` jakub at gcc dot gnu.org
2021-03-12 11:39 ` jakub at gcc dot gnu.org
2021-03-16 9:35 ` cvs-commit at gcc dot gnu.org
2021-03-16 9:51 ` [Bug target/99542] [9/10 " jakub at gcc dot gnu.org
2021-03-16 21:51 ` cvs-commit at gcc dot gnu.org
2021-03-17 11:15 ` cvs-commit at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-20 8:09 ` [Bug target/99542] [9 " jakub at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org
2021-04-22 13:40 ` 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-99542-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: link
Be 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).