Perform the clustering of instructions in the scheduler by using information from the machine model.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
llvm/lib/CodeGen/ScheduleDAGInstrs.cpp | ||
---|---|---|
242 | May be I am bit confused here, but should it not be SDep(Def, SDep::Artificial) ? |
llvm/lib/CodeGen/ScheduleDAGInstrs.cpp | ||
---|---|---|
242 | For each instruction, go over its predecessors looking for any instruction that's clustered to it. Then, go over the successors of the clustered instruction and bind them to the original instruction. |
llvm/lib/CodeGen/ScheduleDAGInstrs.cpp | ||
---|---|---|
242 | Thanks, much clearer. May this reply could be added as comment. |
Comment Actions
I'm not sure I like this:
- It introduces a new word "cluster", so we end up having the words "MacroFusion" and "Cluster" around which appear to mean the same thing?
- Using computeOperandLatency() to compute something called cluster feels out of place, similar with getReadAdvanceCycles
May be I am bit confused here, but should it not be SDep(Def, SDep::Artificial) ?
Please consider rewording the comment to make the intention clearer, if possible.