public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100284] gcc crash with -march=armv8.2-a+sve -O3 Date: Tue, 27 Apr 2021 11:11:41 +0000 [thread overview] Message-ID: <bug-100284-4-3Dr2YEY7H4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100284-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100284 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #2 from Alex Coplan <acoplan at gcc dot gnu.org> --- Nevermind, confirmed on latest trunk with a native aarch64 build. Here's a reduced testcase: $ cat test.c int *a; int b; void c() { int e; for (int d; d; d++) if (a[d]) e++; if (e) b = 0; } $ gcc/xgcc -B gcc test.c -c -O3 -march=armv8.2-a+sve during GIMPLE pass: vrp test.c: In function ‘c’: test.c:3:6: internal compiler error: in operation_could_trap_p, at tree-eh.c:2546 3 | void c() { | ^ 0xe725cb operation_could_trap_p(tree_code, bool, bool, tree_node*) /home/alecop01/toolchain/src/gcc/gcc/tree-eh.c:2546 0x12df947 maybe_resimplify_conditional_op /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:156 0x12df49b gimple_resimplify3 /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:404 0x13383a3 gimple_simplify_381 /home/alecop01/toolchain/builds/rel/gcc/gimple-match.c:20829 0x1339bab gimple_simplify_PLUS_EXPR /home/alecop01/toolchain/builds/rel/gcc/gimple-match.c:58341 0x14586db gimple_simplify /home/alecop01/toolchain/builds/rel/gcc/gimple-match.c:135430 0x1459cfb gimple_resimplify2 /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:318 0x147f50b try_conditional_simplification /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:872 0x147f50b gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node* (*)(tree_node*), tree_node* (*)(tree_node*)) /home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:1046 0xaaf51f fold_stmt_1 /home/alecop01/toolchain/src/gcc/gcc/gimple-fold.c:6204 0xff5f8b substitute_and_fold_dom_walker::before_dom_children(basic_block_def*) /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-propagate.c:859 0x195b313 dom_walker::walk(basic_block_def*) /home/alecop01/toolchain/src/gcc/gcc/domwalk.c:309 0xff4dbb substitute_and_fold_engine::substitute_and_fold(basic_block_def*) /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-propagate.c:987 0x11408fb execute_vrp /home/alecop01/toolchain/src/gcc/gcc/tree-vrp.c:4531 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2021-04-27 11:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-27 9:50 [Bug c/100284] New: " gilles.gouaillardet at gmail dot com 2021-04-27 10:52 ` [Bug c/100284] " acoplan at gcc dot gnu.org 2021-04-27 11:11 ` acoplan at gcc dot gnu.org [this message] 2021-04-27 12:21 ` [Bug tree-optimization/100284] ICE in operation_could_trap_p " rguenth at gcc dot gnu.org 2021-04-27 12:41 ` rsandifo at gcc dot gnu.org 2021-04-27 15:25 ` acoplan at gcc dot gnu.org 2021-04-27 17:30 ` cvs-commit at gcc dot gnu.org 2021-04-28 5:49 ` gilles.gouaillardet at gmail dot com 2021-04-28 7:41 ` gilles.gouaillardet at gmail dot com 2021-04-28 8:34 ` rsandifo 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-100284-4-3Dr2YEY7H4@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).