> at runtime if AES is supported or not (e.g. if this is checked at
> installation time and different executable is installed depending on
> this install check, then no luck (until Valgrind supports the AES
> instructions).
Yeah, I agree with that analysis. The failing instruction is in a
system library
==71202== valgrind: Unrecognised instruction at address 0x3945c0b.
==71202== at 0x3945C0B: aes_encrypt_key_hw (in
/usr/lib/system/libcommonCrypto.dylib)
so it seems reasonably that the library was customised at install
time, and can simply assume it won't get run on any other CPU.
So we can't avoid solving this problem merely by adjusting the
simulated CPUID output bits.
J
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
