Skip to content
This repository has been archived by the owner on Apr 28, 2023. It is now read-only.

Repromote from shared to private memory #554

Open
ftynse opened this issue Jul 5, 2018 · 0 comments
Open

Repromote from shared to private memory #554

ftynse opened this issue Jul 5, 2018 · 0 comments
Labels
enhancement New feature or request polyhedral

Comments

@ftynse
Copy link
Contributor

ftynse commented Jul 5, 2018

If a tensor reference group is promoted to shared memory at some scope, it may be interesting to promote it to registers at some deeper scope. There are two possibilities:

  • promote to registers instead of promoting to shared (freeing the shared memory for other uses or for increased occupancy);
  • promote to registers from shared, hiding global access latency and/or having more coalescing when copying from global to shared.

#161 and #217 attempted this behavior; first by demoting from shared memory, then by promoting from shared to private. Demotion from shared was mostly harmful, principally because promotion to registers was too deep and rarely beneficial by itself. The effect may be different with tunable promotion depth, so we can start by having this behavior controlled by a flag.

@ftynse ftynse added polyhedral enhancement New feature or request labels Jul 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request polyhedral
Projects
None yet
Development

No branches or pull requests

1 participant