dev-qt/qtwebengine: also filter -march w/ clang on arm64

For a different reason than originally, but feel we're better off
doing this unless Qt starts testing this.

Note that it doesn't mean no native optimizations at all, qtwebengine
still enables several things for detection+usage at runtime.

Closes: https://bugs.gentoo.org/970048
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
This commit is contained in:
Ionen Wolkens
2026-02-13 23:12:35 -05:00
parent c34e92f5d6
commit 82ad3c86a7
5 changed files with 25 additions and 25 deletions

View File

@@ -254,11 +254,11 @@ src_configure() {
ewarn "-g2+/-ggdb* *FLAGS replaced with -g1 (enable USE=custom-cflags to keep)"
fi
# Built helpers segfault when using (at least) -march=armv8-a+pauth
# (bug #920555, #920568 -- suspected gcc bug). For now, filter all
# for simplicity. Override with USE=custom-cflags if wanted, please
# report if above -march works again so can cleanup.
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
# Qt normally ignores users *FLAGS specifically for qtwebengine, and
# does not really support passing -march -- qt6-build.eclass has some
# checks to ensure working flags with amd64, but that does not exist
# for arm64 and can lead to problems (bug #920555,#920568,#970048)
use arm64 && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may

View File

@@ -256,11 +256,11 @@ src_configure() {
ewarn "-g2+/-ggdb* *FLAGS replaced with -g1 (enable USE=custom-cflags to keep)"
fi
# Built helpers segfault when using (at least) -march=armv8-a+pauth
# (bug #920555, #920568 -- suspected gcc bug). For now, filter all
# for simplicity. Override with USE=custom-cflags if wanted, please
# report if above -march works again so can cleanup.
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
# Qt normally ignores users *FLAGS specifically for qtwebengine, and
# does not really support passing -march -- qt6-build.eclass has some
# checks to ensure working flags with amd64, but that does not exist
# for arm64 and can lead to problems (bug #920555,#920568,#970048)
use arm64 && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may

View File

@@ -255,11 +255,11 @@ src_configure() {
ewarn "-g2+/-ggdb* *FLAGS replaced with -g1 (enable USE=custom-cflags to keep)"
fi
# Built helpers segfault when using (at least) -march=armv8-a+pauth
# (bug #920555, #920568 -- suspected gcc bug). For now, filter all
# for simplicity. Override with USE=custom-cflags if wanted, please
# report if above -march works again so can cleanup.
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
# Qt normally ignores users *FLAGS specifically for qtwebengine, and
# does not really support passing -march -- qt6-build.eclass has some
# checks to ensure working flags with amd64, but that does not exist
# for arm64 and can lead to problems (bug #920555,#920568,#970048)
use arm64 && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may

View File

@@ -255,11 +255,11 @@ src_configure() {
ewarn "-g2+/-ggdb* *FLAGS replaced with -g1 (enable USE=custom-cflags to keep)"
fi
# Built helpers segfault when using (at least) -march=armv8-a+pauth
# (bug #920555, #920568 -- suspected gcc bug). For now, filter all
# for simplicity. Override with USE=custom-cflags if wanted, please
# report if above -march works again so can cleanup.
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
# Qt normally ignores users *FLAGS specifically for qtwebengine, and
# does not really support passing -march -- qt6-build.eclass has some
# checks to ensure working flags with amd64, but that does not exist
# for arm64 and can lead to problems (bug #920555,#920568,#970048)
use arm64 && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may

View File

@@ -254,11 +254,11 @@ src_configure() {
ewarn "-g2+/-ggdb* *FLAGS replaced with -g1 (enable USE=custom-cflags to keep)"
fi
# Built helpers segfault when using (at least) -march=armv8-a+pauth
# (bug #920555, #920568 -- suspected gcc bug). For now, filter all
# for simplicity. Override with USE=custom-cflags if wanted, please
# report if above -march works again so can cleanup.
use arm64 && tc-is-gcc && filter-flags '-march=*' '-mcpu=*'
# Qt normally ignores users *FLAGS specifically for qtwebengine, and
# does not really support passing -march -- qt6-build.eclass has some
# checks to ensure working flags with amd64, but that does not exist
# for arm64 and can lead to problems (bug #920555,#920568,#970048)
use arm64 && filter-flags '-march=*' '-mcpu=*'
fi
# chromium passes this by default, but qtwebengine does not and it may