-
Notifications
You must be signed in to change notification settings - Fork 839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
20220911-fixes-re-multi-test #5579
20220911-fixes-re-multi-test #5579
Conversation
@SparkiDev note all tests have passed on this. The "pending" on Options-A and FIPSv2 Regression are Jenkins->github integration glitches. |
Tried gcc-13 with -Werror=array-bounds with --enable-all and it didn't fail. (Not FIPS or kernel.) |
So far I've only gotten it to trigger in the linuxkm build. That's what the copy-paste is from. My guess is it's something to do with the options that Kbuild is passing to gcc. Anyway the new |
What are the KBUILD_EXTRA_FLAGS? |
…int_minimal, with same structure as struct sp_int but only one digit, to allow error-free access to sp_ints allocated with ALLOC_SP_INT() with fewer than SP_INT_DIGITS digits, and use the new type in _sp_zero() and sp_init_size() to eliminate -Werror=array-bounds on _sp_zero() under gcc-13.
…t(), and sp_init_size(), re sp_int_minimal.
That's the recipe in
The only difference between the long-existing |
c070deb
to
d18a654
Compare
wolfssl/wolfcrypt/sp_int.h and wolfcrypt/src/sp_int.c:
add
struct sp_int_minimal
, with same structure asstruct sp_int
but only one digit, to allow error-free access tosp_int
s allocated withALLOC_SP_INT()
with fewer thanSP_INT_DIGITS
digits, and use the new type in_sp_zero()
andsp_init_size()
to eliminate-Werror=array-bounds
on_sp_zero()
under gcc-13.tested with
wolfssl-mult-test.sh ... super-quick-check fips-140-3-dev-optest-acvp-sp-asm-gcc-latest linuxkm-mainline-pie-gcc-latest
at testing commit 7ccf1f2c3b9 (PR#346).also adds support for
$KBUILD_EXTRA_FLAGS
to linuxkm/Makefile, needed to activatelinuxkm-mainline-pie-gcc-latest
.