Hello Richard, > I ask because in the final range: > > start = early_start; > end = MIN (end, early_start + ii); > /* Schedule the node close to it's predecessors. */ > step = 1; > > END is an exclusive bound. It seems like we might be double-counting here, > and effectively limiting the schedule to SCHED_TIME (v_node) + ii - 2.
Yes, I think it indeed should be fixed. Thanks for reporting on this. Revital
