Summary: | move ppc64 to ELFv2 ABI? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Profiles | Assignee: | ppc64 architecture team <ppc64> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | erhard_f, gyakovlev, toolchain |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=704784 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas K. Hüttel
![]() ![]() One benefit would be that lld can be used as linker and hence llvm/clang/lld toolchain on glibc-based profiles. LLD does not do ELFv1 ABI. musl ppc64 is already ELFv2 ABI so no problem here. ppc64be should not be elfv2 due to some toolcain assumptions. Poc64le is already elfv2. I’ll dump more information why elfv2 should not be used. It can be used and we can even have a profile for that, but tldr is that adding an extra incompatibility on top of not very compatible triplet will create a bit of chaos. |