[all-commits] [llvm/llvm-project] 3de583: [AMDGPU][Doc] GFX12.5 Barrier Execution Model (#18...
Pierre van Houtryve via All-commits
all-commits at lists.llvm.org
Fri Apr 10 01:44:51 PDT 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 3de583e09f00d821fbde28463a5a14ff121bfd6b
https://github.com/llvm/llvm-project/commit/3de583e09f00d821fbde28463a5a14ff121bfd6b
Author: Pierre van Houtryve <pierre.vanhoutryve at amd.com>
Date: 2026-04-10 (Fri, 10 Apr 2026)
Changed paths:
M llvm/docs/AMDGPUUsage.rst
Log Message:
-----------
[AMDGPU][Doc] GFX12.5 Barrier Execution Model (#185632)
- Document GFX12.5-specific intrinsics.
- Rename signal -> arrive, leave -> drop to match C++ terminology.
- Update execution model to support GFX12.5 semantics (e.g. threads can
arrive w/o waiting)
- Various clean-ups & wording updates on the model.
- Added "mutually exclusive" barrier objects.
- Added barrier-phase-with + related constraints.
- Document that barriers can exist at cluster scope too.
- Update GFX12 target semantics/code sequences to include GFX12.5.
The model is no longer marked as incomplete, it is now just
experimental.
There are more updates planned in the future to support more features,
and
improve some known shortcomings of the model. e.g., currently many
relations
encode too much semantic information, which means the model doesn't
build
when barriers aren't used correctly. I'd like the model to eventually
represent
broken executions as well, just like a memory model can.
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