https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882
--- Comment #7 from emilie.feral at numworks dot com ---
Hello,
Any news on the subject?
Would you advise in the meantime to discard the LTO (with the -fno-lto option)
on the compilation unit containing the failing code?
The bug occurred for us
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882
--- Comment #5 from emilie.feral at numworks dot com ---
When compiling without the lto using the command:
arm-none-eabi-gcc main.c -Os -mfloat-abi=hard -mthumb -mcpu=cortex-m4
-ffreestanding -nostdlib -lgcc -save-temps -o a.elf
I get the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882
--- Comment #2 from emilie.feral at numworks dot com ---
Here they are:
arm-none-eabi-gcc -v
•[master]
Using built-in specs.
COLLECT_GCC=/Applications/ARM/bin/arm-none-eabi-gcc
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: emilie.feral at numworks dot com
Target Milestone: ---
Created attachment 49163
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49163&action=edit
preprocess
