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: Lousy scheduling decisions owing to bad interaction betweensched and greg :(


On Fri, 2004-09-03 at 14:29, Joern Rennecke wrote:
> > ===================================================================
> >  4) Does an expander sound like the right solution to the problem? 
> > ===================================================================
> 
> Yes.  You'll also have to have an insn predicate for movsi that rejects
> memory-memory moves to prevent the rtl optimizers from generating them.

It can't really be a predicate (in the strict sense) because they can
only validate one operand.  Instead you need a final condition on the
insn that rejects it in the case where both operands turn out to be
memory operands.  The ARM does this for its mov<mm> patterns as, I
suspect, do several ports.

R.


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