This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa
- From: Baruch Siach <baruch at tkos dot co dot il>
- To: Sterling Augustine <augustine dot sterling at gmail dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Chris Zankel <chris at zankel dot net>, Marc Gauthier <marc at cadence dot com>
- Date: Tue, 21 Jan 2014 07:46:54 +0200
- Subject: Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa
- Authentication-results: sourceware.org; auth=none
- References: <9378e9d8b82241f494b682ad796dcd41acfe6b6b dot 1390123290 dot git dot baruch at tkos dot co dot il> <CAGSvup9F6nW2-txuHxnF-KRaB8TPZuN+CkTLecSevib18eSfhQ at mail dot gmail dot com>
Hi Sterling,
On Mon, Jan 20, 2014 at 12:06:59PM -0800, Sterling Augustine wrote:
> On Sun, Jan 19, 2014 at 1:21 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > The xtensa port uses __xtensa_libgcc_window_spill in libgcc to implement
> > __builtin_frame_address. This symbol is local/hidden in libgcc. This is not a
> > problem when linking against static libgcc. But g++ defaults to
> > -shared-libgcc, thus breaking link against C++ shared libraries that are using
> > __builtin_frame_address as follows:
>
> This is OK for mainline.
Thanks. This is needed for the 4.7 and 4.8 branches as well.
> I assume your copyright assignment is on file?
According to
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html, only
"legally significant" contributions of more than 15 lines of code "or so"
require copyright assignment.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -