[all-commits] [llvm/llvm-project] d76890: [AMDGPU][Doc] Move barrier documentation to a sepa...

Pierre van Houtryve via All-commits all-commits at lists.llvm.org
Wed May 6 00:50:39 PDT 2026


  Branch: refs/heads/users/pierre-vh/standalone-barrier-docs
  Home:   https://github.com/llvm/llvm-project
  Commit: d76890555522b85007f38798bc70c6092dfd3fe8
      https://github.com/llvm/llvm-project/commit/d76890555522b85007f38798bc70c6092dfd3fe8
  Author: pvanhout <pierre.vanhoutryve at amd.com>
  Date:   2026-04-30 (Thu, 30 Apr 2026)

  Changed paths:
    A llvm/docs/AMDGPUExecutionSynchronization.rst
    M llvm/docs/AMDGPUUsage.rst
    M llvm/docs/UserGuides.rst

  Log Message:
  -----------
  [AMDGPU][Doc] Move barrier documentation to a separate document

Create a new "AMDGPU Execution Synchronization" document.
For now, it just documents barriers and their execution model.
Hopefully, over time, we can improve it to document the
programming model of most common methods of synchronizing execution
of threads (e.g. using memory/spinlock).

I kept the documentation mostly as-is, but I did do some minor changes
to make it flow a bit better as a standalone document. For example,
the fact that barriers work at a wavefront granularity has been moved
to the section about `s_barrier` specifically.
I also moved the note about barrier objects existing within a scope
in the main documentation. As a result, the "target-specific properties"
section has been eliminated.


  Commit: 7986683519a8875e421978ef40629ef8c59b1302
      https://github.com/llvm/llvm-project/commit/7986683519a8875e421978ef40629ef8c59b1302
  Author: pvanhout <pierre.vanhoutryve at amd.com>
  Date:   2026-05-06 (Wed, 06 May 2026)

  Changed paths:
    M llvm/docs/AMDGPUExecutionSynchronization.rst

  Log Message:
  -----------
  scope -> scope instance


Compare: https://github.com/llvm/llvm-project/compare/e867cb0b30bd...7986683519a8

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