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 tree-optimization/111039] [11/12/13/14 Regression] Unable to coalesce ssa_names
Date: Wed, 16 Aug 2023 20:00:24 +0000 [thread overview]
Message-ID: <bug-111039-4-1SGjisvO0Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111039-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111039
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Target Milestone|--- |11.5
Known to work| |4.8.5
Last reconfirmed| |2023-08-16
Summary|Unable to coalesce |[11/12/13/14 Regression]
|ssa_names |Unable to coalesce
| |ssa_names
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andreas Krebbel from comment #0)
> This very much looks like another instance of PR71020.
It is much older than that though.
Confirmed.
next prev parent reply other threads:[~2023-08-16 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 19:28 [Bug tree-optimization/111039] New: " krebbel at gcc dot gnu.org
2023-08-16 20:00 ` pinskia at gcc dot gnu.org [this message]
2023-08-16 20:03 ` [Bug tree-optimization/111039] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-08-16 20:08 ` pinskia at gcc dot gnu.org
2023-08-17 11:07 ` rguenth at gcc dot gnu.org
2023-08-17 13:28 ` cvs-commit at gcc dot gnu.org
2023-08-17 13:49 ` [Bug tree-optimization/111039] [11/12/13 " rguenth at gcc dot gnu.org
2023-08-24 10:56 ` cvs-commit at gcc dot gnu.org
2024-05-17 11:12 ` [Bug tree-optimization/111039] [11/12 " cvs-commit at gcc dot gnu.org
2024-06-21 9:22 ` [Bug tree-optimization/111039] [11 " cvs-commit at gcc dot gnu.org
2024-06-21 9:38 ` 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-111039-4-1SGjisvO0Q@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).