This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: regrename creates invalid insn

From: Ian Lance Taylor <iant at google dot com>
To: Andreas Schwab <schwab at linux-m68k dot org>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 12 Mar 2012 14:57:11 -0700
Subject: Re: regrename creates invalid insn
References: <m2d38hvigj.fsf@igel.home> <mcrlin5bkyx.fsf@dhcp-172-18-216-180.mtv.corp.google.com> <m24nttv7ja.fsf@igel.home>

Andreas Schwab <schwab@linux-m68k.org> writes:

> Ian Lance Taylor <iant@google.com> writes:
>
>> But it also looks like the pattern should use a match_scratch.
>
> It is also used as input in operand 2.

Sorry, I missed that.

This still seems like a bug in regrename to me, but it also seems like
an unusual case, so it is less surprising that it hasn't been seen
before.

Ian

Follow-Ups:
- Re: regrename creates invalid insn
  - From: Andreas Schwab

References:
- regrename creates invalid insn
  - From: Andreas Schwab
- Re: regrename creates invalid insn
  - From: Ian Lance Taylor
- Re: regrename creates invalid insn
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]