GL_ARB_cl_event: workaround via glFenceSync during replay #856
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
January 18, 2023 14:56
This enough to keep program going despite absence of OpenCL context and any data coming from it.
|
Not sure in what I should pass to trace::FunctionSig and trace::Call constructors. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When replaying glCreateSyncFromCLeventARB, make a typical call to glFenceSync instead.
That would create a sync object which can be waited for and deleted, so from OpenGL view it behaves exactly as desired.
(Of course it does not perform any synchronization with OpenCL context since we don't record/replay OpenCL)