Test results for amd64, cezanne, crypto_kem/mceliece8192128f

[Page version: 20250925 09:42:54]

Compiler output

bm.c: bm.c:82: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:84: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:85: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:86: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:87: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:88: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:89: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:90: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:91:15: warning: AVX vector return of type 'vec256' (aka '__m256i') without 'avx' enabled changes the ABI [-Wpsabi]
bm.c: ...

Compiler output

decrypt.c: In file included from decrypt.c:9:
decrypt.c: In file included from ./vec128_gf.h:11:
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 0x597c5528 curr 0x59c36768 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1845447184 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 2508870)
   at 0x...: crypto_kem_mceliece8192128f_sse_constbranchindex_decrypt (decrypt.c:0)
   by 0x...: crypto_kem_mceliece8192128f_sse_constbranchindex_operation_dec (kem_dec.c:38)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:345)
client stack range: [0x1FFEEFE000 0x1FFF000FFF] client SP: 0x1FFEFF1E50
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 0x59c36768 end 0x59c8a067 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 1899396616 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 2507818)
   at 0x...: crypto_kem_mceliece8192128f_sse_constbranchindex_decrypt (decrypt.c:0)
   by 0x...: crypto_kem_mceliece8192128f_sse_constbranchindex_operation_dec (kem_dec.c:38)
   by 0x...: test (try.c:160)
   by 0x...: main (try-anything.c:345)
client stack range: [0x1FFEEFE000 0x1FFF000FFF] client SP: 0x1FFEFF1E50
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.

Passed TIMECOP

TIMECOP iterations: 1