[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-06-26 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #11 from Paul Floyd --- The real answer for this is to not use LTO. Do you have evidence showing that there is a big benefit to using it? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-06-26 Thread Michal
https://bugs.kde.org/show_bug.cgi?id=469049 Michal changed: What|Removed |Added CC||hramr...@gmail.com --- Comment #10 from Michal --- Cr

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-05-05 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #8 from Paul Floyd --- Created attachment 158529 --> https://bugs.kde.org/attachment.cgi?id=158529&action=edit Patch for lto build on ppnbe With this == 744 tests, 14 stderr failures, 5 stdout failures, 0 stderrB failures, 2 stdoutB fail

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #7 from Paul Floyd --- I was wondering about the GCC version - the system that I reproduced on has GCC 12.2 so quite recent. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

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

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #6 from Mark Wielaard --- (In reply to Paul Floyd from comment #5) > This is an LTO issue. On gccfarm gcc203 which is > > paulf@gcc203:~/scratch/valgrind$ lscpu > Architecture:ppc64 > CPU op-mode(s):32-bit, 64-bit >

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #5 from Paul Floyd --- This is an LTO issue. On gccfarm gcc203 which is paulf@gcc203:~/scratch/valgrind$ lscpu Architecture:ppc64 CPU op-mode(s):32-bit, 64-bit Byte Order:Big Endian Then with ./configu

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #4 from Mark Wielaard --- (In reply to Paul Floyd from comment #2) > (In reply to Mark Wielaard from comment #1) > > There is a debian ppc64(be) system for builder.sourceware.org which builds: > > https://builder.sourceware.org/buildbot/#/bu

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 --- Comment #3 from Paul Floyd --- (In reply to Dirk Mueller from comment #0) > /tmp/ccAV30QW.ltrans8.ltrans.o:/home/abuild/rpmbuild/BUILD/valgrind-3.20.0/ > memcheck/../coregrind/m_machine.c:2393: undefined reference to > `vgPlain_unknown_SP_update' >

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

2023-04-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=469049 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd

[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20

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