summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/help/TestHelp.py
diff options
context:
space:
mode:
authorAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-04-30 15:55:04 +0000
committerAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-04-30 15:55:04 +0000
commite047d3529baa0920dc55ae278c39e40f03baa2af (patch)
tree810cfa6949204c8677c6d4e971f09791bf60f36a /lldb/packages/Python/lldbsuite/test/help/TestHelp.py
parent79e5cd2fc50f810f9ebfef41422695773caaffa7 (diff)
downloadbcm5719-llvm-e047d3529baa0920dc55ae278c39e40f03baa2af.tar.gz
bcm5719-llvm-e047d3529baa0920dc55ae278c39e40f03baa2af.zip
[llvm-mca] Correctly handle zero-latency stores that consume pipeline resources.
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/help/TestHelp.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud