Lee Noar wrote:
Do you not see this in the archive you have built? PIC code is easy to
spot as it has an instruction pattern as follows at the beginning of the
function:
ADD r7,pc,r7
LDMIA r8,{r7,r8}
LDR r8,[r8,#0]
LDR r7,[r8,r7,LSL#4]
Perhaps this is deliberate by the developers to make the build easier (I
don't know if it actually does) or maybe an oversight that hasn't shown
up on other platforms.
Can anyone else confirm if they are seeing PIC code in the libglib
static archive. Actually, assuming you're using a code viewer (like Zap)
in RISC OS, it's probably easier to build Vala and search the binary -
objects stored in archives aren't always word aligned and don't
disassemble correctly.
That's ok, objdump knows what to do:
/home/riscos/cross/bin/arm-unknown-riscos-objdump -d
/home/riscos/env/lib/libglib-2.0.a
The formatting is bit different:
30: e08f7007 add r7, pc, r7
34: e8970180 ldmia r7, {r7, r8}
38: e5988000 ldr r8, [r8]
3c: e7987207 ldr r7, [r8, r7, lsl #4]
But yes, obviously I can see that code too. That is
from localcharset.o. Why it is like this, I don't know.
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
