search for: mvxwork

Hi Rafael, There are a lot of flags. Here are the ones you ask about: -KPIC, -call_shared generate SVR4 position independent code -call_nonpic generate non-PIC code that can operate with DSOs -mvxworks-pic generate VxWorks position independent code -non_shared do not generate code that can operate with DSOs -xgot assume a 32 bit GOT Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Remember, this issue is not whether the direct or standalone assembler c...

...2 18:57, Carter, Jack <jcarter at mips.com> wrote: > Hi Rafael, > > There are a lot of flags. Here are the ones you ask about: > > -KPIC, -call_shared generate SVR4 position independent code > -call_nonpic generate non-PIC code that can operate with DSOs > -mvxworks-pic generate VxWorks position independent code > -non_shared do not generate code that can operate with DSOs > -xgot assume a 32 bit GOT > > Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Awesome. As a though exe...

...2 18:57, Carter, Jack <jcarter at mips.com> wrote: > Hi Rafael, > > There are a lot of flags. Here are the ones you ask about: > > -KPIC, -call_shared generate SVR4 position independent code > -call_nonpic generate non-PIC code that can operate with DSOs > -mvxworks-pic generate VxWorks position independent code > -non_shared do not generate code that can operate with DSOs > -xgot assume a 32 bit GOT > > Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. Awesome. As a though exe...

...ter at mips.com> wrote: >> Hi Rafael, >> >> There are a lot of flags. Here are the ones you ask about: >> >> -KPIC, -call_shared generate SVR4 position independent code >> -call_nonpic generate non-PIC code that can operate with DSOs >> -mvxworks-pic generate VxWorks position independent code >> -non_shared do not generate code that can operate with DSOs >> -xgot assume a 32 bit GOT >> >> Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. > &g...

On 6 December 2012 17:49, Carter, Jack <jcarter 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

...arter at mips.com> wrote: >> Hi Rafael, >> >> There are a lot of flags. Here are the ones you ask about: >> >> -KPIC, -call_shared generate SVR4 position independent code >> -call_nonpic generate non-PIC code that can operate with DSOs >> -mvxworks-pic generate VxWorks position independent code >> -non_shared do not generate code that can operate with DSOs >> -xgot assume a 32 bit GOT >> >> Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. > >...

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

...arter at mips.com> wrote: >> Hi Rafael, >> >> There are a lot of flags. Here are the ones you ask about: >> >> -KPIC, -call_shared generate SVR4 position independent code >> -call_nonpic generate non-PIC code that can operate with DSOs >> -mvxworks-pic generate VxWorks position independent code >> -non_shared do not generate code that can operate with DSOs >> -xgot assume a 32 bit GOT >> >> Just to make things fun, the SGI notion of cpic (call pic) fits gnu's -call_nonpic. > >...