Design Meeting Minutes: 2025/11/25

NOTE: Please read the terms of participation (“Terms”) prior to joining the Teams meeting. You joining the Teams meeting with Microsoft indicates your acknowledgement, agreement, and consent to these Terms. If you do not agree to these Terms, please do not join the meeting.

If you intend to contribute code or other copyrightable materials (e.g. written comments, tools, documentation, etc.) to the hlsl specs repository, you are required to sign a Contributor License Agreement (CLA). For details, visit https://cla.microsoft.com.

Administrivia

• No updates

Issues

• No marked issues

PRs

Carried Forward

• [dxil] Proposal to add new debug printf dxil op
  • @tex3d will review this in more detail.
• [202x] Propose adding vk::SampledTexture* types
  • Ready to merge.
• Add proposal for scalar layout for constant buffers
  • Action Item @llvm-beanz - Move to merge.
• Rough proposal collecting thoughts on uniformity
  • Action Item: @llvm-beanz to update
• New Proposal: Draft proposal to modify resource typing in HLSL
  • Action Item: @llvm-beanz to work with author
• [0001] Consider targeting 202x for hlsl namespace
  • Revisit after namespace fixes in DXC go in.
• [0023] Adopt C++11 Base
  • Action item: @llvm-beanz to complete design
• [0032] Constructors
  • Action item: @llvm-beanz to complete design #526

Current Business

• Needs Review
  • bitfields spec language
    • Action item: @llvm-beanz & @imbelic to review
• Call to accept
  • C++ Attributes
    • There was some discussion about the attribute syntax for bindings. In particular the current proposal’s text would deprecate applying resource bindings on user-defined types and having the binding apply to the members.
    • Action Item: @llvm-beanz to update proposal to clarify that specific attributes are not final.
    • Accepted by overall consensus.
  • Restricted Unbounded Arrays
    • Accepted by overall consensus.
  • groupshared arguments
    • One point of discussion was around the [noinline] attribute.
      • There is a desire that this work in the future.
      • The current implementation in DXC is quite hacky.
      • @llvm-beanz and @tex3d agreed that this is unlikely to be a standardizable feature since it doesn’t work across APIs and likely needs changes to DXIL and SPIRV for accurate code generation.
    • Action Item: @spall to update with overloading semantics.
    • Accepted by overall consensus.

Discussion Topics

Other Discussion