[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-14 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-14 Thread Florian Weimer
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #8 from Florian Weimer --- The ELN glibc scratch build succeeded: https://src.fedoraproject.org/rpms/glibc/pull-request/92#comment-194579 There's a TMT failure, but it's unrelated (potential kernel robust mutex issue). This test does not

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-14 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #7 from Mark Wielaard --- There is now also an fedora eln build: https://koji.fedoraproject.org/koji/buildinfo?buildID=2437715 Since eln is build with -march=x86-64-v3 this might be a good testing environment. Please let me know if you are

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #6 from Mark Wielaard --- (In reply to Mark Wielaard from comment #5) > I'll add it to the next fedora rawhide valgrind build so we can test it a > bit more. There is now valgrind-3.22.0-8.fc41 with this and some other (x86-64-v3) fixes to

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Florian Weimer
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #4 from Florian Weimer --- Based on a further suggestion from H.J., I put the strcmp implementation posted here into glibc and ran its strcmp test suite against it. It passes. For such a simple implementation it should have really good

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=485487 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Florian Weimer
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #3 from Florian Weimer --- H.J. suggests to use the implementation from (adapted for x86-64). I can submit that

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Florian Weimer
https://bugs.kde.org/show_bug.cgi?id=485487 Florian Weimer changed: What|Removed |Added CC||fwei...@redhat.com --- Comment #2 from

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

2024-04-13 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark