This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what does the calling for min_insn_conflict_delay mean
- From: Ian Lance Taylor <iant at google dot com>
- To: "Amker.Cheng" <amker dot cheng at gmail dot com>
- Cc: gcc at gcc dot gnu dot org, vmakarov at google dot com
- Date: Mon, 21 Sep 2009 15:15:09 -0700
- Subject: Re: what does the calling for min_insn_conflict_delay mean
- References: <e8b251c80909200652y1e2e8808m2020f51438c54be@mail.gmail.com>
"Amker.Cheng" <amker.cheng@gmail.com> writes:
> In function new_ready, it calls to min_insn_conflict_delay with
> "min_insn_conflict_delay (curr_state, next, next)".
> But the function's comments say that it returns minimal delay of issue of
> the 2nd insn after issuing the 1st in given state.
> Why the last two parameter for the call are both "next"?
> seems conflict with the comments.
This change dates back to the first DFA scheduler patch. It does seem a
little odd, particularly as the call in new_ready is the only use of
min_insn_conflict_delay. CC'ing vmakarov in case he remembers anything
about this old code.
Ian