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

Remove stale comment #2542

Merged
merged 1 commit into from
May 1, 2019
Merged

Remove stale comment #2542

merged 1 commit into from
May 1, 2019

Conversation

zoddicus
Copy link
Contributor

Fixes #1121

@zoddicus
Copy link
Contributor Author

The issue listed (#1121) is about making sure that shader entry point functions are void(). My understanding reading the existing code is that this is already being checked, just the comments are a bit out of date. I am just updating the comments and closing out the issue with this PR.

@zoddicus zoddicus merged commit a5da68d into KhronosGroup:master May 1, 2019
@zoddicus zoddicus deleted the issue1121 branch May 1, 2019 14:56
afd pushed a commit to afd/SPIRV-Tools that referenced this pull request May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OpEntryPoint: shader entry points have void(void) signature
2 participants