This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-4.8.0 lto plugin depends from old libgcc
- From: Ian Lance Taylor <iant at google dot com>
- To: ÐÐÐÐÑÐÐ ÐÐÐÐÐÐ <alexpux at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Fri, 29 Mar 2013 06:16:25 -0700
- Subject: Re: GCC-4.8.0 lto plugin depends from old libgcc
- References: <CABEPuQLC052HnzOcHsW6soMKHcQn4qiOEgqJtBNDzENTYhmHDQ at mail dot gmail dot com>
On Fri, Mar 29, 2013 at 2:14 AM, ÐÐÐÐÑÐÐ ÐÐÐÐÐÐ <alexpux@gmail.com> wrote:
>
> When building MinGW-w64 toolchains with GCC-4.8.0 toolchain under
> windows I have liblto_plugin-0.dll depended on old libgcc_s*.dll.
>
> For example:
> 1. I have GCC-4.8.0 SJLJ multilib toolchain.
> 2. I need build GCC-4.8.0 DWARF toolchain.
> 3. After building DWARF toolchain has liblto_plugin-0.dll depended
> fron libgcc_s_sjlj-1.dll. DependsWalker show that liblto_plugin-0.dll
> need __udivdi3 and __umoddi3 functions from libgcc*.dll
>
> If I build new toolchain with earlier GCC (<=4.7.2)
> liblto_plugin-0.dll doesn't depends from any libgcc*.dll.
> Is it bug in new gcc-4.8.0?
Maybe it is a bug but it doesn't sound like one. It's normal for code
compiled by GCC to depend on libgcc. Why is it a problem in this
case?
Ian