https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118221
--- Comment #6 from Trampas Stern <trampas at gmail dot com> --- I have requested access to bugzilla for the binutils and can create a bug report there. Thanks Trampas On Fri, Dec 27, 2024 at 3:55 PM pinskia at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118221 > > --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > GCC does not include objdump/assembler/linker, that is a seperate project > called binutils (https://sourceware.org/binutils/) which has its own > versioning > and release scheme. > > GCC also does not include the libc. Since you are using the bare metal > built > toolchains from arm, I am assume you are using newlib. > > Note GDB is also its own project too with its own release and versioning > scheme. You didn't mention which version of binutils nor gdb you are using. > Only what version of GCC you are using. > > Also since you are using a prebuilt toolchain with all of the versions > from a > specific vendor, you should be reporting the issue to them first with full > directions on how to reproduce the issue. > > Right now you have only given a small main source file without the full > command > lines on how you generated the elf files. This is required. See > https://gcc.gnu.org/bugs/ also. > > > Then I set up the build environment and set through the start up code, > aka > reset vector and configuring clocks. > > This is not provided for an example. So there is no way to reproduce the > exact > binaries you have provided to debug what is going wrong. > > Also you might want to look into the linker map (`-Map file` option passed > to > the linker, if you are using the GCC driver to invoke the linker, then > `-Wl,-Map,linkermapfile` is what you want to use) to understand what the > linker > is doing. > > -- > You are receiving this mail because: > You reported the bug.
