Would it be possible to turn libgcc_s.so into a linker script that links
against libgcc.a and libgcc_s.so.1, and teach g++ not to link against
libgcc.a explicitly anymore?
I'm suggesting this because libtool uses -nostdlib when linking shared
objects in C++ mode, and does not link against -lgcc, o
On 13/03/2019 03:25, Vincent Lefevre wrote:
> On 2019-03-12 21:56:59 +0100, David Brown wrote:
>> I disagree. To generate an unconditional error (rejecting the program), the
>> compiler would need such proof - such as by tracing execution from main().
>> But to generate a warning activated specifi
On Tue, 2019-03-12 at 16:08 +0100, Martin Liška wrote:
> Hi.
>
> I've thinking about the file split about quite some time, mainly
> in context of PR84402. I would like to discuss if it's fine for
> maintainers of the target to make such split and into which logical
> components can the file be spl
On Tue, Mar 12, 2019 at 9:54 PM Jeff Law wrote:
>
> On 3/12/19 2:50 PM, Eric Gallager wrote:
> > On 3/12/19, Martin Liška wrote:
> >> Hi.
> >>
> >> I've thinking about the file split about quite some time, mainly
> >> in context of PR84402. I would like to discuss if it's fine for
> >> maintainer
On 3/12/19 3:28 PM, Ian Lance Taylor wrote:
On Tue, Mar 12, 2019 at 11:20 AM Aldy Hernandez wrote:
I have some libgo failures which I'm pretty sure I caused (see below for
details), but I can't seem to figure out how to reproduce. Before I go
down the rabbit hole, is there an easy way of r
On Wed, 13 Mar 2019, Florian Weimer wrote:
> Would it be possible to turn libgcc_s.so into a linker script that links
> against libgcc.a and libgcc_s.so.1, and teach g++ not to link against
> libgcc.a explicitly anymore?
It is already a linker script on platforms using t-slibgcc-libgcc in
libgcc
gcc@gcc.gnu.org：
sSQxub电、微 1 3 7 =2 4 3 2= 0 0 7 7 刘NcO
jfiC
06时52分49秒
