On Thu, Jun 23, 2016 at 7:10 AM, Andy Polyakov via RT <r...@openssl.org> wrote: >>>> A quick question about this configuration... Should Linux-x32 enable >>>> ec_nistp_64_gcc_128 by default? Does anything prohibit >>>> ec_nistp_64_gcc_128 in this configuration? >>>> >>>> # ./Configure linux-x32 >>>> Configuring OpenSSL version 1.1.0-pre6-dev (0x0x10100006L) >>>> no-asan [default] OPENSSL_NO_ASAN (skip dir) >>>> ... >>>> no-ec_nistp_64_gcc_128 [default] OPENSSL_NO_EC_NISTP_64_GCC_128 (skip >>>> dir) >>>> ... >>>> >>>> I believe it meets the three criteria for ec_nistp_64_gcc_128. >>> >>> What are "the three criteria"? I mean I'm not really sure. Nor am I sure >>> that they are perfect. I mean maybe they need some adjustment in x32 >>> context. To either allow or prevent erroneous compilation. Bottom line >>> is that I don't actually know at this point... >> >> My bad... According to my notes, one can use ec_nistp_64_gcc_128 when >> these three conditions are met: >> >> * Little endian CPU >> * CPU allows unaligned data access >> * Compiler supports __uint128_t > > Correct. But there still might be nuances. For example first two > criteria were not actually formulated originally....
Gotcha, thanks. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4583 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
