[llvm] MachineTraceMetrics: always include instr latency in depth (PR #73550)

[David Green via llvm-commits]

davemgreen wrote:

I'm not saying I'm against this patch exactly, I'm not sure MachineRraceMetrics ever works super well. But it looks like the `Cycle` here is the first point the instruction can be issued - i.e. when all it's operands become available. Not when it finishes executing, and the _result_ becomes available.

Can you explain more about the issue you are trying to solve?

https://github.com/llvm/llvm-project/pull/73550