[Bug tree-optimization/114787] [14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

2024-04-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787

Andrew Pinski  changed:

   What|Removed |Added

  Component|target  |tree-optimization

--- Comment #3 from Andrew Pinski  ---
(In reply to Andrew Pinski from comment #2)
> The first difference besides prediction/counts on the BB is in the register
> allocator.
> 
> The code for aarch64 looks ok too.

So I was wrong (and now even more confused than before). In that sometimes even
GCC 13.2.0 code generation is broken. But I don't understand what the
conditions are which cause it (adding -fdump-tree-optimized-all or something
like that seems to cause different code generation).

[Bug tree-optimization/114787] [14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

2024-04-20 Thread law at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787

Jeffrey A. Law  changed:

   What|Removed |Added

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

[Bug tree-optimization/114787] [14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)

2024-04-20 Thread jakub at gcc dot gnu.org via Gcc-bugs 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787

Jakub Jelinek  changed:

   What|Removed |Added

Version|unknown |14.0
   Last reconfirmed||2024-04-20
 CC||hubicka at gcc dot gnu.org,
   ||jakub at gcc dot gnu.org,
   ||rguenth at gcc dot gnu.org
   Target Milestone|--- |14.0
 Status|UNCONFIRMED |NEW
Summary|wrong code at -O1 on|[14 Regression] wrong code
   |x86_64-linux-gnu (the   |at -O1 on x86_64-linux-gnu
   |generated code hangs)   |(the generated code hangs)
 Ever confirmed|0   |1

--- Comment #1 from Jakub Jelinek  ---
Started with r14-7138-g05e8ef2a05b477589cae25af3311bad0f68a90fe