This is the mail archive of the
mailing list for the GCC project.
Re: SH Linux: remove big endian multilib
- To: "M. R. Brown" <mrbrown at 0xd6 dot org>
- Subject: Re: SH Linux: remove big endian multilib
- From: NIIBE Yutaka <gniibe at m17n dot org>
- Date: Sun, 5 Aug 2001 10:29:21 +0900 (JST)
- Cc: Michael Eager <eager at mvista dot com>, Andrew Haley <aph at cambridge dot redhat dot com>, amylaar at redhat dot com, gcc at gcc dot gnu dot org
- References: <firstname.lastname@example.org><200107270834.f6R8Y5u21170@mule.m17n.org><3B6B6CE4.2A076E08@mvista.com><200108040435.f744ZAo18841@mule.m17n.org><20010804113600.A11515@0xd6.org>
The ABI of four targets are differents. Hence, we need four libgcc-s.
Please understand this point. We need four libgcc-s for sh-unknown-linux-gnu.
If we omit multilib support in sh-unknown-linux-gnu, say, we won't
have libgcc for -m4. It still compiles program, yes, but doesn't link
(sometime it does with libgcc for -m3, but not always).
> I've used that patch for a while now, but I'm in agreement with the others
> that multilibs for Linux doesn't make much sense, when glibc doesn't
> support it.
I agree with this more or less. Using specified one is better and
simple. But the definition of sh-unknown-linux-gnu is supporting four