public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112376] [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c missed threading in aarch64 case
Date: Thu, 15 Feb 2024 07:55:53 +0000 [thread overview]
Message-ID: <bug-112376-4-VJ3tudBu8S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112376-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112376
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-02-15
Summary|[14 Regression] |[14 Regression]
|gcc.dg/tree-ssa/ssa-dom-thr |gcc.dg/tree-ssa/ssa-dom-thr
|ead-7.c was not adjusted |ead-7.c missed threading in
|for aarch64 case |aarch64 case
Ever confirmed|0 |1
Keywords| |missed-optimization
Component|testsuite |tree-optimization
Status|UNCONFIRMED |NEW
CC| |amacleod at redhat dot com,
| |tnfchris at gcc dot gnu.org
--- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
This is a jumpthreading regression caused by:
commit g:0cfc9c953d0221ec3971a25e6509ebe1041f142e
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Thu Aug 17 12:34:59 2023 -0400
Phi analyzer - Initialize with range instead of a tree.
Rangers PHI analyzer currently only allows a single initializer to a group.
This patch changes that to use an inialization range, which is
cumulative of all integer constants, plus a single symbolic value.
There is no other change to group functionality.
This patch also changes the way PHI groups are printed so they show up in
the
listing as they are encountered, rather than as a list at the end. It
was more difficult to see what was going on previously.
We seem to miss one thread that we did previously in the testcase. The new
code does look worse.
Jumpthreading is outside my wheelhouse for now, so any Ideas Andrew?
next prev parent reply other threads:[~2024-02-15 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 6:24 [Bug testsuite/112376] New: [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c was not adjusted for " pinskia at gcc dot gnu.org
2023-11-04 6:24 ` [Bug testsuite/112376] " pinskia at gcc dot gnu.org
2024-02-15 7:55 ` tnfchris at gcc dot gnu.org [this message]
2024-03-07 21:03 ` [Bug tree-optimization/112376] [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c missed threading in " law at gcc dot gnu.org
2024-05-07 7:42 ` [Bug tree-optimization/112376] [14/15 " 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-112376-4-VJ3tudBu8S@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).