* problem facing while upgrading from v2.13 to v2.16 of binutils
@ 2006-03-14 15:53 Inder
2006-03-16 8:48 ` Nick Clifton
0 siblings, 1 reply; 3+ messages in thread
From: Inder @ 2006-03-14 15:53 UTC (permalink / raw)
To: binutils
Hi all
We are upgrding our source base from the previous version of biutils
to a more recent once.
My target is 'arm-elf'
-------------------------------- TEST SOURCE (test.s)
-----------------------------------
.section .text.__GLOBAL__D__dummyconstructor,"ax",%progbits
.align 2
.ascii "__GLOBAL__D__dummyconstructor\000"
.align 2
.word -16777172
.type __GLOBAL__D__dummyconstructor, %function
__GLOBAL__D__dummyconstructor:
mov r0, r0
mov r0, r0
mov r0, r0
mov r0, r0
-------------------------------- --------------------------------
--------------------------------
code when compiler with --version
GNU assembler 2.16.1
gives the following output
--------------------------------------------------------------------------------------------------------
arm-elf-objdump -D test.o
--------------------------------------------------------------------------------------------------------
00000000 <.text.__GLOBAL__D__dummyconstructor>:
0: 4c475f5f mcrrmi 15, 5, r5, r7, cr15
4: 4c41424f sfmmi f4, 2, [r1], {79}
8: 5f445f5f swipl 0x00445f5f
c: 6d75645f cfldrdvs mvd6, [r5, #-380]!
10: 6f63796d swivs 0x0063796d
14: 7274736e rsbvcs r7, r4, #-1207959551 ; 0xb8000001
18: 6f746375 swivs 0x00746375
1c: 00000072 andeq r0, r0, r2, ror r0
20: ff00002c swinv 0x0000002c
24: e1a00000 nop (mov r0,r0)
28: e1a00000 nop (mov r0,r0)
2c: e1a00000 nop (mov r0,r0)
30: e1a00000 nop (mov r0,r0)
34: e1a00000 nop (mov r0,r0)
38: e1a00000 nop (mov r0,r0)
3c: e1a00000 nop (mov r0,r0)
40: e1a00000 nop (mov r0,r0)
44: e1a00000 nop (mov r0,r0)
48: e1a00000 nop (mov r0,r0)
4c: e1a00000 nop (mov r0,r0)
--------------------------------------------------------------------------------------------------------
The function (__GLOBAL__D__dummyconstructor) is not define any where.
while with the previous version of binutils v2.13
it gives the following output:
--------------------------------------------------------------------------------------------------------
Disassembly of section .text._GLOBAL__I__Z7errFuncP12EwsContext_sjPPKcj:
00000000 <__GLOBAL__D__dummyconstructor-0x24>:
0: 4c475f5f mcrrmi 15, 5, r5, r7, cr15
4: 4c41424f sfmmi f4, 2, [r1], {79}
8: 5f445f5f swipl 0x00445f5f
c: 6d75645f cfldrdvs mvd6, [r5, #-380]!
10: 6f63796d swivs 0x0063796d
14: 7274736e rsbvcs r7, r4, #-1207959551 ; 0xb8000001
18: 6f746375 swivs 0x00746375
1c: 00000072 andeq r0, r0, r2, ror r0
20: ff00002c swinv 0x0000002c
00000024 <__GLOBAL__D__dummyconstructor>:
24: e1a00000 nop (mov r0,r0)
28: e1a00000 nop (mov r0,r0)
2c: e1a00000 nop (mov r0,r0)
30: e1a00000 nop (mov r0,r0)
34: e1a00000 nop (mov r0,r0)
38: e1a00000 nop (mov r0,r0)
3c: e1a00000 nop (mov r0,r0)
40: e1a00000 nop (mov r0,r0)
44: e1a00000 nop (mov r0,r0)
48: e1a00000 nop (mov r0,r0)
4c: e1a00000 nop (mov r0,r0)
--------------------------------------------------------------------------------------------------------
Some thing strange is happeing with the function in the new version of binutils,
it actually not emitting the function.
Can anybody tell me if its a problem with the new binutils or am i
missing something.
--
Thanks,
Inder
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problem facing while upgrading from v2.13 to v2.16 of binutils
2006-03-14 15:53 problem facing while upgrading from v2.13 to v2.16 of binutils Inder
@ 2006-03-16 8:48 ` Nick Clifton
2006-03-16 19:10 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Nick Clifton @ 2006-03-16 8:48 UTC (permalink / raw)
To: Inder; +Cc: binutils
Hi Inder,
> -------------------------------- TEST SOURCE (test.s)
> .section .text.__GLOBAL__D__dummyconstructor,"ax",%progbits
> .align 2
> .ascii "__GLOBAL__D__dummyconstructor\000"
> .align 2
> .word -16777172
> .type __GLOBAL__D__dummyconstructor, %function
> __GLOBAL__D__dummyconstructor:
> mov r0, r0
> mov r0, r0
> mov r0, r0
> mov r0, r0
The problem, I suspect is that you are missing a ".global" directive in
the above assembler source. so if you add:
.global __GLOBAL__D__dummyconstructor
jut after the ".type" line, I think that you might see the disassembly
that you are expecting.
Cheers
Nick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problem facing while upgrading from v2.13 to v2.16 of binutils
2006-03-16 8:48 ` Nick Clifton
@ 2006-03-16 19:10 ` Daniel Jacobowitz
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Jacobowitz @ 2006-03-16 19:10 UTC (permalink / raw)
To: Nick Clifton; +Cc: Inder, binutils
On Thu, Mar 16, 2006 at 09:00:15AM +0000, Nick Clifton wrote:
> Hi Inder,
>
> >-------------------------------- TEST SOURCE (test.s)
> > .section .text.__GLOBAL__D__dummyconstructor,"ax",%progbits
> > .align 2
> > .ascii "__GLOBAL__D__dummyconstructor\000"
> > .align 2
> > .word -16777172
> > .type __GLOBAL__D__dummyconstructor, %function
> >__GLOBAL__D__dummyconstructor:
> > mov r0, r0
> > mov r0, r0
> > mov r0, r0
> > mov r0, r0
>
> The problem, I suspect is that you are missing a ".global" directive in
> the above assembler source. so if you add:
>
> .global __GLOBAL__D__dummyconstructor
>
> jut after the ".type" line, I think that you might see the disassembly
> that you are expecting.
Shouldn't it show up in the obdump output even if it's a local symbol?
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-03-16 16:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-03-14 15:53 problem facing while upgrading from v2.13 to v2.16 of binutils Inder
2006-03-16 8:48 ` Nick Clifton
2006-03-16 19:10 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).