public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101394] ICE on valid code with -O2: SSA corruption: Unable to coalesce ssa_names 10 and 19 which are marked as MUST COALESCE.
Date: Mon, 12 Jul 2021 07:47:28 +0000 [thread overview]
Message-ID: <bug-101394-4-Hms3R3HtvT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101394-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101394
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-07-12
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look.
next prev parent reply other threads:[~2021-07-12 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 14:00 [Bug tree-optimization/101394] New: " cnsun at uwaterloo dot ca
2021-07-09 16:43 ` [Bug tree-optimization/101394] " pinskia at gcc dot gnu.org
2021-07-12 7:47 ` rguenth at gcc dot gnu.org [this message]
2021-07-12 9:09 ` marxin at gcc dot gnu.org
2021-07-12 10:19 ` cvs-commit at gcc dot gnu.org
2021-07-12 10:20 ` rguenth at gcc dot gnu.org
2021-07-12 17:18 ` [Bug tree-optimization/101394] [9/10/11 Regression] " pinskia at gcc dot gnu.org
2021-07-12 17:20 ` pinskia at gcc dot gnu.org
2021-07-13 10:59 ` cvs-commit at gcc dot gnu.org
2021-09-06 10:18 ` [Bug tree-optimization/101394] [9/10 " cvs-commit at gcc dot gnu.org
2021-09-06 10:20 ` [Bug tree-optimization/101394] [9 " rguenth at gcc dot gnu.org
2021-10-13 10:09 ` cvs-commit at gcc dot gnu.org
2021-10-13 10:10 ` rguenth 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-101394-4-Hms3R3HtvT@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).