We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Regressed by intel/compute-runtime@691a4ea
I wonder if Intel bindings need to be updated.
$ ze_peak zeDriverGet... Device : * name : Intel(R) Gen9 * vendorId : 32902 * deviceId : 6418 * subdeviceId : 0 * isSubdevice : FALSE * coreClockRate : 1150 * numAsyncComputeEngines : 3 * numAsyncCopyEngines : 0 * maxCommandQueuePriority : 0 Process 82663 stopped * thread #1, name = 'ze_peak', stop reason = signal SIGABRT frame #0: 0x000000080060b02a libc.so.7`__sys_thr_kill at thr_kill.S:4 (lldb) bt * thread #1, name = 'ze_peak', stop reason = signal SIGABRT * frame #0: 0x000000080060b02a libc.so.7`__sys_thr_kill at thr_kill.S:4 frame #1: 0x000000080060a9c4 libc.so.7`__raise(s=6) at raise.c:52:10 frame #2: 0x0000000800573459 libc.so.7`abort at abort.c:67:8 frame #3: 0x00000008003d6a49 libcxxrt.so.1`report_failure(err=<unavailable>, thrown_exception=0x0000000802717fa8) at exception.cc:719:5 frame #4: 0x000000000020df59 ze_peak`L0Context::init_xe(this=0x00007fffffffde70) at ze_peak.cpp:183:5 frame #5: 0x00000000002115d9 ze_peak`main(argc=1, argv=0x00007fffffffe0f0) at ze_peak.cpp:760:11 frame #6: 0x000000000020b8bf ze_peak`_start(ap=<unavailable>, cleanup=<unavailable>) at crt1.c:76:7 (lldb) f 4 frame #4: 0x000000000020df59 ze_peak`L0Context::init_xe(this=0x00007fffffffde70) at ze_peak.cpp:183:5 180 result = 181 zeCommandListCreate(device, &command_list_description, &command_list); 182 if (result) { -> 183 throw std::runtime_error("zeDeviceCreateCommandList failed: " + 184 std::to_string(result)); 185 } 186 if (verbose)
The text was updated successfully, but these errors were encountered:
Nevermind. This could be a bug unrelated to ABI.
Sorry, something went wrong.
No branches or pull requests
Regressed by intel/compute-runtime@691a4ea
I wonder if Intel bindings need to be updated.
The text was updated successfully, but these errors were encountered: