diff options
| author | Mike Hommey <mh@glandium.org> | 2025-08-22 14:55:42 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-22 05:55:42 +0000 |
| commit | be179d069664ce03c485e49fa1f6e2ca3d6286fa (patch) | |
| tree | 21c21446f6985d04ae7683a4a1791428965c5c86 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py | |
| parent | dee25a8a8e616bcb473cced720870223bbebc2cf (diff) | |
| download | llvm-be179d069664ce03c485e49fa1f6e2ca3d6286fa.zip llvm-be179d069664ce03c485e49fa1f6e2ca3d6286fa.tar.gz llvm-be179d069664ce03c485e49fa1f6e2ca3d6286fa.tar.bz2 | |
Be explicit about what libstdc++ C++11 ABI to use (#154447)
libstdc++ can be configured to default to a different C++11 ABI, and
when the system that is used to build clang has a different default than
the system used to build a clang plugin, that leads to uses of different
ABIs, leading to breakage (missing symbols) when using clang APIs that
use types like std::string.
We arbitrarily choose to default to the old ABI, but the user can opt-in
to the new ABI. The important part is that whichever is picked is
reflected in llvm-config's output.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions