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 ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
