|
From: David S. <ds...@um...> - 2008-03-27 04:54:41
|
Response from intel! "David, Compile the main (the module with PROGRAM) as not requiring SSE3, compile everything else with requires SSE3. The processor test is only performed on startup of the main based on main's options. If your main does some productive work, then rename it into a subroutine and make a seperate file as a main stub and call the former main then compile the stub without requirees SSE3. Jim XXXXX" I tested this - it works! It seems like it is probably an issue with the particular mechanism which the intel compiler uses the check the instruction set and the processor at run time. Something to be investigated for the next release? David |
|
From: Julian S. <js...@ac...> - 2008-03-27 11:48:34
|
This is a known bug in Valgrind -- see http://bugs.kde.org/show_bug.cgi?id=155528 and has been fixed in the trunk. Fix will be in 3.3.1. For the meantime use the trunk. You can checkout and build it as detailed at http://www.valgrind.org/downloads/repository.html Let me know if this does/does not fix the problem. J On Thursday 27 March 2008 05:54, David Stuebe wrote: > Response from intel! > > "David, > > Compile the main (the module with PROGRAM) as not requiring SSE3, compile > everything else with requires SSE3. The processor test is only performed on > startup of the main based on main's options. If your main does some > productive work, then rename it into a subroutine and make a seperate file > as a main stub and call the former main then compile the stub without > requirees SSE3. > > Jim XXXXX" > > I tested this - it works! It seems like it is probably an issue with the > particular mechanism which the intel compiler uses the check the > instruction set and the processor at run time. > > Something to be investigated for the next release? > > David |