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 tree-optimization/97315] [11 Regression] ICE in choose_value, at gimple-ssa-evrp.c:282 since r11-3690-gebc77ce3a4c70730b4e38d68f88693eadbdc8712
Date: Wed, 07 Oct 2020 10:04:25 +0000	[thread overview]
Message-ID: <bug-97315-4-GCLhYipKDL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97315-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97315

Alex Coplan <acoplan at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acoplan at gcc dot gnu.org

--- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> ---
Seeing a similar ICE with the following simple C testcase:

int a;
int b(signed char c, int d) { return c < 0 ? 0 : c >> d; }
void e(void)
{
  for (int i = 0; i <= 0; i++)
    while (a)
      b(-(i != 1), i);
}

$ aarch64-elf-gcc -O2 test.c
during GIMPLE pass: evrp
test.c: In function 'e':
test.c:8:1: internal compiler error: in choose_value, at gimple-ssa-evrp.c:282
    8 | }
      | ^
0x18d93f0 hybrid_folder::choose_value(tree_node*, tree_node*)
        /home/alecop01/toolchain/src/gcc/gcc/gimple-ssa-evrp.c:282
0x18d94e4 hybrid_folder::value_of_expr(tree_node*, gimple*)
        /home/alecop01/toolchain/src/gcc/gcc/gimple-ssa-evrp.c:236
0xf8e112 substitute_and_fold_engine::replace_uses_in(gimple*)
        /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-propagate.c:871
0xf8e912 substitute_and_fold_dom_walker::before_dom_children(basic_block_def*)
        /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-propagate.c:1141
0x18a5d5b dom_walker::walk(basic_block_def*)
        /home/alecop01/toolchain/src/gcc/gcc/domwalk.c:309
0xf8f885 substitute_and_fold_engine::substitute_and_fold(basic_block_def*)
        /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-propagate.c:1283
0x18d9828 execute_early_vrp
        /home/alecop01/toolchain/src/gcc/gcc/gimple-ssa-evrp.c:328
0x18d9bf8 execute
        /home/alecop01/toolchain/src/gcc/gcc/gimple-ssa-evrp.c:375
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.

  parent reply	other threads:[~2020-10-07 10:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  8:34 [Bug tree-optimization/97315] New: " marxin at gcc dot gnu.org
2020-10-07  8:34 ` [Bug tree-optimization/97315] " marxin at gcc dot gnu.org
2020-10-07 10:04 ` acoplan at gcc dot gnu.org [this message]
2020-10-07 12:02 ` aldyh at gcc dot gnu.org
2020-10-07 12:13 ` aldyh at gcc dot gnu.org
2020-10-07 12:21 ` rguenth at gcc dot gnu.org
2020-10-07 12:26 ` rguenth at gcc dot gnu.org
2020-10-07 12:35 ` dcb314 at hotmail dot com
2020-10-07 15:27 ` amacleod at redhat dot com
2020-10-07 15:35 ` amacleod at redhat dot com
2020-10-07 17:22 ` rguenther at suse dot de
2020-10-07 18:07 ` amacleod at redhat dot com
2020-10-08  9:21 ` cvs-commit at gcc dot gnu.org
2020-10-08  9:36 ` cvs-commit at gcc dot gnu.org
2020-10-08  9:38 ` aldyh 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-97315-4-GCLhYipKDL@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).