This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?

From: Eric Botcazou <ebotcazou at adacore dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Ollie Wild <aaw at google dot com>, gcc at gcc dot gnu dot org
Date: Thu, 8 Mar 2012 08:22:40 +0100
Subject: Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
References: <CAFOgFcQwBnZR6SQ_kODmBQpY1x4FTrqyUGoZ1oDqSUVAj+_vvw@mail.gmail.com> <201203080741.32099.ebotcazou@adacore.com> <mcrwr6vpoby.fsf@dhcp-172-18-216-180.mtv.corp.google.com>

> True, but not, as far as I can see, an explanation for why the symbols
> are hidden.  Hiding the symbols doesn't fix the problem of having
> multiple libgcc_eh on those platforms.

Yes, it does, as it prevents libgcc_eh from being linked in shared libraries, 
thus forcing you to use libgcc_s.so, at least on those platforms.

-- 
Eric Botcazou

Follow-Ups:
- Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Ian Lance Taylor

References:
- Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Ollie Wild
- Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Eric Botcazou
- Re: Why are libgcc.a and libgcc_eh.a compiled with -fvisibility=hidden?
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]