summaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
diff options
context:
space:
mode:
authorLucas Ramirez <11032120+lucas-rami@users.noreply.github.com>2025-05-27 17:10:28 +0200
committerGitHub <noreply@github.com>2025-05-27 17:10:28 +0200
commit3e182164740cd6efe20a57d72684672894b3f9d3 (patch)
treebc68423b24914fdb3872068e528fb1300a79f19e /lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
parente90ea09489ba4405f3ff3345b09ab5f99d2b9dcb (diff)
[AMDGPU][Scheduler] Delete RescheduleRegions bitvector from scheduler (NFC) (#141595)
The `GCNScheduleDAGMILive`'s `RescheduleRegions` bitvector is only used by the rematerialization stage (`PreRARematStage`). 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, which instead relies on each stage's `initGCNRegion` hook to determine whether the current region should be rescheduled. This moves the bitvector to the `PreRARematStage`, which uses it to store the set of regions that must be rescheduled between stage initialization and region initialization. This NFC also swaps a call to `GCNRegPressure::getArchVGPRNum(false)` for a call to `GCNRegPressure::getArchVGPRNum()`---which is equivalent but simpler in the context---and makes `GCNSchedStage::finalizeGCNRegion` use its own API to advance to the next region.
Diffstat (limited to 'lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py')
0 files changed, 0 insertions, 0 deletions