Re: [RFA 2/2]: --enable-explicit-exception-frame-registration compatibility option

2014-09-21 Thread Hans-Peter Nilsson
> From: Jeff Law > Date: Fri, 19 Sep 2014 08:29:16 +0200 > On 09/12/14 11:51, Hans-Peter Nilsson wrote: > > Ping! > >> libgcc: > >>* crtstuff.c [EH_FRAME_SECTION_NAME && !USE_PT_GNU_EH_FRAME]: > >>Sanity-check USE_EH_FRAME_REGISTR

Re: [RFA 2/2]: --enable-explicit-exception-frame-registration compatibility option

2014-09-18 Thread Jeff Law
On 09/12/14 11:51, Hans-Peter Nilsson wrote: Ping! From: Hans-Peter Nilsson Date: Thu, 4 Sep 2014 23:42:28 +0200 This adds an option to allow programs and libraries built *without* inhibit_libc to stay compatible with system librarie

Re: [RFA 2/2]: --enable-explicit-exception-frame-registration compatibility option

2014-09-12 Thread Hans-Peter Nilsson
Ping! > From: Hans-Peter Nilsson > Date: Thu, 4 Sep 2014 23:42:28 +0200 > This adds an option to allow programs and libraries built > *without* inhibit_libc to stay compatible with system libraries > (really: libgcc_s.so.1) built *with* i

[RFA 2/2]: --enable-explicit-exception-frame-registration compatibility option

2014-09-04 Thread Hans-Peter Nilsson
This adds an option to allow programs and libraries built *without* inhibit_libc to stay compatible with system libraries (really: libgcc_s.so.1) built *with* inhibit_libc, at the cost of the registration. As mentioned, that's a one-way compatibility barrier. While it's nice to avoid the overhead