This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] compileflags for libgcc
- From: Richard Zidlicky <rz at linux-m68k dot org>
- To: Jim Wilson <wilson at specifixinc dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 10 Jan 2004 14:20:10 +0100
- Subject: Re: [patch] compileflags for libgcc
- References: <20031228175430.GA3893@linux-m68k.org> <3FFF6CD5.7090101@specifixinc.com>
On Fri, Jan 09, 2004 at 07:09:09PM -0800, Jim Wilson wrote:
> Richard Zidlicky wrote:
> >+TARGET_LIBGCC2_CFLAGS = -Dmc68060 -D__mc68060__
>
> This just looks weird. I don't follow the logic that it only effects
> 68060 libraries. It will effect all libraries because it is an
> unconditional change to TARGET_LIBGCC2_CFLAGS.
it affects soubroutines that are only ever called from code
compiled with -m68060 or -m68020-60 flag.
> The usual solution to this problem for an embedded target is to
> multilib, but that is probably inconvenient for a linux target.
multilib would be better, but even with this setting we get optimal
behaviour for nearly all targets/flag combinations. Normal 68020 code
will do the longlong arithmetic inline and code compiled with -m68060
will link to this library routines.
Code compiled with -m68020-60 will run slower than now on 68020-40
but this combination doesnt appear to be widely used.
> If you just want one multilib, then probably you should be using the
> -m68020-60 option, which should emit code suitable for all targets from
> the 020 to the 060.
do you mean
TARGET_LIBGCC2_CFLAGS = -m68020-60
..that would work quite well for everyone I think.
Richard