> Thanks for the response. > > It is a huge application, 1.5M lines not including big external dependencies > like ACE/TAO. Porting over to 64bit mode would probably take months. Any > other suggestion? Perhaps disabling the generation of the offending AVX > instructions with some compiler flag? >
You can install a SIGILL handler to continue execution. I'm guessing it will probably foul some Valgrind analysis. I don't know if it will ruin all analysis. You might also retard your optimization level a bit so vectorizing instructions are used less frequently. Valgrind recommends -O1 or -O0 (http://valgrind.org/docs/manual/QuickStart.html), but I've noticed GCC will utilize some vectorization even at -O1 level, like wide memcpy's. Maybe a selection of -fno-XXX compiler options will ferret the unwanted instructions. You can also use Clang or GCC's sanitizers. I try to test will all the analysis tools I can get my hands on. In cases where Valgrind does not run, I depend on other tools, like Coverity and Sanitizers. Jeff ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
