[Bug tree-optimization/112376] [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c missed threading in aarch64 case

2024-03-07 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112376

Jeffrey A. Law  changed:

   What|Removed |Added

   Priority|P3  |P2
 CC||law at gcc dot gnu.org

[Bug tree-optimization/112376] [14 Regression] gcc.dg/tree-ssa/ssa-dom-thread-7.c missed threading in aarch64 case

2024-02-14 Thread tnfchris at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112376

Tamar Christina  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  ---
This is a jumpthreading regression caused by:

commit g:0cfc9c953d0221ec3971a25e6509ebe1041f142e
Author: Andrew MacLeod 
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?