lcvon007 wrote: In TargetSchedModel::computeOperandLatency will use the WriteResourceID in LatencyTable, and it doesn't affect the logic when calling STI->getReadAdvanceCycles(UseDesc, UseIdx, WriteID) after change. https://github.com/llvm/llvm-project/pull/86654