Displaying 3 results from an estimated 3 matches for "ppc_abi_elfv2".
Did you mean:
ppc_abi_elfv1
2014 Jul 30
4
[LLVMdev] [PowerPC] ABI questions
...arwinABI, SVR4ABI and ELFv2ABI.
- The CodeGenerator documentation claims that the AIX PowerPC ABI is
followed (with some deviations). Is this refering to the DarwinABI?
- In a recent commit a TargetABI value and enumeration was added to
PPCSubtarget which contains PPC_ABI_UNKNOWN, PPC_ABI_ELFv1 and
PPC_ABI_ELFv2. For 64-bit non-Darwin the TargetABI value is set to
either ELF-variant in resetSubtargetFeatures(...) based on endianess
(unless explicitly set previously). As I understand it ELFv2 is a new
ABI but which ABI does ELFv1 map to?
- Since isSVR4ABI() is defined as !isDarwin() it currently is possible...
2014 Jul 31
2
[LLVMdev] [PowerPC] ABI questions
...> > is
> > followed (with some deviations). Is this refering to the DarwinABI?
>
> No, that's the ELFv1 ABI.
>
> > - In a recent commit a TargetABI value and enumeration was added to
> > PPCSubtarget which contains PPC_ABI_UNKNOWN, PPC_ABI_ELFv1 and
> > PPC_ABI_ELFv2. For 64-bit non-Darwin the TargetABI value is set to
> > either ELF-variant in resetSubtargetFeatures(...) based on
> > endianess
> > (unless explicitly set previously). As I understand it ELFv2 is a
> > new
> > ABI but which ABI does ELFv1 map to?
>
> I hope th...
2014 Jul 30
2
[LLVMdev] [PowerPC] ABI questions
...t isn't ELFv1?
Just to be clear the document I'm talking about is:
http://llvm.org/docs/CodeGenerator.html#llvm-powerpc-abi
- David
>> - In a recent commit a TargetABI value and enumeration was added to
>> PPCSubtarget which contains PPC_ABI_UNKNOWN, PPC_ABI_ELFv1 and
>> PPC_ABI_ELFv2. For 64-bit non-Darwin the TargetABI value is set to
>> either ELF-variant in resetSubtargetFeatures(...) based on endianess
>> (unless explicitly set previously). As I understand it ELFv2 is a new
>> ABI but which ABI does ELFv1 map to?
>
> I hope the above makes it clearer...