public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106534] [13 Regression][gcn] ICE 'verify_ssa failed' / 'error: definition in block 18 does not dominate use in block 19' during libgfortran bootstrap
Date: Fri, 05 Aug 2022 10:56:11 +0000 [thread overview]
Message-ID: <bug-106534-4-rfdw1TYmgn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106534-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106534
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 5 Aug 2022, burnus at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106534
>
> --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
> Seems as if the ICE is fixed for that file by reverting the following commit:
>
> commit r13-1963-gc832ec4c3ec4853ad89ff3b0dbf6e9454e75e8cc
> middle-end: Fix phi-ssa assertion triggers. [PR106519]
As hinted in the e-mail exchange the earlier two transforms might need
guarding with !diamond_p since IIRC only minmax is capable of dealing
with it?
next prev parent reply other threads:[~2022-08-05 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 9:02 [Bug middle-end/106534] New: " burnus at gcc dot gnu.org
2022-08-05 9:11 ` [Bug middle-end/106534] " rguenth at gcc dot gnu.org
2022-08-05 10:23 ` burnus at gcc dot gnu.org
2022-08-05 10:49 ` tnfchris at gcc dot gnu.org
2022-08-05 10:54 ` burnus at gcc dot gnu.org
2022-08-05 10:56 ` rguenther at suse dot de [this message]
2022-08-05 11:03 ` tnfchris at gcc dot gnu.org
2022-08-05 11:06 ` burnus at gcc dot gnu.org
2022-08-05 11:17 ` tnfchris at gcc dot gnu.org
2022-08-05 11:24 ` tnfchris at gcc dot gnu.org
2022-08-05 13:54 ` cvs-commit at gcc dot gnu.org
2022-08-05 13:56 ` tnfchris 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-106534-4-rfdw1TYmgn@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).