-
Notifications
You must be signed in to change notification settings - Fork 769
[UR] Fixed bug with zero depth ur_rect_region which must be checked before calling func #17681
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
Conversation
looks like there're more files the change needs propagating to, the easiest way is to run the |
Fixed functions: - urEnqueueMemBufferWriteRect() - urEnqueueMemBufferReadRect()
@aarongreig, I fixed all conditions and renamed commit name. |
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.
Good find! 🚀
@GermanAizek it looks like the CI had some issues last week, would you mind updating the branch so it re-runs it against the latest changes? Other than that it should be good to merge, thanks for the patch! |
@intel/llvm-gatekeepers this is ready to merge |
…efore calling func (intel#17681) Its PR migrated from oneapi-src/unified-runtime#2746 It looks like a common typo when writing functions. Fixed functions: - urEnqueueMemBufferWriteRect() - urEnqueueMemBufferReadRect() Co-authored-by: Nicolas Miller <[email protected]>
Its PR migrated from oneapi-src/unified-runtime#2746
It looks like a common typo when writing functions.
Fixed functions: