Test results for amd64, cezanne, crypto_kem/mceliece348864pc

[Page version: 20260902 16:19:30]

Compiler output

decrypt.c: decrypt.c:218:11: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
decrypt.c:         allone = vec256_set1_16b(0xFFFF);
decrypt.c:                  ^
decrypt.c: decrypt.c:222:17: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
decrypt.c:                 error256[i] = vec256_or_reduce(eval[i]);
decrypt.c:                               ^
decrypt.c: decrypt.c:223:17: warning: AVX vector argument of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
decrypt.c:                 error256[i] = vec256_xor(error256[i], allone);
decrypt.c:                               ^
decrypt.c: decrypt.c:151:12: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
decrypt.c:                 out[i] = vec256_set4x(v[0], v[1], v[2], v[3]);
decrypt.c:                          ^
decrypt.c: In file included from decrypt.c:16:
decrypt.c: In file included from ./fft_tr.h:11:
decrypt.c: ./vec256.h:35:10: error: always_inline function '_mm256_set_epi64x' requires target feature 'avx', but would be inlined into function 'vec256_set4x' that is compiled without support for 'avx'
decrypt.c:         return  _mm256_set_epi64x(a3, a2, a1, a0);
decrypt.c:                 ^
decrypt.c: ./vec256.h:35:10: error: AVX vector return of type '__m256i' (vector of 4 'long long' values) without 'avx' enabled changes the ABI
decrypt.c: decrypt.c:60:15: warning: AVX vector argument of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
decrypt.c:                 out[i][j] = vec256_and(inv[i][j], recv[i]);
decrypt.c:                             ^
decrypt.c: In file included from decrypt.c:16:
decrypt.c: In file included from ./fft_tr.h:11:
decrypt.c: ./vec256.h:74:9: error: always_inline function '_mm256_and_si256' requires target feature 'avx2', but would be inlined into function 'vec256_and' that is compiled without support for 'avx2'
decrypt.c:         return _mm256_and_si256(a, b);
decrypt.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:12: 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:10:
decrypt.c: In file included from ./vec128_gf.h:11:
decrypt.c: ./vec128.h:33: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 0x597c5528 curr 0x59c2aad8 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1711373272 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: show_sched_status_wrk (m_libcassert.c:406)
   by 0x...: report_and_quit (m_libcassert.c:477)
   by 0x...: panic (m_libcassert.c:553)
   by 0x...: vgPlain_core_panic_at (m_libcassert.c:558)
   by 0x...: vgPlain_core_panic (m_libcassert.c:563)
   by 0x...: failure_exit (m_translate.c:761)
   by 0x...: vpanic (main_util.c:253)
   by 0x...: private_LibVEX_alloc_OOM (main_util.c:181)
   by 0x...: LibVEX_Alloc_inline (main_util.h:176)
   by 0x...: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:493)
   by 0x...: libvex_BackEnd (main_main.c:1133)
   by 0x...: LibVEX_Translate (main_main.c:1236)
   by 0x...: vgPlain_translate (m_translate.c:1831)
   by 0x...: handle_chain_me (scheduler.c:1169)
   by 0x...: vgPlain_scheduler (scheduler.c:1514)
   by 0x...: thread_wrapper (syswrap-linux.c:101)
   by 0x...: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2232318)
   at 0x...: weight_check (decrypt.c:116)
   by 0x...: crypto_kem_mceliece348864pc_avx_constbranchindex_decrypt (decrypt.c:238)
   by 0x...: crypto_kem_mceliece348864pc_avx_constbranchindex_operation_dec (kem_dec.c:41)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:344)
client stack range: [0x1FFEF93000 0x1FFF000FFF] client SP: 0x1FFEFF91E0
valgrind stack range: [0x1008CAE000 0x1008DADFFF] top usage: 18792 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 0x597c5528 curr 0x59c2aad8 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1891476552 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: show_sched_status_wrk (m_libcassert.c:406)
   by 0x...: report_and_quit (m_libcassert.c:477)
   by 0x...: panic (m_libcassert.c:553)
   by 0x...: vgPlain_core_panic_at (m_libcassert.c:558)
   by 0x...: vgPlain_core_panic (m_libcassert.c:563)
   by 0x...: failure_exit (m_translate.c:761)
   by 0x...: vpanic (main_util.c:253)
   by 0x...: private_LibVEX_alloc_OOM (main_util.c:181)
   by 0x...: LibVEX_Alloc_inline (main_util.h:176)
   by 0x...: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:493)
   by 0x...: libvex_BackEnd (main_main.c:1133)
   by 0x...: LibVEX_Translate (main_main.c:1236)
   by 0x...: vgPlain_translate (m_translate.c:1831)
   by 0x...: handle_chain_me (scheduler.c:1169)
   by 0x...: vgPlain_scheduler (scheduler.c:1514)
   by 0x...: thread_wrapper (syswrap-linux.c:101)
   by 0x...: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2231335)
   at 0x...: weight_check (decrypt.c:116)
   by 0x...: crypto_kem_mceliece348864pc_avx_constbranchindex_decrypt (decrypt.c:238)
   by 0x...: crypto_kem_mceliece348864pc_avx_constbranchindex_operation_dec (kem_dec.c:41)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:344)
