"Ling-hua Tseng" <[EMAIL PROTECTED]> writes:

> The algorithm is highly dependent on the information of LOG_LINKS(insn).
> But I found that there are not any dependecy info for `reload instructions'
> because the register allocation pass and reloading pass are peformed after
> the first insn scheduling pass.

Right.  The LOG_LINKS field is not reliable after reload.

> Should I write a violent algorithm to scan these data dependencies?

Yes.

> Are there any better solutions for this problem?

At present, there is not.

mips_avoid_hazard in config/mips/mips.c is an example of how the MIPS
backend addresses a similar issue.  Note the use of DELAYED_REG.

Ian

Reply via email to