Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-21 Thread Sterling Augustine
On Mon, Jan 20, 2014 at 9:46 PM, Baruch Siach wrote: > 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 wrote: >> > The xtensa port uses __xtensa_libgcc_window_spill in libgcc to implement >> > __builtin_frame_ad

Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-20 Thread Baruch Siach
Hi Sterling, On Mon, Jan 20, 2014 at 09:53:36PM -0800, Sterling Augustine wrote: > On Mon, Jan 20, 2014 at 9:46 PM, Baruch Siach wrote: > > According to > > https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html, only > > "legally significant" contributions of more than 15 lines of

Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-20 Thread Sterling Augustine
On Mon, Jan 20, 2014 at 9:46 PM, Baruch Siach wrote: > Hi Sterling, >> 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.ht

Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-20 Thread Baruch Siach
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 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 > >

Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-20 Thread Chris Zankel
Hi Sterling, Given that you are the maintainer on file and I think you have signed the copyright assignment, you should be able to just take it. AFAIK a copyright assignment is only required for large(r) patches. Thanks, -Chris On 1/20/14, 12:06 PM, Sterling Augustine wrote: On Sun, Jan 19,

Re: [PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-20 Thread Sterling Augustine
On Sun, Jan 19, 2014 at 1:21 AM, Baruch Siach 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 b

[PATCH] libgcc: use linker script for libgcc_s.so on xtensa

2014-01-19 Thread Baruch Siach
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 __bui