aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorAlex Rønne Petersen <alex@alexrp.com>2024-09-20 02:53:03 +0200
committerGitHub <noreply@github.com>2024-09-20 08:53:03 +0800
commit72a218056d68b7aa65ab3eda56837117bb59f11a (patch)
tree654fc66510f25991b3c03523fbfe642e952945d7 /lldb/source/Plugins/ScriptInterpreter/Python
parentb3533a156da92262eb19429d8c12f53e87f5ccec (diff)
downloadllvm-72a218056d68b7aa65ab3eda56837117bb59f11a.zip
llvm-72a218056d68b7aa65ab3eda56837117bb59f11a.tar.gz
llvm-72a218056d68b7aa65ab3eda56837117bb59f11a.tar.bz2
[llvm][Triple] Add `Environment` members and parsing for glibc/musl parity. (#107664)
This adds support for: * `muslabin32` (MIPS N32) * `muslabi64` (MIPS N64) * `muslf32` (LoongArch ILP32F/LP64F) * `muslsf` (LoongArch ILP32S/LP64S) As we start adding glibc/musl cross-compilation support for these targets in Zig, it would make our life easier if LLVM recognized these triples. I'm hoping this'll be uncontroversial since the same has already been done for `musleabi`, `musleabihf`, and `muslx32`. I intentionally left out a musl equivalent of `gnuf64` (LoongArch ILP32D/LP64D); my understanding is that Loongson ultimately settled on simply `gnu` for this much more common case, so there doesn't *seem* to be a particularly compelling reason to add a `muslf64` that's basically deprecated on arrival. Note: I don't have commit access.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions