dev-debug/valgrind: stop filtering LTO

mjw pointed out that Valgrind has a --enable-lto configure arg but it also
seems to work well nowadays. Valgrind is a special-case so use it.

Signed-off-by: Sam James <sam@gentoo.org>
This commit is contained in:
Sam James
2024-04-25 09:54:03 +01:00
parent 6bc8f48fa5
commit 6ada69a5bb
2 changed files with 4 additions and 2 deletions
@@ -75,6 +75,8 @@ src_configure() {
--with-gdbscripts-dir="${EPREFIX}"/usr/share/gdb/auto-load
)
tc-is-lto && myconf+=( --enable-lto )
# Respect ar, bug #468114
tc-export AR
@@ -87,7 +89,6 @@ src_configure() {
# -fstack-protector-strong See -fstack-protector (bug #620402)
# -m64 -mx32 for multilib-portage, bug #398825
# -fharden-control-flow-redundancy: breaks runtime ('jump to the invalid address stated on the next line')
# -flto* fails to build, bug #858509
filter-flags -fomit-frame-pointer
filter-flags -fstack-protector
filter-flags -fstack-protector-all
+2 -1
View File
@@ -75,6 +75,8 @@ src_configure() {
--with-gdbscripts-dir="${EPREFIX}"/usr/share/gdb/auto-load
)
tc-is-lto && myconf+=( --enable-lto )
# Respect ar, bug #468114
tc-export AR
@@ -87,7 +89,6 @@ src_configure() {
# -fstack-protector-strong See -fstack-protector (bug #620402)
# -m64 -mx32 for multilib-portage, bug #398825
# -fharden-control-flow-redundancy: breaks runtime ('jump to the invalid address stated on the next line')
# -flto* fails to build, bug #858509
filter-flags -fomit-frame-pointer
filter-flags -fstack-protector
filter-flags -fstack-protector-all