Hi,
>> For reference. Why does it show up with no-asm? bn_nist.c is
>> collection of functions for specific moduli, but it's perfectly
>> possible to calculate the result using general-purpose subroutines.
>> It was found that general-purpose *assembly* code paths deliver
>> better performance and it was arranged so that bn_nist is not
>> invoked in asm builds (look for #if defined(OPENSSL_BN_ASM_MONT) in
>> crypto/ec/ec_cvt.c).
>
> If "Configure" invoke without "no-asm" flag, then bn_nist.c compiled,
> but function BN_nist_mod_{192,224,256,384} don't called. If
> "Configure" invoke with "no-asm", OpenSSL use
> BN_nist_mod_{192,224,256,384} functions. Right?
Yes.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
