[PATCH] Option to build bare-metal ARM cross-compiler for arm-none-eabi target without libunwind

[Sebastian Huber]

On 06/12/2012 04:37 PM, Joseph S. Myers wrote:
> You need to provide a self-contained explanation of what the problem is
> that your patch is fixing and why you chose that approach to fixing it -
> with reference to the ARM EABI documentes (RTABI etc.) for why your
> approach is valid according to the ARM EABI.
>
> libunwind is a library separate from libgcc that is used by libgcc for
> unwinding on ia64-linux-gnu only (whether built by GCC or separately
> installed).  There is also a separate libunwind project that may be used
> on GNU/Linux platforms but I am not aware of being used for bare-metal at
> all.  Certainly it would be unusual to use it for ARM EABI and the ARM
> EABI libgcc works fine without it.  So referring to libunwind in the ARM
> EABI context seems rather confusing; if you don't want it, just do the
> same as almost all other ARM EABI users and don't use it; it's *using*
> libunwind that requires special action, not avoiding it.

I think the main problem is the usage of -fexceptions for some libgcc files.  I 
would not disable the libunwind build and simply avoid the -fexceptions.  See also

http://gcc.gnu.org/ml/gcc-help/2011-03/msg00149.html

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.