https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
Filip Kastl changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
--- Comment #4 from Filip Kastl ---
Hmm. The slowdown disappeared again. The measurements went back to their
original values. I'll mark this PR as WORKSFORME if there are no objections.
Btw we upgraded the machine's glibc. That happened after t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
--- Comment #3 from Filip Kastl ---
The machine in question has glibc 2.36 so the benchmark is running without this
memchr improvement. We intend to update that machine sometime in the next 3
months. I can get back to this bug when we do that an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
--- Comment #2 from Andrew Pinski ---
Also what glibc version is on the system? Since if it is std::find that is
causing the regression memchr was improved in the last year or so in glibc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
Filip Kastl changed:
What|Removed |Added
Target Milestone|--- |15.0
