https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #10 from Sam James ---
Please see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032#c5.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #9 from Thomas Petazzoni ---
FYI, this is still happening at least with GCC 13.3.0. We got again the build
issue in our autobuilder today:
https://autobuild.buildroot.org/results/f37b03dc47da8f54c583b33cac960daeed72c29f/build-end.lo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #8 from Richard Earnshaw ---
Perhaps something is changing the decision on the use of the frame pointer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #7 from Christophe Lyon ---
Indeed, but I am surprised it seems to compile for cortex-m4?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
Richard Earnshaw changed:
What|Removed |Added
Last reconfirmed||2022-09-27
Status|UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #5 from Christophe Lyon ---
Could you share the preprocessed source file in the M3 and M4 cases along with
the full command line used to compile it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #4 from Thomas Petazzoni ---
Yes, same triplet. We do not (yet) have FDPIC support for ARM in Buildroot (we
have a patch series pending for that).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #3 from Christophe Lyon ---
Interesting
Did you use the same target triplet?
arm*-*-uclinuxfdpiceabi is handled differently from
arm-buildroot-uclinux-uclibcgnueabi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
--- Comment #2 from Thomas Petazzoni ---
Thanks for the feedback. There must be something special in those
configurations, because I did build a Cortex-M4 configuration with gcc 11.3.0
just a few days ago, and it built fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107032
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
10 matches
Mail list logo
