This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: constraint reshuffle for SH gcc target port
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Joern Rennecke <joern dot rennecke at superh dot com>
- Cc: gcc at gcc dot gnu dot org, Kaz Kojima <kkojima at gcc dot gnu dot org>, Alexandre Oliva <aoliva at redhat dot com>, Toshiyasu Morita <toshiyasu dot morita at hsa dot hitachi dot com>, stephen clarke <stephen dot clarke at st dot com>, Ralf Corsepius <corsepiu at faw dot uni-ulm dot de>, Joel Sherrill <joel dot sherrill at OARcorp dot com>, linuxsh-shmedia-dev at lists dot sourceforge dot net, linux-sh at m17n dot org, Richard dot Earnshaw at arm dot com
- Date: Sat, 14 Jun 2003 14:11:55 +0100
- Subject: Re: RFC: constraint reshuffle for SH gcc target port
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> The gcc.dg/compat/scalar-return-4 c_compat_x_tst.o compile failure
> is yet another of these little bugs that can be easily solved with
> another constraint - but there are more problems like this, the SH
> port is already very low on free constraint letters, and the existing
> constraint letters are also somewhat haphazard. For instance, the
> 'Z' constraint really belongs into the CONST_OK_FOR_CONSTRAINT space,
> but it didn't fit there because all the letters had been used up.
> Thus, I think it is time to reshuffle some constraints to get some
> more order in the existing constraints and make room for new ones.
> This will affect assembler templates that use any of the renamed
> constraints. I have attached an outline of the existing usage of
> uppercase constraint letters (lowercase letters that are not defined
> in a machine-independent way are used for register classes on the SH),
> what constraints I want to change, and list of the uppercase constraints
> after the reshuffle.
>
Doesn't this break any constraints in asm statements that use the
constraint letters you are changing?
R.