public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102681] [12 Regression] AArch64 bootstrap failure
Date: Fri, 22 Oct 2021 05:42:54 +0000	[thread overview]
Message-ID: <bug-102681-4-Wv4uTSK2Uu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102681-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So the major difference comes from mark_stack_region_used.
We have a missing jump thread in ethread.

Before the patch, ethread was able to jump thread all the way through:
  if (_13 != 0)
    goto <bb 3>; [5.50%]
  else
    goto <bb 4>; [94.50%]

  <bb 3> :
  # _22 = PHI <0(2)>
  goto <bb 7>; [INV]

  <bb 4> :
  # _18 = PHI <1(2)>
  _15 = upper_bound.coeffs[0];
  goto <bb 6>; [100.00%]

  <bb 5> :

But after we get:

  <bb 2> :
  _13 = upper_bound.coeffs[1];
  if (_13 != 0)
    goto <bb 3>; [5.50%]
  else
    goto <bb 4>; [94.50%]

  <bb 3> :
  # _22 = PHI <0(2)>
  goto <bb 5>; [100.00%]

  <bb 4> :
  # _9 = PHI <1(2)>
  _15 = upper_bound.coeffs[0];

  <bb 5> :
  # _16 = PHI <0(3), 1(4)>
  # const_upper_20 = PHI <const_upper_21(D)(3), _15(4)>
  if (_16 != 0)
    goto <bb 7>; [INV]
  else
    goto <bb 8>; [INV]

We totally missed the jump threading of 3->5->7 path and the 4->5->8 path.

Aldy,
  Can you look into why there is a missing jump threading there?

  parent reply	other threads:[~2021-10-22  5:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  5:58 [Bug tree-optimization/102681] New: " fxue at os dot amperecomputing.com
2021-10-11  6:34 ` [Bug tree-optimization/102681] " aldyh at gcc dot gnu.org
2021-10-11  8:07 ` tnfchris at gcc dot gnu.org
2021-10-11  9:09 ` [Bug bootstrap/102681] [12 Regression] " rguenth at gcc dot gnu.org
2021-10-11 16:35 ` msebor at gcc dot gnu.org
2021-10-14  7:00 ` fxue at os dot amperecomputing.com
2021-10-14 12:25 ` rsandifo at gcc dot gnu.org
2021-10-16 20:03 ` pinskia at gcc dot gnu.org
2021-10-21  9:22 ` pinskia at gcc dot gnu.org
2021-10-21 18:21 ` pinskia at gcc dot gnu.org
2021-10-21 18:43 ` pinskia at gcc dot gnu.org
2021-10-21 18:58 ` pinskia at gcc dot gnu.org
2021-10-21 19:52 ` pinskia at gcc dot gnu.org
2021-10-21 22:23 ` pinskia at gcc dot gnu.org
2021-10-21 22:35 ` pinskia at gcc dot gnu.org
2021-10-21 23:21 ` pinskia at gcc dot gnu.org
2021-10-22  5:42 ` pinskia at gcc dot gnu.org [this message]
2021-10-22  5:47 ` pinskia at gcc dot gnu.org
2021-10-22  6:12 ` tnfchris at gcc dot gnu.org
2021-10-22  7:21 ` aldyh at gcc dot gnu.org
2021-10-22  7:30 ` aldyh at gcc dot gnu.org
2021-10-22  7:47 ` aldyh at gcc dot gnu.org
2021-10-22  8:32 ` rguenth at gcc dot gnu.org
2021-10-22  9:41 ` cvs-commit at gcc dot gnu.org
2021-10-22  9:42 ` rguenth at gcc dot gnu.org
2021-10-22 11:21 ` 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-102681-4-Wv4uTSK2Uu@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).