diff options
author | Lucas Ramirez <11032120+lucas-rami@users.noreply.github.com> | 2025-08-01 13:20:05 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-08-01 13:20:05 +0200 |
commit | 96f3872dc950e01b9b41fa0c214dbcb78c71eaa8 (patch) | |
tree | 6767ca81fd7d272f0348a9b3915bd75db155534b /lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp | |
parent | dfbbb744384167bc874985c340149e39c107e37f (diff) | |
download | llvm-96f3872dc950e01b9b41fa0c214dbcb78c71eaa8.zip llvm-96f3872dc950e01b9b41fa0c214dbcb78c71eaa8.tar.gz llvm-96f3872dc950e01b9b41fa0c214dbcb78c71eaa8.tar.bz2 |
[AMDGPU][Scheduler] Delete RegionsWithMinOcc bitvector from scheduler (NFC) (#142361)
The `GCNScheduleDAGMILive`'s `RegionsWithMinOcc` bitvector is only used
by the `UnclusteredHighRPStage`. Its presence in the scheduler's state
forces us to maintain its value throughout scheduling even though it is
of no use to the iterative scheduling process itself. At any point
during scheduling it is possible to cheaply compute the occupancy
induced by a particular register pressure. Furthermore, the field
doesn't appear to be updated correctly throughout scheduling i.e., bits
corresponding to regions at minimum occupancy are not always set in the
vector.
This removes the bitvector from `GCNScheduleDAGMILive`.
`UnclusteredHighRPStage::initGCNRegion` now directly computes the
occupancy of possibly reschedulable regions instead of querying the
vector. Since it is the most expensive check, it is done last in the
list.
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp')
0 files changed, 0 insertions, 0 deletions