-
Notifications
You must be signed in to change notification settings - Fork 229
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
Debug break during seemingly innocuous Level Zero operations #639
Comments
The assertion ( debug_break_if) is there to catch potential issues with truncating the address, this debug break is not required here - we are using canonized addresses with upper bits set and this HW command truncates upper bits and ignores them. we are adding DEBUG_BREAK_IF() for potential issues that need investigation - so you may see some of them fire when there is nothing wrong in the code. It is possible to disable DebugBreaks with EnableDebugBreak=0 debug variable. |
Perfect, that works, thanks! |
While debugging a Julia/oneAPI.jl-related issue, I was using a debug build of the compute-runtime. Doing so however triggers a debug break with the following seemingly innocuous Level Zero operations:
That's the following debug break:
compute-runtime/shared/source/generated/xe_hpg_core/hw_cmds_generated_xe_hpg_core.inl
Line 6381 in 44273fc
What's the purpose of that debug break? Is my code doing anything wrong? I was hoping to have a CI job on oneAPI.jl run with a debug build of compute-runtime and IGC in order to spot any failed assertions (as these checks aren't present in release mode).
cc @pengtu
The text was updated successfully, but these errors were encountered: