diff options
| author |   Sam James <sam@gentoo.org> | 2024-09-30 02:25:23 +0100 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2024-09-30 02:51:44 +0100 |
| commit | ea474da34fe1f904936f0f6b6e52d91364c36c95 (patch) | |
| tree | f5d549fd9ee0fc9e45476c65203532eb32195d4c /eclass/systemd.eclass | |
| parent | toolchain.eclass: check CXXFLAGS too in -march=native sanity check (diff) | |
| download | gentoo-ea474da34fe1f904936f0f6b6e52d91364c36c95.tar.gz gentoo-ea474da34fe1f904936f0f6b6e52d91364c36c95.tar.bz2 gentoo-ea474da34fe1f904936f0f6b6e52d91364c36c95.zip | |
toolchain.eclass: unset _GLIBCXX_ASSERTIONS for stage1 with D bootstrap
When bootstrapping D for >= GCC 12 - where we enable _GLIBCXX_ASSERTIONS
by default for USE=hardened - using GCC 11, we run into trouble where
an implementation detail of _GLIBCXX_ASSERTIONS changed: see PR104807,
r12-7504-gd3a757af21ac33, and r12-7522-g4cb935cb69f120.
Workaround this by just disabling _GLIBCXX_ASSERTIONS for the stage 1
compiler (where it's not particularly important anyway) when USE=hardened
and we're building D. We could make this more conditional if needed
but I don't think it's worth it. In fact, maybe we should do this
unconditionally for a minor speed boost in building.
Bug: https://gcc.gnu.org/PR104807
Bug: https://bugs.gentoo.org/940470
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'eclass/systemd.eclass')
0 files changed, 0 insertions, 0 deletions