This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Option to build bare-metal ARM cross-compiler for arm-none-eabi target without libunwind
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Larry Doolittle <ldoolitt at recycle dot lbl dot gov>
- Cc: gcc-patches at gcc dot gnu dot org, Fredrik Hederstierna <fredrik dot hederstierna at securitas-direct dot com>
- Date: Tue, 12 Jun 2012 14:37:03 +0000 (UTC)
- Subject: Re: [PATCH] Option to build bare-metal ARM cross-compiler for arm-none-eabi target without libunwind
- References: <20120603163535.GA15766@recycle.lbl.gov>
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.
--
Joseph S. Myers
joseph@codesourcery.com