On Sun, Sep 26, 2010 at 7:22 PM, John Reiser <[email protected]> wrote:
>> I get the following error trying to compile valgrind 3.5.0 with icc
>> version 11.1:
>
>> icc: command line warning #10006: ignoring unknown option '-Wno-long-long'
>> icc: command line warning #10006: ignoring unknown option '-Wno-pointer-sign'
>> icc: command line warning #10006: ignoring unknown option
>> '-Wdeclaration-after-statement'
>
> Those three lines above are warnings, not errors, and are not fatal.
> icc and gcc differ in diagnosing extensions and legal-but-iffy code.
>
>> ld:../valt_load_address_amd64_linux.lds:219: syntax error
>> make[4]: *** [memcheck-amd64-linux] Error 1
>
> What is line 219 of valt_load_address_amd64_linux.lds ?
> The source has:
> -----
> .debug_line 0 : { *(.debug_line) }
> .debug_frame 0 : { *(.debug_frame) } ### line 219
> .debug_str 0 : { *(.debug_str) }
> -----
> which is OK. Is yours OK?
line 219 of my valt_load_address_amd64_linux.lds has
------
.debug_pubtypes 0 : { *(.debug_pubtypes) }
.debug_ranges ld: warning: cannot find entry symbol _start; not
setting start address ### line 219
0 : { *(.debug_ranges) }
------
> Is your /bin/ld OK? Does running
> memcheck on the 'make' itself and all children:
> valgrind --trace-children=yes make
> detect any problems?
The call to
Command: /opt/intel/Compiler/11.1/069/bin/intel64/icc -Wno-long-long
-Wno-pointer-sign -Wdeclaration-after-statement -fno-stack-protector
-o memcheck-amd64-linux -static
-Wl,-defsym,valt_load_address=0x38000000 -nodefaultlibs -
nostartfiles -u _start -m64
-Wl,-T,../valt_load_address_amd64_linux.lds
memcheck_amd64_linux-mc_leakcheck.o
memcheck_amd64_linux-mc_malloc_wrappers.o
memcheck_amd64_linux-mc_main.o memcheck_amd64_linux-mc_translate.o
memcheck_amd64_linux
-mc_machine.o memcheck_amd64_linux-mc_errors.o
../coregrind/libcoregrind-amd64-linux.a ../VEX/libvex-amd64-linux.a
-lgcc
yields a long alternating list of
Conditional jump or move depends on uninitialised value(s)
and
Invalid read of size 8
So I guess this is an icc problem? The call to ld, however, shows no errors.
I use icc because I would like to compile valgrind to be used with
code compiled with the intel MPI compiler, so I suppose switching to
gcc is not an option?
Thank you for your help!
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
