[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 Richard Biener changed: What|Removed |Added Target Milestone|14.0|14.2 --- Comment #2 from Richard Biener --- GCC 14.1 is being released, retargeting bugs to GCC 14.2.
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 Tamar Christina changed: What|Removed |Added CC||tnfchris at gcc dot gnu.org --- Comment #3 from Tamar Christina --- Hi Filip, Do you generate these runs with counters based PGO or compiler instrumentation? Just so I know before I start trying to reproduce them.
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 --- Comment #4 from Filip Kastl --- (In reply to Tamar Christina from comment #3) > Hi Filip, > > Do you generate these runs with counters based PGO or compiler > instrumentation? > > Just so I know before I start trying to reproduce them. Hi Tamar, By counters you mean some sort of hardware counters? I didn't know there were multiple ways to do PGO with GCC. I think that the answer to your question is "compiler instrumentation". I just do -fprofile-generate, run the instrumented binary and then -fprofile-use.
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 --- Comment #5 from Tamar Christina --- (In reply to Filip Kastl from comment #4) > (In reply to Tamar Christina from comment #3) > > Hi Filip, > > > > Do you generate these runs with counters based PGO or compiler > > instrumentation? > > > > Just so I know before I start trying to reproduce them. > > Hi Tamar, > > By counters you mean some sort of hardware counters? I didn't know there > were multiple ways to do PGO with GCC. > > I think that the answer to your question is "compiler instrumentation". I > just do -fprofile-generate, run the instrumented binary and then > -fprofile-use. Yeah, with some elbow grease the perf record method works too, but it's not very accurate on Armv8. I'll try to reproduce and bisect these over the weekend!
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 --- Comment #6 from Andrew Pinski --- Looks like the regression mentioned in comment #0 is fixed. And even the regression that happened during GCC 14. There is still more from GCC 13 though.
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 --- Comment #7 from Filip Kastl --- (In reply to Andrew Pinski from comment #6) >There is still more from GCC 13 though. I'm not sure what you mean by that. GCC 13 looks fine to me. Here is a comparison of measurements on trunk, 12, 13 and 14 https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.6=755.100.0&plot.7=868.100.0&plot.8=1032.100.0&plot.9=586.100.0 It seems to me that the only version of GCC where this bug persists may be GCC 14. I'm not sure if the changes that removed the slowdown from trunk were also backported to 14.
[Bug target/114412] [14/15 Regression] 7% slowdown of 436.cactusADM on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412 Jakub Jelinek changed: What|Removed |Added Target Milestone|14.2|14.3 --- Comment #8 from Jakub Jelinek --- GCC 14.2 is being released, retargeting bugs to GCC 14.3.
