artifact_id;status_id;status_name;priority;submitter_id;submitter_name;assigned_to_id;assigned_to_name;open_date;close_date;last_modified_date;summary;details;"Resolution";"Version";"Component"
1646;1;"Open";3;145;"Jérémie Dimino";100;"Nobody";"2016-07-20 16:12";"";"2016-07-20 16:12";"Fix build on 32 bit architectures";"Building cryptokit 1.11 on 32 bits fails with the following error:
src/aesni.c: In function ‘aesni_check_available’:
src/aesni.c:27: error: can't find a register in class ‘BREG’ while reloading ‘asm’
src/aesni.c:27: error: ‘asm’ operand has impossible constraints
The attached patch fix the build by using __get_cpuid from . Tested on Linux and OSX, for both 32 and 64 bit builds.";"None";"None";"None"
1708;1;"Open";3;23228;"Etienne Millon";100;"Nobody";"2016-11-22 12:38";"";"2016-11-22 12:38";"Fallback to Z.powm if Z.powm_sec is not available";"`Z.powm_sec` implements constant-time modular exponentiation, but it
fails at runtime if zarith has been built against a version of GMP that
does not support it.
Until version 1.10, cryptokit would use its own non-constant-time
modular exponentation implementation, so it makes it possible to use
cryptokit 1.11 without the new constant-time implementation when only
old versions of GMP are available.
Thanks!";"None";"None";"None"
1709;1;"Open";3;23228;"Etienne Millon";100;"Nobody";"2016-11-22 12:39";"";"2016-11-22 12:39";"Align key_schedule on a 16 byte boundary";"Memory access to/from XMM registers require the memory operand to be
aligned in order to have good performance (using the `MOVDQA`
operation). To ensure that, the compiler is supposed to align stack
variables, but it can not always do that. In particular, old GCC
versions (4.4.7, present in Centos 6) fail to do that. It is thus
necessary to align it manually using extra space.";"None";"None";"None"