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 bootstrap/102681] [12 Regression] AArch64 bootstrap failure
Date: Fri, 22 Oct 2021 07:47:44 +0000 [thread overview]
Message-ID: <bug-102681-4-rfUl6GFkeh@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 #20 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #16)
> (In reply to Andrew Pinski from comment #15)
> > We totally missed the jump threading of 3->5->7 path and the 4->5->8 path.
>
> FAIL: path through PHI in bb8 (incoming bb:6) crosses loop
>
> But but, it does not exactly cross the loop as 5 (6) is not part of the loop
> but rather just 8.
I looked at the IL, and this still counts as crossing loop boundaries. Your
going from no loop to loop 1. No cigar :-(.
Actually, even if you remove the hunk I mentioned the shared registry
restrictions will disallow it. That being said, I should clean that up.
next prev parent reply other threads:[~2021-10-22 7:47 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
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 [this message]
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-rfUl6GFkeh@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).