This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, AArch64 07/11] Link static libgcc after shared libgcc for -shared-libgcc
- From: Joseph Myers <joseph at codesourcery dot com>
- To: <rth7680 at gmail dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>, <ramana dot radhakrishnan at arm dot com>, <agraf at suse dot de>, <matz at suse dot de>, Richard Henderson <richard dot henderson at linaro dot org>
- Date: Wed, 26 Sep 2018 16:49:49 +0000
- Subject: Re: [PATCH, AArch64 07/11] Link static libgcc after shared libgcc for -shared-libgcc
- References: <20180926050355.32746-1-richard.henderson@linaro.org> <20180926050355.32746-8-richard.henderson@linaro.org>
On Tue, 25 Sep 2018, rth7680@gmail.com wrote:
> From: Richard Henderson <richard.henderson@linaro.org>
>
> We are about to introduce symbols to libgcc.a that will
> not be present in libgcc_s.so. Most symbols will be
> resolved from the shared library first, and only the new
> symbols will be pulled from the static library.
Configurations with this property should be using libgcc's
config/t-slibgcc-libgcc to make libgcc_s.so into a linker script. Unless
you have a configuration needing this but not supporting linker scripts, I
wouldn't expect driver changes to be needed.
The linker script looks like:
/* GNU ld script
Use the shared library, but some functions are only in
the static library. */
GROUP ( libgcc_s.so.1 -lgcc )
--
Joseph S. Myers
joseph@codesourcery.com