client stack range: [0x1FFEF93000 0x1FFF000FFF] client SP: 0x1FFEFF91C0
valgrind stack range: [0x1008BB2000 0x1008CB1FFF] top usage: 18792 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 0x597c5528 curr 0x59c2aad8 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1707475912 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: show_sched_status_wrk (m_libcassert.c:406)
   by 0x...: report_and_quit (m_libcassert.c:477)
   by 0x...: panic (m_libcassert.c:553)
   by 0x...: vgPlain_core_panic_at (m_libcassert.c:558)
   by 0x...: vgPlain_core_panic (m_libcassert.c:563)
   by 0x...: failure_exit (m_translate.c:761)
   by 0x...: vpanic (main_util.c:253)
   by 0x...: private_LibVEX_alloc_OOM (main_util.c:181)
   by 0x...: LibVEX_Alloc_inline (main_util.h:176)
   by 0x...: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:493)
   by 0x...: libvex_BackEnd (main_main.c:1133)
   by 0x...: LibVEX_Translate (main_main.c:1236)
   by 0x...: vgPlain_translate (m_translate.c:1831)
   by 0x...: handle_chain_me (scheduler.c:1169)
   by 0x...: vgPlain_scheduler (scheduler.c:1514)
   by 0x...: thread_wrapper (syswrap-linux.c:101)
   by 0x...: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2243763)
   at 0x...: weight_check (decrypt.c:113)
   by 0x...: crypto_kem_mceliece348864pc_sse_constbranchindex_decrypt (decrypt.c:201)
   by 0x...: crypto_kem_mceliece348864pc_sse_constbranchindex_operation_dec (kem_dec.c:41)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:344)
client stack range: [0x1FFEFB1000 0x1FFF000FFF] client SP: 0x1FFEFF9610
valgrind stack range: [0x1008BAE000 0x1008CADFFF] top usage: 18792 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 0x597c5528 curr 0x59c2aad8 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1887029840 bytes allocated
vex storage: P total 512 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
   at 0x...: show_sched_status_wrk (m_libcassert.c:406)
   by 0x...: report_and_quit (m_libcassert.c:477)
   by 0x...: panic (m_libcassert.c:553)
   by 0x...: vgPlain_core_panic_at (m_libcassert.c:558)
   by 0x...: vgPlain_core_panic (m_libcassert.c:563)
   by 0x...: failure_exit (m_translate.c:761)
   by 0x...: vpanic (main_util.c:253)
   by 0x...: private_LibVEX_alloc_OOM (main_util.c:181)
   by 0x...: LibVEX_Alloc_inline (main_util.h:176)
   by 0x...: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:493)
   by 0x...: libvex_BackEnd (main_main.c:1133)
   by 0x...: LibVEX_Translate (main_main.c:1236)
   by 0x...: vgPlain_translate (m_translate.c:1831)
   by 0x...: handle_chain_me (scheduler.c:1169)
   by 0x...: vgPlain_scheduler (scheduler.c:1514)
   by 0x...: thread_wrapper (syswrap-linux.c:101)
   by 0x...: run_a_thread_NORETURN (syswrap-linux.c:154)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2242747)
   at 0x...: weight_check (decrypt.c:113)
   by 0x...: crypto_kem_mceliece348864pc_sse_constbranchindex_decrypt (decrypt.c:201)
   by 0x...: crypto_kem_mceliece348864pc_sse_constbranchindex_operation_dec (kem_dec.c:41)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:344)
client stack range: [0x1FFEFB2000 0x1FFF000FFF] client SP: 0x1FFEFF95F0
valgrind stack range: [0x1008CAE000 0x1008DADFFF] top usage: 18792 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