This is the mail archive of the
mailing list for the GCC project.
Re: [patch] MIPS: Two classes associated with the "e" constraint
- From: Richard Sandiford <rsandifo at redhat dot com>
- To: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 28 Feb 2004 08:59:05 +0000
- Subject: Re: [patch] MIPS: Two classes associated with the "e" constraint
- References: <Pine.LNX.firstname.lastname@example.org>
"Maciej W. Rozycki" <email@example.com> writes:
> I've noticed the "e" constraint is bound to two register classes,
> M16_NA_REGS and LEA_REGS, with obviously only one being active. Here's an
> obvious fix, allocating a new constraint for LEA_REGS, the newer of the
> two classes. But AFAICT "e" isn't used to refer to M16_NA_REGS anymore,
> so perhaps this meaning can simply be removed.
mips_char_to_class['e'] = M16_NA_REGS;
should just be removed. Like you say, it's not used by any of the
.md patterns. Nor is it documented as a MIPS-specific constraint,
so I don't see any need to keep it for inline asm.
I remember checking that "e" wasn't needed before remapping it to
LEA_REGS. ("e" for effective address, of course.) I was supposed
to get rid of the line above at the same time. but obviously I forgot.