|
From: Dave N. <dc...@us...> - 2006-02-08 19:13:41
|
I sent a message about an assembler error in helgrind/tests/allok.c back
in January. It appears that gcc is having problems with -gstab. Julian
acknowledged that this is a problem. Would it be possible to remove
this test (until the problem is fixed) from the build of helgrind? This
is preventing me from using nightly builds.
I suspect that I am going to have similar problems using the nightly
builds on the PPC970 where I reported a problem I am seeing having to do
with suppression that I need:
index-not-intercepted-early-enough-HACK-4
See end of 3_1_BUGSTATUS.txt.
-------- Original Message --------
Subject: Re: [Valgrind-developers] ppc64-linux coming to life
Date: Wed, 18 Jan 2006 15:41:34 -0800
From: Dave Nomura <dc...@us...>
To: val...@li...
CC: Julian Seward <js...@ac...>
References: <200...@ac...>
<43C...@us...> <200...@ac...>
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"
gcc -v gives me the following information about the assembler invocation:
GNU C version 3.4.3 20050227 (Red Hat 3.4.3-22.1) (ppc64-redhat-linux)
compiled by GNU C version 3.4.3 20050227 (Red Hat 3.4.3-22.1).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
as -a64 -mppc64 -many -V -Qy -o allok.o /tmp/ccIKMQIP.s
GNU assembler version 2.15.92.0.2 (ppc-redhat-linux) using BFD version
2.15.92.0.2 20040927
/tmp/ccIKMQIP.s: Assembler messages:
/tmp/ccIKMQIP.s:285: Error: can't resolve `main' {.opd section} -
`.L.main' {.text section}
/tmp/ccIKMQIP.s:285: Error: expression too complex
Julian Seward wrote:
>>and I get the following errors building the test programs in
>>helgrind/tests. Should these tests compile cleanly?
>>
>>make allok deadlock inherit race race2 readshared
>>make[1]: Entering directory `/home/dcn/svn/1-18/helgrind/tests'
>>if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -Winline -Wall -Wshadow
>>-gstabs -m64 -Wno-long-long -Wdeclaration-after-statement -MT allok.o
>>-MD -MP -MF ".deps/allok.Tpo" -c -o allok.o allok.c; \
>>then mv -f ".deps/allok.Tpo" ".deps/allok.Po"; else rm -f
>>".deps/allok.Tpo"; exit 1; fi
>>/tmp/ccYznKU9.s: Assembler messages:
>>/tmp/ccYznKU9.s:285: Error: can't resolve `main' {.opd section} -
>>`.L.main' {.text section}
>
>
> They should compile cleanly and indeed they have on our 970.
>
> helgrind/allok.c is a completely vanilla small pthreads program.
> Are you able to compile it by hand (gcc -m64 -o allok allok.c -lpthread) ?
>
> J
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
|