******************
Falcon-Padded-512:
******************

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $ valgrind --tool=massif --stacks=yes ./test_sig_mem Falcon-padded-512 2
==314215== Massif, a heap profiler
==314215== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==314215== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==314215== Command: ./test_sig_mem Falcon-padded-512 2
==314215==
Configuration info
==================
Target platform:  aarch64-Linux-6.6.20+rpt-rpi-2712 - ARM PMU options enabled
Compiler:         gcc (12.2.0)
Compile options:  [-march=armv8-a+crypto;-Wa,--noexecstack;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.10.1-dev
Git commit:       6b4e692b8083f391d181087f500b3389ffb007d8 (+ local modifications)
OpenSSL enabled:  Yes (OpenSSL 3.0.11 19 Sep 2023)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
OQS build flags:  OQS_SPEED_USE_ARM_PMU OQS_DIST_BUILD OQS_OPT_TARGET=generic CMAKE_BUILD_TYPE=Release
CPU exts active:  AES SHA2 NEON

vex: priv/host_arm64_defs.c:2829 (genSpill_ARM64): Assertion `offsetB < 4096' failed.
vex storage: T total 140238368 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==314215==    at 0x58009114: show_sched_status_wrk (m_libcassert.c:406)
==314215==    by 0x58009263: report_and_quit (m_libcassert.c:477)
==314215==    by 0x5800949B: panic (m_libcassert.c:553)
==314215==    by 0x5800949B: vgPlain_core_panic_at (m_libcassert.c:558)
==314215==    by 0x580094BF: vgPlain_core_panic (m_libcassert.c:563)
==314215==    by 0x5808277B: failure_exit (m_translate.c:761)
==314215==    by 0x580EDD27: vex_assert_fail (main_util.c:245)
==314215==    by 0x5814C973: genSpill_ARM64 (host_arm64_defs.c:2829)
==314215==    by 0x581435DB: spill_vreg (host_generic_reg_alloc3.c:338)
==314215==    by 0x58144B3F: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:1280)
==314215==    by 0x580EC843: libvex_BackEnd (main_main.c:1133)
==314215==    by 0x580EC843: LibVEX_Translate (main_main.c:1236)
==314215==    by 0x58084F6F: vgPlain_translate (m_translate.c:1831)
==314215==    by 0x5805664B: handle_chain_me (scheduler.c:1169)
==314215==    by 0x58059227: vgPlain_scheduler (scheduler.c:1514)
==314215==    by 0x580A861F: thread_wrapper (syswrap-linux.c:101)
==314215==    by 0x580A861F: run_a_thread_NORETURN (syswrap-linux.c:154)
==314215==    by 0xFFFFFFFFFFFFFFFF: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 314215)
==314215==    at 0x1CCA38: PQCLEAN_FALCONPADDED512_AARCH64_is_short (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314215==    by 0x14712F: do_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314215==    by 0x1241D7: OQS_SIG_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314215==    by 0x12316B: main (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
client stack range: [0x1FFF000000 0x1FFF003FFF] client SP: 0x1FFF002020
valgrind stack range: [0x1002C18000 0x1002D17FFF] top usage: 19776 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.

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $

******************
Falcon-1024:
******************

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $ valgrind --tool=massif --stacks=yes ./test_sig_mem Falcon-1024 2
==314265== Massif, a heap profiler
==314265== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==314265== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==314265== Command: ./test_sig_mem Falcon-1024 2
==314265==
Configuration info
==================
Target platform:  aarch64-Linux-6.6.20+rpt-rpi-2712 - ARM PMU options enabled
Compiler:         gcc (12.2.0)
Compile options:  [-march=armv8-a+crypto;-Wa,--noexecstack;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.10.1-dev
Git commit:       6b4e692b8083f391d181087f500b3389ffb007d8 (+ local modifications)
OpenSSL enabled:  Yes (OpenSSL 3.0.11 19 Sep 2023)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
OQS build flags:  OQS_SPEED_USE_ARM_PMU OQS_DIST_BUILD OQS_OPT_TARGET=generic CMAKE_BUILD_TYPE=Release
CPU exts active:  AES SHA2 NEON

vex: priv/host_arm64_defs.c:2829 (genSpill_ARM64): Assertion `offsetB < 4096' failed.
vex storage: T total 139388352 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==314265==    at 0x58009114: show_sched_status_wrk (m_libcassert.c:406)
==314265==    by 0x58009263: report_and_quit (m_libcassert.c:477)
==314265==    by 0x5800949B: panic (m_libcassert.c:553)
==314265==    by 0x5800949B: vgPlain_core_panic_at (m_libcassert.c:558)
==314265==    by 0x580094BF: vgPlain_core_panic (m_libcassert.c:563)
==314265==    by 0x5808277B: failure_exit (m_translate.c:761)
==314265==    by 0x580EDD27: vex_assert_fail (main_util.c:245)
==314265==    by 0x5814C973: genSpill_ARM64 (host_arm64_defs.c:2829)
==314265==    by 0x581435DB: spill_vreg (host_generic_reg_alloc3.c:338)
==314265==    by 0x58144B3F: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:1280)
==314265==    by 0x580EC843: libvex_BackEnd (main_main.c:1133)
==314265==    by 0x580EC843: LibVEX_Translate (main_main.c:1236)
==314265==    by 0x58084F6F: vgPlain_translate (m_translate.c:1831)
==314265==    by 0x5805928F: handle_tt_miss (scheduler.c:1141)
==314265==    by 0x5805928F: vgPlain_scheduler (scheduler.c:1503)
==314265==    by 0x580A861F: thread_wrapper (syswrap-linux.c:101)
==314265==    by 0x580A861F: run_a_thread_NORETURN (syswrap-linux.c:154)
==314265==    by 0xFFFFFFFFFFFFFFFF: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 314265)
==314265==    at 0x13F748: PQCLEAN_FALCON1024_AARCH64_verify_raw (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314265==    by 0x13C947: do_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314265==    by 0x1241D7: OQS_SIG_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314265==    by 0x12316B: main (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
client stack range: [0x1FFF000000 0x1FFF003FFF] client SP: 0x1FFF001050
valgrind stack range: [0x1002C18000 0x1002D17FFF] top usage: 19776 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.

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $


******************
Falcon-padded-1024:
******************

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $ valgrind --tool=massif --stacks=yes ./test_sig_mem Falcon-padded-1024 2
==314268== Massif, a heap profiler
==314268== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==314268== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==314268== Command: ./test_sig_mem Falcon-padded-1024 2
==314268==
Configuration info
==================
Target platform:  aarch64-Linux-6.6.20+rpt-rpi-2712 - ARM PMU options enabled
Compiler:         gcc (12.2.0)
Compile options:  [-march=armv8-a+crypto;-Wa,--noexecstack;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.10.1-dev
Git commit:       6b4e692b8083f391d181087f500b3389ffb007d8 (+ local modifications)
OpenSSL enabled:  Yes (OpenSSL 3.0.11 19 Sep 2023)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
OQS build flags:  OQS_SPEED_USE_ARM_PMU OQS_DIST_BUILD OQS_OPT_TARGET=generic CMAKE_BUILD_TYPE=Release
CPU exts active:  AES SHA2 NEON

vex: priv/host_arm64_defs.c:2829 (genSpill_ARM64): Assertion `offsetB < 4096' failed.
vex storage: T total 139286056 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==314268==    at 0x58009114: show_sched_status_wrk (m_libcassert.c:406)
==314268==    by 0x58009263: report_and_quit (m_libcassert.c:477)
==314268==    by 0x5800949B: panic (m_libcassert.c:553)
==314268==    by 0x5800949B: vgPlain_core_panic_at (m_libcassert.c:558)
==314268==    by 0x580094BF: vgPlain_core_panic (m_libcassert.c:563)
==314268==    by 0x5808277B: failure_exit (m_translate.c:761)
==314268==    by 0x580EDD27: vex_assert_fail (main_util.c:245)
==314268==    by 0x5814C973: genSpill_ARM64 (host_arm64_defs.c:2829)
==314268==    by 0x581435DB: spill_vreg (host_generic_reg_alloc3.c:338)
==314268==    by 0x58144B3F: doRegisterAllocation_v3 (host_generic_reg_alloc3.c:1280)
==314268==    by 0x580EC843: libvex_BackEnd (main_main.c:1133)
==314268==    by 0x580EC843: LibVEX_Translate (main_main.c:1236)
==314268==    by 0x58084F6F: vgPlain_translate (m_translate.c:1831)
==314268==    by 0x5805928F: handle_tt_miss (scheduler.c:1141)
==314268==    by 0x5805928F: vgPlain_scheduler (scheduler.c:1503)
==314268==    by 0x580A861F: thread_wrapper (syswrap-linux.c:101)
==314268==    by 0x580A861F: run_a_thread_NORETURN (syswrap-linux.c:154)
==314268==    by 0xFFFFFFFFFFFFFFFF: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 314268)
==314268==    at 0x154AB8: PQCLEAN_FALCONPADDED1024_AARCH64_verify_raw (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314268==    by 0x151AE7: do_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314268==    by 0x1241D7: OQS_SIG_verify (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
==314268==    by 0x12316B: main (in /home/cuserp3/work/pqc-evaluation-tools/lib/liboqs/build/tests/test_sig_mem)
client stack range: [0x1FFF000000 0x1FFF003FFF] client SP: 0x1FFF001040
valgrind stack range: [0x1002C18000 0x1002D17FFF] top usage: 19776 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.

cuserp3@pi-3:~/work/pqc-evaluation-tools/lib/liboqs/build/tests $