David Garske
David Garske
> The define probably isn't reaching the assembly code! Good point. Trying again with ASFLAGS
Still not working for me. Any suggestions? ``` ./configure -host=armv7a --enable-armasm --enable-debug --disable-shared AM_CFLAGS="-fomit-frame-pointer -DWOLFSSL_ARM_ARCH_NEON_64BIT" AM_CCASFLAGS="-fomit-frame-pointer -DWOLFSSL_ARM_ARCH_NEON_64BIT" && make ... wolfcrypt/src/port/arm/armv8-chacha.c: In function 'wc_Chacha_encrypt_256': wolfcrypt/src/port/arm/armv8-chacha.c:1383:1: error: fp cannot be used...
> Try without debug for now. I did. It was in the log. Still his fault
@SparkiDev I pulled latest. Still see the same bus error without debug. With debug same "fp cannot be used" error. Tested using: `./configure -host=armv7a --enable-armasm AM_CFLAGS="-DWOLFSSL_ARM_ARCH_NEON_64BIT" AM_CCASFLAGS="-DWOLFSSL_ARM_ARCH_NEON_64BIT" && make`. AND...
> @dgarske > Can you tell be which file the compiler is complaining about with the use of fp? > I've eliminated the error with the my QEMU build when...
retest this please
Jenkins retest this please
Hi @MalikAlmazrua , Thank you for the report. This is a very minor issue and I will push a fix. Related to ZD 13147 and PR https://github.com/wolfSSL/wolfssl/pull/4523 Thanks, David Garske,...
Hi @Ziemien , The reason for the crash is the stack defined for Hmac structure does not match the size that wolfSSL expects. It sounds like your application is not...
Hi @Ziemien , The SHA256 is on by default unless --disable-sha256 or `NO_SHA256` is used. The issue you are seeing is a data type mismatch trying to call from C++...