[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #30 from Дилян Палаузов --- For the record, with /usr/local/etc/config.site containing CC=clang CXX=clang++ CFLAGS="-Wall -pipe -O3" CXXFLAGS="-pipe -O3" LDFLAGS="-L/usr/local/lib64 -Wl,-O1,-s -fuse-ld=gold" and this changes: diff --git

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #29 from Philippe Waroquiers --- Created attachment 111644 --> https://bugs.kde.org/attachment.cgi?id=111644=edit tentative patch to support llvm+lto With the attached patch, llvm+lto works till the link

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #28 from Philippe Waroquiers --- (In reply to Philippe Waroquiers from comment #27) > So, when I have a little bit of time, I will install llvm > and see if I can make that work. At least on Ubunty 17.10,

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #27 from Philippe Waroquiers --- (In reply to Дилян Палаузов from comment #26) > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84934#c1 suggests that > distributions are supposed to install the LTO-plugin on

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #26 from Дилян Палаузов --- With python 3.6, doing "./configure --with-lto --enable-optimizations && make" compiles with -flto, but calls ranlib/ar, not gcc-ranlib or gcc-ar. Why can python-lto live without

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #25 from Philippe Waroquiers --- (In reply to Дилян Палаузов from comment #23) > I just verified, that LLVM does not install gcc-ar and gcc-ranlib, but > llvm-ar and llvm-ranlib . > > So to make LTO work with

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Philippe Waroquiers changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #23 from Дилян Палаузов --- I just verified, that LLVM does not install gcc-ar and gcc-ranlib, but llvm-ar and llvm-ranlib . So to make LTO work with Clang, on systems where GCC is not installed, either llvm-ar

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Дилян Палаузов changed: What|Removed |Added Resolution|FIXED |---

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Philippe Waroquiers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #20 from Дилян Палаузов --- With the change below m_libcsetjmp.c links on amd64 correctly with LTO. Is the change equivalent (apart from cheating gcc restoring rax in in VG_MINIMAL_LONGJMP)? Is volatile after

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #19 from Дилян Палаузов --- A waring like "a plugin is needed to handle lto objects" suggests that nm/ar do not find the LTO plugin. For an object file compiled with LTO (and -fno-fat-lto-objects), `nm x.o` will

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #18 from Philippe Waroquiers --- (In reply to Дилян Палаузов from comment #16) > People either want to compile everything with LTO, or nothing with LTO, or > they don't know about LTO. Humph, that looks like a

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #17 from Дилян Палаузов --- Having a global /usr/local/etc/config.site file is not necessary. It is possible to put the file somewhere else and set in env CONFIG_SITE for the current session where the file is

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #16 from Дилян Палаузов --- People either want to compile everything with LTO, or nothing with LTO, or they don't know about LTO. Modifying /usr/local/etc/config.site is not the only way, calling

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #15

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #14 from Дилян Палаузов --- Autoconf users willing to compile everything with LTO just by calling ./configure put in /usr/local/etc/config.site: CFLAGS="-O3 -fno-fat-lto-objects -flto" CXXFLAGS="-O3

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Philippe Waroquiers changed: What|Removed |Added Attachment #88247|0 |1

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 --- Comment #12 from Philippe Waroquiers --- Note that I am busy doing a (I hope ok to commit soon)patch in valgrind source code so that -flto works 'out of the box'. The patch currently gives working tools on Debian 9

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

https://bugs.kde.org/show_bug.cgi?id=338252 Austin English changed: What|Removed |Added CC|