summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/interpreter
diff options
context:
space:
mode:
authorAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-11-09 19:30:20 +0000
committerAndrea Di Biagio <Andrea_DiBiagio@sn.scee.net>2018-11-09 19:30:20 +0000
commit91bdf24cfdcba93fda1872c8c68186cf4118a442 (patch)
treea2b9a8741145d5560b78abfd43bbf9ee780544c8 /lldb/packages/Python/lldbsuite/test/python_api/interpreter
parentdfc08baceb5af96bf931c1471d5234da846dc7ab (diff)
downloadbcm5719-llvm-91bdf24cfdcba93fda1872c8c68186cf4118a442.tar.gz
bcm5719-llvm-91bdf24cfdcba93fda1872c8c68186cf4118a442.zip
[llvm-mca] Account for buffered resources when analyzing "Super" resources.
This was noticed when working on PR3946. By construction, a group cannot be used as a "Super" resource. That constraint is enforced by method `SubtargetEmitter::ExpandProcResource()`. A Super resource S can be part of a group G. However, method `SubtargetEmitter::ExpandProcResource()` would not update the number of consumed resource cycles in G based on S. In practice, this is perfectly fine because the resource usage is correctly computed for processor resource units. However, llvm-mca should still check if G is a buffered resource. Before this patch, llvm-mca didn't correctly check if S was part of a group that defines a buffer. So, the instruction descriptor was not correctly set. For now, the semantic change introduced by this patch doesn't affect any of the upstream scheduling models. However, it will allow to make some progress on PR3946. llvm-svn: 346545
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud