Re: [Valgrind-developers] ppc64-linux coming to life

[Julian S. <js...@ac...>]

On Wednesday 18 January 2006 23:41, Dave Nomura wrote:
> I am able to compile with the simple gcc invocation that you've given
> below.  I did some experimentation with the gcc invocation generated by
> make and it appears that it is the -gstabs that causes the problem.
>
> The assembler file around line 285 looks like:280         .long 0
>      281         .byte 0,0,0,1,128,1,0,1
>      282         .size   main,.-.L.main
>      283         .stabs  "a:(10,20)",128,0,0,112
>      284         .stabs  "b:(10,20)",128,0,0,120
>      285         .stabn  192,0,0,main-.L.main
>      286         .stabn  224,0,0,.Lscope1-.L.main
>
> If I compare this to the same test program built in the 3.1.0 ppc32
> valgrind it looks like:
>      256         .size   main, .-main
>      257         .stabs  "a:(10,20)",128,0,0,8
>      258         .stabs  "b:(10,20)",128,0,0,12
>      259         .stabn  192,0,0,main-main
>      260         .stabn  224,0,0,.Lscope1-main
>
> I don't know enough about the assembler to know what this gibberish
> means but the assembler seems to be complaining about
> 	 "main-.L.main" vs "main-main"

That might be a bug in gcc's .stabs generation for ppc64.
Shouldn't the first line be

>      285         .stabn  192,0,0,.L.main-.L.main

?

It doesn't sound unreasonable for the assembler to complain about having to
compute the difference in addresses between two symbols in different
sections.

J