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: Problem with peephole to peephole2 conversion


> You'll have something like this in your test
> 
> operands[0] == operands[1] || peep2_regno_dead_p (2, operands[0])
> 
> i.e. you only need to test for op0's death if it is different from op1.
> 
> Paolo
> 

Exactly.. this is the same thing as calling dead_or_set_p(insn,
operands[0]).  If it can be done by dead_or_set_p, why use
peep2_dead_reg_p? Other ports also support the use of peep2_dead_reg_p
instead of dead_or_set_p. What is the basic difference between the
two? I mean, there must be something the former can do which the
latter can't.

Please correct me if i am wrong.

Thanks in advance,
Ashwin.


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