This is the mail archive of the
mailing list for the GCC project.
Re: Patches for coldfire v4e
- From: Daniel Jacobowitz <drow at false dot org>
- To: Bernardo Innocenti <bernie at develer dot com>
- Cc: arcjai at yahoo dot com, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org,peter at the-baradas dot com, Jaiprakash C <cjaiprakash at noida dot hcltech dot com>
- Date: Wed, 13 Apr 2005 12:06:58 -0400
- Subject: Re: Patches for coldfire v4e
- References: <firstname.lastname@example.org> <425CD3FF.email@example.com>
On Wed, Apr 13, 2005 at 10:10:39AM +0200, Bernardo Innocenti wrote:
> >>What are the changes you need to apply?
> >>Would plain 68020 code run on v4e processor? As far
> >>as I can see, m68k-linux isn't a multilib target.
> > Problem occurs mainly due to restricted addressing
> > modes in v4e. For ex v4e supports only 16-bit
> > displacements. So all crt* files needs to be build for
> > v4e. Also v4e does not have extended floating point
> > instructions (XF mode) so we may have to modify t-*
> > for fpgnulib.c.
> So it seems adding coldfire-linux is the only way
> to address this...
Why? Adding support (if it isn't already there) for something like
--with-arch=coldfire should work just as well.