Regarding bare-metal ARM cross-compiler toolchain without libunwind. Patch now proposed to gcc-patches: http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00720.html Thanks & Best Regards Fredrik -----Ian Lance Taylor <iant@xxxxxxxxxx> wrote: ----- To: Fredrik Hederstierna <fredrik.hederstierna@xxxxxxxxxxxxxxxxxxxx> From: Ian Lance Taylor <iant@xxxxxxxxxx> Date: 03/27/2012 03:30PM Cc: gcc-help@xxxxxxxxxxx Subject: Re: Bare metal ARM Cross compiler for arm-none-eabi target without libunwind? Fredrik Hederstierna <fredrik.hederstierna@xxxxxxxxxxxxxxxxxxxx> writes: > /usr/local/gcc/arm-elf-tools-4.7.0/lib/gcc/arm-none-eabi/4.7.0/thumb//libgcc.a(unwind-arm.o): In function `get_eit_entry': You need to find out why unwind-arm.o is being included in your link. You could easily remove it from libgcc.a, but that would just leave you with some other undefined symbol. unwind-arm.o is only being pulled in because it defines some symbol that your program refers to. What symbol? If you are using the GNU linker you can find out easily enough by adding -Wl,-M to your link command. That will produce a map file. The first part of the file will be a list starting with "Archive member included because of file (symbol)". Look for the symbol that causes unwind-arm.o to be included. Ian
