This is the mail archive of the
crossgcc@sources.redhat.com
mailing list for the crossgcc project.
See the CrossGCC FAQ for lots
more information.
ARM/Thumb Interwork
- From: "Bhattacharya, Soubhik" <soubhik_bhattacharya at mentorg dot com>
- To: crossgcc at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: Wed, 29 Oct 2003 12:10:10 +0530
- Subject: ARM/Thumb Interwork
- Organization: Mentor Graphics
hi all,
i'm working on a tool that reads and analyzes arm/thumb elf files
produced by gcc. to do this i need to be able to distinguish between arm
and thumb code fragments.
arm eabi 2.0 extends generic elf standard to specify how to distinguish
between arm and thumb code fragments. however, it seems that the cross
gcc that i have does not follow arm eabi 2.0. so what is the convention
that gcc follows and how to learn about it?
with the help of 'objdump', i cud see that calls to arm functions from
thumb code and vice versa is supported thru special wrapper functions
(__<func>_from_thumb and __<func>_from_arm). this technique will not
work for a function having a mix of arm and thumb code. are such
functions supported? what happens if a relocatable object is generated
with -mcallee-super-interworking?
soubhik.
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com