search for: q67lwmnf6c5v

Displaying 2 results from an estimated 2 matches for "q67lwmnf6c5v".

2015 Nov 27
1
Test failed!!
...t; -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWV6K3AAoJEJ6/8sItn9q9bikIALCjl3JoSE6WzQBeocHhHA5s hMni6ehX0e5rmDly+jtFSABB4AEkKophiHHYAblVWV+VMuexY6URGiADS1XtfMk8 KujHncHp/KpOsRhBhr07qgUzsTzCmBStVrkgEb8gIhy4aYWgaS1ZrRC/CHwyAMlJ Iz1NEDEVvWVQYy6nb9R/B699j39YF0+n7n1rQTJDR5OgabD4bZ//Q67lWmNf6C5v fSwUmydfOzcAy1EJzf8Bsx8lmNDsC/LWRKsTpDXzVnIoyx0N4C5S1Ab8GFiQcafR OxRFELfOI/jPiisc4JlpDHw+TYOskY6D8rEuGbDvswHvw/I4gQSMS4tpQPwVnV0= =6cGh -----END PGP SIGNATURE-----
2015 Nov 26
2
Test failed!!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Jesus, Thanks for the report. As far as I can tell, what's happening is that when intrinsics are enabled, we compile all tests with -msse4.1, even when it's only run-time detected. In most cases, that doesn't cause any issue, but sometimes the compiler will take the C code and generate an SSEx instruction on its own. I think this is