Skip to content

Commit 6855a7c

Browse files
llvm-beanzdamyanp
andauthored
Agenda and minutes for 2025-09-04 meeting (#334)
This adds the agenda and meeting minutes for the 2025-09-04 meeting. --------- Co-authored-by: Damyan Pepper <[email protected]>
1 parent d1c50e5 commit 6855a7c

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

meetings/2025-09-04.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: 2025-09-04 - HLSL Working Group Minutes
3+
---
4+
5+
> Propose a discussion topic by making an edit suggestion on the GitHub PR.
6+
7+
* Discussion topics
8+
* We had a brief discussion of restrictions on the ternary operator and select intrinsic that are implemented by DXC. We shelved this conversation since it is more appropriate for the language design audience. We will follow up there with a concrete proposal on [hlsl-specs](https://github.com/microsoft/hlsl-specs).
9+
* [Feature Profiles](https://gist.github.com/llvm-beanz/07094cdc9ef49e4897d38474eef4ef92)
10+
* Tex raised concerns about conflating profiles and feature tiers, suggesting that feature tiers should be separate from target profiles and specified indipendently.
11+
* Chris: The proposal as written describes profiles as a base target and required feature set, but provides options to override the base values. This should cover the full use cases.
12+
* It was difficult to reach consensus without a fleshed out proposal to review.
13+
* Nathan suggested allowing for user-defined profiles as well as compiler-provided profiles.
14+
* Action Item: Chris to flesh out and post the proposal to [wg-hlsl](https://github.com/llvm/wg-hlsl/).
15+
* CBuffer Update
16+
* Justin put up a draft PR, hopefully this unblocks - https://github.com/llvm/llvm-project/pull/156919.
17+
* Status of semantics
18+
* Action Item: Chris to review https://github.com/llvm/llvm-project/pull/152537
19+
* Request for feedback on RFC: https://discourse.llvm.org/t/rfc-adding-instructions-to-to-carry-gep-type-traversal-information/88141

0 commit comments

Comments
 (0)