On 29/09/11 11:09, Gaetano Mendola wrote: > I'm getting the following error running my application with valgrind: > > vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0x5A 0x7 0x48 0xF 0x5A > 0x4F > ==31136== valgrind: Unrecognised instruction at address 0x1f2a2c20. > ==31136== at 0x1F2A2C20: ??? (in > /opt/intel/composerxe-2011.1.107/ipp/lib/intel64/libippsy8.so.7.0) > ==31136== by 0x1F2A1FAE: y8_ownippsSum_32f (in > /opt/intel/composerxe-2011.1.107/ipp/lib/intel64/libippsy8.so.7.0) > ==31136== by 0x1F2FDE5C: y8_ownippsMean_32f (in > /opt/intel/composerxe-2011.1.107/ipp/lib/intel64/libippsy8.so.7.0) > ==31136== by 0x1F1A2D31: y8_ippsMean_32f (in > /opt/intel/composerxe-2011.1.107/ipp/lib/intel64/libippsy8.so.7.0)
That's CVTPS2PD which looks like it has been supported for ages. What version of valgrind are you using? Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
