Implementation notes: amd64, kizomba, crypto_kem/mceliece8192128pc

Compiler output

bm.c: bm.c:80:37: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         for (i = 13; i < 16; i++) buf[i] = vec256_setzero();
bm.c:                                            ^
bm.c: bm.c:82:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[0][0] = vec256_set1_16b(0x5555);
bm.c:                      ^
bm.c: bm.c:83:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[0][1] = vec256_set1_16b(0xAAAA);
bm.c:                      ^
bm.c: bm.c:84:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[1][0] = vec256_set1_16b(0x3333);
bm.c:                      ^
bm.c: bm.c:85:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[1][1] = vec256_set1_16b(0xCCCC);
bm.c:                      ^
bm.c: bm.c:86:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[2][0] = vec256_set1_16b(0x0F0F);
bm.c:                      ^
bm.c: bm.c:87:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[2][1] = vec256_set1_16b(0xF0F0);
bm.c:                      ^
bm.c: bm.c:88:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c:         mask[3][0] = vec256_set1_16b(0x00FF);
bm.c:                      ^
bm.c: bm.c:89:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c: ...

Compiler output

pk_gen.c: pk_gen.c:211:12: warning: variable length array folded to constant array as an extension [-Wgnu-folding-constant]
pk_gen.c:                 uint64_t w[ PK_NROWS ][ nBlocks_I*2 ];
pk_gen.c:                          ^
pk_gen.c: pk_gen.c:212:10: warning: variable length array folded to constant array as an extension [-Wgnu-folding-constant]
pk_gen.c:                 vec128 v[ PK_NROWS ][ nBlocks_I ];
pk_gen.c:                        ^
pk_gen.c: 2 warnings generated.

Compiler output

decrypt.c: In file included from decrypt.c:9:
decrypt.c: In file included from ./vec128_gf.h:10:
decrypt.c: ./vec128.h:38:9: error: always_inline function '_mm_testz_si128' requires target feature 'sse4.1', but would be inlined into function 'vec128_testz' that is compiled without support for 'sse4.1'
decrypt.c:         return _mm_testz_si128(a, a);
decrypt.c:                ^
decrypt.c: 1 error generated.

TIMECOP error (can be valgrind bug)

error 1
VEX temporary storage exhausted.
Pool = TEMP,  start 0x597c14a8 curr 0x59c6eb80 end 0x59c85fe7 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 313843832 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 3928890)
   at 0x...: extract_gf (sk_gen.c:43)
   by 0x...: crypto_kem_mceliece8192128pc_avx_constbranchindex_genpoly_gen (sk_gen.c:153)
   by 0x...: crypto_kem_mceliece8192128pc_avx_constbranchindex_operation_keypair (kem_keypair.c:57)
   by 0x...: crypto_kem_mceliece8192128pc_avx_constbranchindex_keypair (wrap_keypair.c:10)
   by 0x...: test (try.c:126)
   by 0x...: main (try-anything.c:345)
client stack range: [0x1FFEFDD000 0x1FFF000FFF] client SP: 0x1FFEFDE500
valgrind stack range: [0x1008CAE000 0x1008DADFFF] top usage: 18744 of 1048576
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

TIMECOP error (can be valgrind bug)

error 1
VEX temporary storage exhausted.
Pool = TEMP,  start 0x597c14a8 curr 0x59c6eb80 end 0x59c85fe7 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 316696896 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
   by 0x...: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 3939406)
   at 0x...: extract_gf (sk_gen.c:43)
   by 0x...: crypto_kem_mceliece8192128pc_sse_constbranchindex_genpoly_gen (sk_gen.c:153)
   by 0x...: crypto_kem_mceliece8192128pc_sse_constbranchindex_operation_keypair (kem_keypair.c:57)
   by 0x...: crypto_kem_mceliece8192128pc_sse_constbranchindex_keypair (wrap_keypair.c:10)
   by 0x...: test (try.c:126)
   by 0x...: main (try-anything.c:345)
client stack range: [0x1FFEFDD000 0x1FFF000FFF] client SP: 0x1FFEFDE500
valgrind stack range: [0x1008CAE000 0x1008DADFFF] top usage: 18744 of 1048576
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

Passed TIMECOP

TIMECOP iterations: 1