Potential failure to set context when recording an event #314
Labels
Comments
eyalroz
changed the title
|
Well, turns out it may not be ok after all. |
eyalroz
added a commit
that referenced
this issue
Apr 13, 2022
…Also, * A scoped context setter variable was mis-named as a device setter (probably forgot to rename it when making the big switch to being driver-based). * Rephrased an error message regarding enqueuing an event on a stream in another context.
eyalroz
added a commit
that referenced
this issue
Apr 13, 2022
eyalroz
added a commit
that referenced
this issue
Apr 16, 2022
…(e.g. on a stream). Also, * Defined an `event::detail_::flags_t` type. * A scoped context setter variable was mis-named as a device setter (probably forgot to rename it when making the big switch to being driver-based). * Rephrased an error message regarding enqueuing an event on a stream in another context.
eyalroz
added a commit
that referenced
this issue
Jun 20, 2022
…(e.g. on a stream). Also, * Defined an `event::detail_::flags_t` type. * A scoped context setter variable was mis-named as a device setter (probably forgot to rename it when making the big switch to being driver-based). * Rephrased an error message regarding enqueuing an event on a stream in another context.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
cuda::event::record(), we're currently not setting the context. This may be ok, but let's be on the safe side.The text was updated successfully, but these errors were encountered: