Date: Tue, 26 Jun 2012 03:58:19 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: precompiled sse-intrinsics vs. -march=native On 2012-06-26 03:41, Solar Designer wrote: > It appears that we shouldn't use the precompiled sse-intrinsics > files (icc's *.S) in -march=native builds. Specifically, when I > tried linux-x86-64-gpu on bull where -march=native implies XOP, I > got reporting that XOP intrinsics were being used, whereas in reality > the build used icc-precompiled SSE2 code. My bad, I though I removed -DUSING_ICC_S_FILE from them. Good thing you caught it. > What's worse, I got segfault for --format=md5 (read beyond end of > heap after MD5_Update() was called with a huge size from the > precompiled intrinsics code, I don't know why), and failed self-test > for raw-md5 and raw-md4 (but working for raw-sha1). > > The misreporting issue has an obvious cause. The segfault and > failed self-tests are a mystery to me: I don't see why the > precompiled code would be incompatible with -march=native on this > machine. The ABI should stay the same. Maybe there's a bug lurking > around that will also bite us in other cases. Odd. Only recent change to these formats was reduced binary size. That was straight-forward and has been well tested since. magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.