Open matwey opened 4 years ago
This seems like a beignet issue. The call-stack points deep inside cl::Program::build()
Initially, I supposed that clpeak
may use some feature without explicitly checking it support.
Anyway, I've checked with Beignet from master
, result is the same.
For the record. The same software configuration works well on never CPU:
Platform: Intel Gen OCL Driver
Device: Intel(R) HD Graphics Kabylake ULT GT2
Driver version : 1.3 (Linux x64)
Compute units : 24
Clock frequency : 1000 MHz
Global memory bandwidth (GBPS)
float : 26.90
float2 : 27.86
float4 : 27.67
float8 : 27.20
float16 : 25.87
Single-precision compute (GFLOPS)
float : 364.71
float2 : 379.20
float4 : 378.50
float8 : 376.99
float16 : 375.05
half-precision compute (GFLOPS)
half : 455.54
half2 : 745.82
half4 : 749.58
half8 : 746.53
half16 : 741.75
No double precision support! Skipped
Transfer bandwidth (GBPS)
enqueueWriteBuffer : 25.97
enqueueReadBuffer : 12.41
enqueueMapBuffer(for read) : 113623.47
memcpy from mapped ptr : 12.42
enqueueUnmap(after write) : 119304.65
memcpy to mapped ptr : 12.38
Kernel launch latency : 35.64 us
Raised an issue for Beignet: https://gitlab.freedesktop.org/beignet/beignet/-/issues/84
Thanks
Hello,
I am running
clpeak
from master withbeignet
1.3.2 on openSUSE Leap 15.1. The same behavior with 3rd and 4th Intel CPU generations.When
gdb
is uses to trap the fault:Even if this hardware configuration cannot be supported, I would expect more informative message than the crash.