Displaying 3 results from an estimated 3 matches for "mgot".
Did you mean:
got
2012 Dec 06
2
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
Older targets like Mips had/have assemblers and ABIs that carry a lot of baggage.
The small bit of baggage that is giving me fits is that MipsELFObjectWriter needs to know the relocation model (static,pic,cpic), whether we are using xgot (-mgot), which abi (old,new), which architecture (32r[123],64[123]), which if any coprocessor or extention instructions are used (mips16,micromips,etc.).
I shouldn't have to muck with base classes to handle esoteric target specific issues such as these.
<target>ELFObjectWriteris used for direc...
2012 Dec 07
0
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
...carter at mips.com> wrote:
> Older targets like Mips had/have assemblers and ABIs that carry a lot of
> baggage.
>
> The small bit of baggage that is giving me fits is that MipsELFObjectWriter
> needs to know the relocation model (static,pic,cpic), whether we are using
> xgot (-mgot), which abi (old,new), which architecture (32r[123],64[123]),
> which if any coprocessor or extention instructions are used
> (mips16,micromips,etc.).
So the mips assembler has command line options like -fPIC?
Cheers,
Rafael
2012 Dec 07
2
[LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter
...carter at mips.com> wrote:
> Older targets like Mips had/have assemblers and ABIs that carry a lot of
> baggage.
>
> The small bit of baggage that is giving me fits is that MipsELFObjectWriter
> needs to know the relocation model (static,pic,cpic), whether we are using
> xgot (-mgot), which abi (old,new), which architecture (32r[123],64[123]),
> which if any coprocessor or extention instructions are used
> (mips16,micromips,etc.).
So the mips assembler has command line options like -fPIC?
Cheers,
Rafael