On 28/11/2016, at 8:07 PM, Alex Bligh wrote: > >> On 27 Nov 2016, at 16:09, Danny Wilson <da...@torquevideo.tv> wrote: >> >> The target machines uses an i5 CPU but the build machine is a core2 duo >> which is why I chose 'native'. Not sure that was the right choice but it >> works (without Valgrind). >> >> I've just tried -march as 'native', 'core2', and 'pentiumpro'. All have the >> same result. > > Tried building the application, or tried building the standard library? I > think you said it was the latter where the illegal instructions were. > > Your distribution might (or might not) have a pentium-pro compatible version > for install. That should not have AVX instructions in (I would have thought) > -- > Alex Bligh
Hi Alex, rebuilding the standard libraries is a little beyond our scope (and I'd figure it unlikely that such a basic function of the c++ library had a memory leak. Something like that would be well published). As Tom pointed out, it could also be from a std template compiled in from my program. Good question now is how to disable generation of the unsupported instructions... ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
