[all-commits] [llvm/llvm-project] 96b38f: [AMDGPU] Add intrinsic exposing s_alloc_vgpr

Diana Picus via All-commits all-commits at lists.llvm.org
Fri Oct 17 05:14:04 PDT 2025


  Branch: refs/heads/users/rovka/alloc-vgpr-intrinsic
  Home:   https://github.com/llvm/llvm-project
  Commit: 96b38fbb35a69286b98e72f7f9c4a5d205724616
      https://github.com/llvm/llvm-project/commit/96b38fbb35a69286b98e72f7f9c4a5d205724616
  Author: Diana Picus <diana-magda.picus at amd.com>
  Date:   2025-10-17 (Fri, 17 Oct 2025)

  Changed paths:
    M llvm/include/llvm/IR/IntrinsicsAMDGPU.td
    M llvm/lib/Target/AMDGPU/AMDGPUInstructionSelector.cpp
    M llvm/lib/Target/AMDGPU/AMDGPURegisterBankInfo.cpp
    M llvm/lib/Target/AMDGPU/AMDGPUSearchableTables.td
    M llvm/lib/Target/AMDGPU/SOPInstructions.td
    M llvm/test/Analysis/UniformityAnalysis/AMDGPU/always_uniform.ll
    A llvm/test/CodeGen/AMDGPU/intrinsic-amdgcn-s-alloc-vgpr.ll

  Log Message:
  -----------
  [AMDGPU] Add intrinsic exposing s_alloc_vgpr

Make it possible to use `s_alloc_vgpr` at the IR level. This is a huge
footgun and use for anything other than compiler internal purposes is
heavily discouraged. The calling code must make sure that it does not
allocate fewer VGPRs than necessary - the intrinsic is NOT a request to
the backend to limit the number of VGPRs it uses (in essence it's not so
different from what we do with the dynamic VGPR flags of the
`amdgcn.cs.chain` intrinsic, it just makes it possible to use this
functionality in other scenarios).



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list