summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
diff options
context:
space:
mode:
authorStanislav Mekhanoshin <Stanislav.Mekhanoshin@amd.com>2017-02-28 17:22:39 +0000
committerStanislav Mekhanoshin <Stanislav.Mekhanoshin@amd.com>2017-02-28 17:22:39 +0000
commit282e8e4a726599257ae88a1a03b6444db8067dbb (patch)
treecb754006608ffb257563f4bbd20e0534d57730ec /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
parentfb834a8278e628a04a84daa9f4ceb61c2dd84248 (diff)
downloadbcm5719-llvm-282e8e4a726599257ae88a1a03b6444db8067dbb.tar.gz
bcm5719-llvm-282e8e4a726599257ae88a1a03b6444db8067dbb.zip
[AMDGPU] New method to estimate register pressure
This change introduces new method to estimate register pressure in GCNScheduler. Standard RPTracker gives huge error due to the following reasons: 1. It does not account for live-ins or live-outs if value is not used in the region itself. That creates a huge error in a very common case if there are a lot of live-thu registers. 2. It does not properly count subregs. 3. It assumes a register used as an input operand can be reused as an output. This is not always possible by itself, this is not what RA will finally do in many cases for various reasons not limited to RA's inability to do so, and this is not so if the value is actually a live-thu. In addition we can now see clear separation between live-in pressure which we cannot change with the scheduling and tentative pressure which we can change. Differential Revision: https://reviews.llvm.org/D30439 llvm-svn: 296491
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud