Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow capabilities to be used with [shader("...")] #4928

Conversation

ArielG-NV
Copy link
Contributor

@ArielG-NV ArielG-NV commented Aug 27, 2024

Fixes: #4917

Changes:

  1. Allow using capabilities instead of Stages with EntryPointAttribute.
  2. When resolving capabilities for an entrypoint+profile (per entrypoint) in resolveStageOfProfileWithEntryPoint add our EntryPointAttribute capabilities.
  3. Added tests and some capabilities related clean-up

Note: due to 'Profile' still being used internally we cannot pass EntryPointAttribute capabilities to IR (and require spirv versions using EntryPointAttribute), related to #4421

Fixes: shader-slang#4917

Changes:
1. Allow using capabilities instead of `Stage`s with `EntryPointAttribute`.
2. When resolving capabilities for an entrypoint+profile (per entrypoint) in `resolveStageOfProfileWithEntryPoint` add our `EntryPointAttribute` and resolved capability
3. Added tests and some capabilities related clean-up
@ArielG-NV ArielG-NV added the pr: non-breaking PRs without breaking changes label Aug 27, 2024
@ArielG-NV ArielG-NV marked this pull request as draft August 28, 2024 01:10
@ArielG-NV ArielG-NV marked this pull request as ready for review August 28, 2024 05:44
@ArielG-NV ArielG-NV marked this pull request as draft August 28, 2024 05:45
@ArielG-NV ArielG-NV marked this pull request as ready for review August 28, 2024 15:30
csyonghe
csyonghe previously approved these changes Aug 28, 2024
alias callable = _callable + raytracing;
alias miss = _miss + raytracing;

alias mesh = _mesh + meshshading_internal;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it be _meshshading_internal?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The capability should be renamed👍
I think we can just do _meshshading since this capability pairs with meshshading.

@csyonghe csyonghe merged commit 65240d0 into shader-slang:master Aug 28, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: non-breaking PRs without breaking changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Capability System: Allow alias's to properly be used with [shader("...")] attribute logic
2 participants