e047d3529b
This fixes PR37293. We can have scheduling classes with no write latency entries, that still consume processor resources. We don't want to treat those instructions as zero-latency instructions; they still have to be issued to the underlying pipelines, so they still consume resource cycles. This is likely to be a regression which I have accidentally introduced at revision 330807. Now, if an instruction has a non-empty set of write processor resources, we conservatively treat it as a normal (i.e. non zero-latency) instruction. llvm-svn: 331193 |
||
|---|---|---|
| .. | ||
| AArch64 | ||
| ARM | ||
| X86 | ||
| invalid_input_file_name.test | ||
| lit.local.cfg | ||