• Locked Locked
  • Replies 17 replies
  • Subscribers 119 subscribers
  • Views 15948 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem in generating position independent code with out TEXTREL

Darisi V SATISH BABU
Note: This was originally posted on 12th August 2010 at http://forums.arm.com

Hi Experts,

Issue:Not able to remove TEXTREL from our static library generated with --apcs /fpic option using armcc(RVCT 4.0 build 771  tool chain)

Description:
    We compiled our codebase(some modules with handwritten assembly) using armcc(RVCT 4.0 build 771  tool chain) to get static libraries, and then these are used by gstreamer module which further compiles using the above generated libraries with wrappers using GCC tool chain and creates shared objects(.so).

Even though we use equivalent --apcs /fpic compile time option during static library creation to remove position independent code, the TEXTREL are not going from library.
When we disable the (handwritten assembly) in the above mentioned codebase, TEXTRELs go away.
As there are lot of handwritten ARM assembly functions,its difficult to enable one by one and compile and check. :unsure:

So,Experts please throw some light on this issue.


Thanks In Advance,
satish
Parents
  • Note: This was originally posted on 17th August 2010 at http://forums.arm.com

    You're using what's known as "embedded assembly".  What you write inside the embedded asm functions has pretty much the same rules as a .s file, but armcc will generate some EXPORT/PROC/ENDP directives for you and some IMPORT directives if you're using __cpp(...).

    It's not using the IMPORT directive per se that is generating the relocation; it's what you do with the imported symbol (DCD or LDR rx,= in my example above).  If know the symbols being used by the unwanted relocations and can post the embedded asm lines that mention them; we might be able to suggest what you could do instead.


    I am also facing similar relocation issue. i am facing issue in normal c code where assembly has been disabled. Code is compiled using RVCT4.0 build 771. I tried with all possible options like --apcs /fpic,  --apcs=/ropi --lower_ropi etc but it has no effect.
    Is there any utility or method using which we can identify, the parts of code responsible for these?
Reply
  • Note: This was originally posted on 17th August 2010 at http://forums.arm.com

    You're using what's known as "embedded assembly".  What you write inside the embedded asm functions has pretty much the same rules as a .s file, but armcc will generate some EXPORT/PROC/ENDP directives for you and some IMPORT directives if you're using __cpp(...).

    It's not using the IMPORT directive per se that is generating the relocation; it's what you do with the imported symbol (DCD or LDR rx,= in my example above).  If know the symbols being used by the unwanted relocations and can post the embedded asm lines that mention them; we might be able to suggest what you could do instead.


    I am also facing similar relocation issue. i am facing issue in normal c code where assembly has been disabled. Code is compiled using RVCT4.0 build 771. I tried with all possible options like --apcs /fpic,  --apcs=/ropi --lower_ropi etc but it has no effect.
    Is there any utility or method using which we can identify, the parts of code responsible for these?
Children
No data