Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,699
    • Issues 2,699
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 908
    • Merge requests 908
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Merge requests
  • !5207

spirv,aco: set restrict by default and use SMEM if we know it's safe

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Rhys Perry requested to merge pendingchaos/mesa:aco_use_smem_if_no_vmem into master May 26, 2020
  • Overview 77
  • Commits 13
  • Pipelines 37
  • Changes 12

This MR enables SMEM for 8/16-bit accesses and on GFX6/7 and disables it if we can't prove that it's safe. This requires that SPIR-V -> NIR sets ACCESS_RESTRICT by default so that we handle SpvDecorationAliased correctly.

Some ideas to improve this:

  • use better alias analysis by using deref information, range analysis and comparing offsets
  • consider control flow and ordering
  • take advantage that SMEM and VMEM should be coherent if both are GLC=1

The last two require that we wait when switching between VMEM and SMEM if one operation is a store.

I'm not too certain about the SPIR-V -> NIR changes

Edited Jun 22, 2020 by Rhys Perry
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: aco_use_smem_if_no_vmem