Re: [Valgrind-users] Unhandled instruction in libm

[Julian S. <js...@ac...>]

On 08/06/2013 10:07 PM, Florian Krohm wrote:
> No work-around really, other than recompiling libm with a suitable set
> of compiler flags (I would not know what those are).

I'm pretty sure this is caused by an AMD-specific insn set extension,
but I don't know which one.  If you constrain the compiler to avoid
AMD-specifics you might be better off.

Also, try using the valgrind svn trunk as the insn set support has
been updated since 3.8.1.  I'd say it's less likely to help, but is
worth a try.

svn co svn://svn.valgrind.org/valgrind/trunk
cd trunk
./autogen.sh
Then configure and build as with the tarball.

J