-
Notifications
You must be signed in to change notification settings - Fork 116
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
Run check-continuations in CI #2720
Conversation
Doesn't actually pass. Part apart from that it LGTM. |
Rebased and now also runs |
Test summary for commit a22df28CTS tests (Failed: 0/137949)
Ubuntu navi3x, SrdcvkUbuntu navi2x, Srdcvk |
The SavedRegisterValues vector was accessed after its allocation went out of scope, make the value owned to prevent that.
Add check-continuations to the GitHub Actions workflows.
Sanitizers found the first bug in continuations :) |
Test summary for commit 3b34a48CTS tests (Failed: 0/137941)
Ubuntu navi3x, SrdcvkUbuntu navi2x, Srdcvk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice :)
Hmm, looks like there's at least one more, actually?
The first loop in the post-process pass should only handle start functions, not resume functions as their arguments are different. Fix this by filtering out resume functions. This fixes a regression introduced in the lgc.rt.shaderstage patch. It asserted in a registercount test.
Cherry-pick an internal patch to fix tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
retest this please |
Test summary for commit 09ef5e5CTS tests (Failed: 0/138020)
Ubuntu navi3x, SrdcvkUbuntu navi2x, Srdcvk |
Add check-continuations to the GitHub Actions workflows.