When Valgrind 3.0.0 is used to check an application compiled with the Intel(R) C++ Compiler for Linux 8.0 or 9.0 targeting Intel® Extended Memory 64 Technology (Intel® EM64T) platforms, and the -xP or -fast switch is used, and the application is run on an Intel(R) EM64T platform, the message "Fatal Error : This program was not built to run on the processsor in your system." appears, and the Valgrind session ends. Valgrind should continue to run and the error message should not appear. Red Hat Enterprise Linux AS release 3 (Taroon Update 3) Linux 2.4.21-20.EL #1 SMP Wed Aug 18 20:34:58 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux This problem also occurs when running Valgrind 3.0.0 on Fortran applications compiled with the Intel(R)Fortran Compiler for Linux 9.0 targeting Intel® Extended Memory 64 Technology (Intel® EM64T) platforms, and the -fast switch is used.
> Valgrind should continue to run and the error message should not appear. icc links in a run-time library which does CPUID at startup. On all 64-bit x86 platforms, Valgrind simulates CPUID as if it was running on an Athlon64. I guess this causes icc's runtime library to barf.
I'm quite tempted to mark this as a bug in icc rather than Valgrind.
The problem is that -xP tells the compiler it can use SSE3 instructions which valgrind doesn't currently support. Most compilers just generate the instructions and then let the program fall over at run time if such an instruction is encountered on a processor that doesn't support them but the Intel compiler tries to be clever and links in some run time start up code that checks the processor capability and startup and refuses to run if you asked for SSE3 at compiler time even if it never actually emitted an SSE3 instruction.
> I'm quite tempted to mark this as a bug in icc rather than Valgrind. -xP is a request for SSE3 code, which Athlon64 won't do -- it can only do SSE2 (at least older models). That's fair enough. So the acid test is, what happens if you rebuild the app -xW (SSE2 only) ?
I'm closing crashing and similar bugs that are more than two years old. If you still see this problem with Valgrind 3.4.1 please reopen the bug report. Thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!