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: How can I write an empty conversion instruction

From: Richard Earnshaw <rearnsha at gcc dot gnu dot org>
To: Richard Henderson <rth at redhat dot com>
Cc: Steve Ellcey <sje at cup dot hp dot com>, gcc at gcc dot gnu dot org
Date: Mon, 09 May 2005 17:26:10 +0100
Subject: Re: How can I write an empty conversion instruction
References: <200505062059.NAA19579@hpsje.cup.hp.com> <20050507031445.GB23300@redhat.com> <1115638848.25452.10.camel@pc960.cambridge.arm.com> <20050509161159.GA17982@redhat.com>

On Mon, 2005-05-09 at 17:11, Richard Henderson wrote:
> On Mon, May 09, 2005 at 12:40:48PM +0100, Richard Earnshaw wrote:
> > > The best way is to have a post-reload splitter that splits the insn
> > > into nothing at all.
> > 
> > Is that really valid?  I would have thought it would break the data flow.
> 
> Obviously you only split to nothing when the registers match.
> But we don't have mode correspondence between successive register
> apperances after reload.
> 
> 
> r~

So do we fully recreate *all* the flow information before a scheduling
pass?

Follow-Ups:
- Re: How can I write an empty conversion instruction
  - From: Richard Henderson

References:
- How can I write an empty conversion instruction
  - From: Steve Ellcey
- Re: How can I write an empty conversion instruction
  - From: Richard Henderson
- Re: How can I write an empty conversion instruction
  - From: Richard Earnshaw
- Re: How can I write an empty conversion instruction
  - From: Richard Henderson

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