Closed erwango closed 2 years ago
@microbuilder Any idea what could have changed in TFM compilation recently that can change the fact that warnings are now generating build error (not complaining, but I'd like to understand ;-) ) ?
@microbuilder Any idea what could have changed in TFM compilation recently that can change the fact that warnings are now generating build error (not complaining, but I'd like to understand ;-) ) ?
I'm not sure off the top of my head, but I'll reproduce and see if I spot a reason.
Seeing this is CI failure on PR https://github.com/zephyrproject-rtos/zephyr/pull/47369 (unrelated, as the issues exists in mainline)
Caused by https://github.com/zephyrproject-rtos/zephyr/pull/45906 ... reverting this to disable FP hard ABI resolves this.
Caused by #45906 ... reverting this to disable FP hard ABI resolves this.
Thank Kevin, so it explains why we get this issue now. Handing over to @jamike
The problem here appears to be the FPU support being enabled without the dependent PR to not build the NS application merged first. Merging https://github.com/zephyrproject-rtos/zephyr/pull/43599 and reverting #47423 again this builds without issues.
The bug description here is inaccurate, the issue is this: error: tf-m-tests/app/CMakeFiles/tfm_ns.dir/main_ns.o uses VFP register arguments, bin/tfm_ns.axf does not
.
Maybe a different issues should be opened (or this one reopened) to track the ST-M missing prototype warning?
Describe the bug A clear and concise description of what the bug is.
Note that exact same warnings were present on release v3.1.0, but the build was successful.
To Reproduce
Expected behavior Should build
Impact Block CI
Environment (please complete the following information):