registers

Separate storage scope from physical backing, then follow a warp through adjacent and strided loads. Count useful bytes and requested sectors before inferring HBM traffic or speed.

Derive a block-level occupancy limit, then compare the extra residency with spill traffic and lost reuse. Use a matched experiment rather than a target percentage.

Derive resident-block limits and distinguish resident warps from ready work before trading registers for more occupancy.

A few extra live values can change register allocation, residency, generated instructions or spills. Compare compiler evidence with runtime behavior before attributing a 30% slowdown to any one of them.