diff options
| author | Michael Kruse <llvm-project@meinersbur.de> | 2025-08-27 10:10:48 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-27 10:10:48 +0200 |
| commit | 88f8ab01b5855bbd7375b7a3d83d9a78d77f3fdf (patch) | |
| tree | 77196c1597336b2b8a171048314fa57fcd4c0159 /clang/lib/AST/ByteCode/Compiler.cpp | |
| parent | 6551f7f1cd623e04e30c06eb58a85ef2fd768be9 (diff) | |
| download | llvm-88f8ab01b5855bbd7375b7a3d83d9a78d77f3fdf.zip llvm-88f8ab01b5855bbd7375b7a3d83d9a78d77f3fdf.tar.gz llvm-88f8ab01b5855bbd7375b7a3d83d9a78d77f3fdf.tar.bz2 | |
[Flang-RT][OpenMP] Define _GLIBCXX_NO_ASSERTIONS (#155440)
Since GCC 15.1, libstdc++ enabled assertions/hardening by default in
non-optimized (-O0) builds [1]. That is, _GLIBCXX_ASSERTIONS is defined
in the libstdc++ headers itself so defining/undefining it on the
compiler command line no longer has an effect in non-optimized builds.
As the commit message[2] suggests, define _GLIBCXX_NO_ASSERTIONS
instead.
For libstdc++ headers before 15.1, -U_GLIBCXX_ASSERTIONS still has to be
on the command line as well.
Defining _GLIBCXX_NO_ASSERTIONS was previously proposed in #152223
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112808
[2] https://github.com/gcc-mirror/gcc/commit/361d230fd7800a7e749aba8ed020f54f5c26d504
Diffstat (limited to 'clang/lib/AST/ByteCode/Compiler.cpp')
0 files changed, 0 insertions, 0 deletions