public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh 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 12:02:16 +0000	[thread overview]
Message-ID: <bug-97315-4-P4JpaA1n68@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

--- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
evrp and ranger disagree on the singleton range for _3 in the following stmt:

 <bb 5> :
  if (_3 != 1)

(gdb) ptg evrp_ret
0

(gdb) ptg ranger_ret
1

Which is interesting because BB5 is actually unreachable:

add_type_duplicate ()
{
  struct tree_node * D.2384;
  struct tree_node * add_type_duplicate_type.2_1;
  short unsigned int _2;
  int _3;
  tree_code_class _4;

  <bb 2> :
  add_type_duplicate_type.2_1 = add_type_duplicate_type;
  _2 = add_type_duplicate_type.2_1->base.code;
  _3 = (int) _2;
  _4 = tree_code_type[_3];
  if (_4 != 0)
    goto <bb 3>; [INV]
  else
    goto <bb 11>; [INV]

  <bb 3> :
  if (_2 == 0)
    goto <bb 13>; [INV]
  else
    goto <bb 11>; [INV]

  <bb 4> :
  if (0 != 0)
    goto <bb 5>; [66.00%]
  else
    goto <bb 15>; [34.00%]

  <bb 15> :
  goto <bb 12>; [100.00%]

  <bb 5> :
  if (_3 != 1)
    goto <bb 6>; [0.04%]
  else
    goto <bb 14>; [99.96%]

  <bb 14> :
  goto <bb 7>; [100.00%]

  <bb 6> :
  tree_check_failed ();

  <bb 13> :

  <bb 7> :

  <bb 12> :
  if (0 != 0)
    goto <bb 8>; [66.00%]
  else
    goto <bb 10>; [34.00%]

  <bb 8> :
  if (1 != 0)
    goto <bb 9>; [0.04%]
  else
    goto <bb 10>; [99.96%]

  <bb 9> :
  tree_check_failed ();

  <bb 10> :
  if (1 != 0)
    goto <bb 4>; [INV]
  else
    goto <bb 11>; [INV]

  <bb 11> :
  return;

}

I'm guessing evrp

  parent reply	other threads:[~2020-10-07 12:02 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
2020-10-07 12:02 ` aldyh at gcc dot gnu.org [this message]
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-P4JpaA1n68@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).