Ling-hua Tseng wrote:
> Should I write a violent algorithm to scan these data dependencies?
> Are there any better solutions for this problem?
Another example to look at might be the ia64 port. It reruns flow and
sched during the machine dependent reorg pass, so we can get the
dependencies right.
"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 schedu
I'm porting GCC 4.1.1 to a VLIW architecture.
I have to insert NOP instructions when data dependencies occurred.
So I wrote an algorithm as the following:
foreach(insn in all real insns) {
foreach(dep_insn in LOG_LINKS(insn)) {
if(INSN_DELETED_P(dep_insn)) continue;
stalls = insn_latency(dep
