summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
diff options
context:
space:
mode:
authorAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-11-27 15:56:00 +0000
committerAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-11-27 15:56:00 +0000
commit7a7588990b278a30145ab20f487779b3413fe2cc (patch)
tree87872c29dc7be77fcefd498d1b7dfeeabb6c1e97 /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
parent3827aabe75e2cde07cbdf8017e5acdee4ca3fec3 (diff)
downloadbcm5719-llvm-7a7588990b278a30145ab20f487779b3413fe2cc.tar.gz
bcm5719-llvm-7a7588990b278a30145ab20f487779b3413fe2cc.zip
[llvm-mca] pass -dispatch-stats flag to a couple of tests. NFC
This change is in preparation for a patch that fixes PR36666. llvm-mca currently doesn't know if a buffered processor resource describes a load or store queue. So, any dynamic dispatch stall caused by the lack of load/store queue entries is normally reported as a generic SCHEDULER stall. See for example the -dispatch-stats output from the two tests modified by this patch. In future, processor models will be able to tag processor resources that are used to describe load/store queues. That information would then be used by llvm-mca to correctly classify dynamic dispatch stalls caused by the lack of tokens in the LS. llvm-svn: 347662
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud