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

Don't use inheritence for L0 V2 event handles #2630

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

RossBrunton
Copy link
Contributor

In the future, we are going to require that handle objects have no
vtable, so this change combines "native" and "pooled" event into one
class. A variant is used to determine whether the event is native or
pooled.

For consistency, parameter order in constructors have been changed to
always start with the context.

@github-actions github-actions bot added the level-zero L0 adapter specific issues label Jan 28, 2025
@RossBrunton RossBrunton force-pushed the ross/v2devirtualevent branch 10 times, most recently from 6d5ad1c to 7c026d8 Compare January 28, 2025 16:22
@RossBrunton RossBrunton marked this pull request as ready for review January 29, 2025 11:37
@RossBrunton RossBrunton requested a review from a team as a code owner January 29, 2025 11:37
source/adapters/level_zero/v2/event.hpp Outdated Show resolved Hide resolved
In the future, we are going to require that handle objects have no
vtable, so this change combines "native" and "pooled" event into one
class. A variant is used to determine whether the event is native or
pooled.

For consistency, parameter order in constructors have been changed to
always start with the context.
@RossBrunton
Copy link
Contributor Author

LLVM testing doesn't test L0 version 2, so I'll trust that the CI testing is sufficient and merge it.

@RossBrunton RossBrunton merged commit 0fd6433 into oneapi-src:main Jan 29, 2025
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level-zero L0 adapter specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants