Open maedoc opened 2 years ago
This is because the ISPC kernels are in a separate .o
file. futhark-pycffi will have to be modified to also include that in the .so
that gets built. (I don't actually remember who builds the .so
.)
when doing ISPC classically (i.e. hand written / without Futhark), I used ISPC to build the .o
, c++
to build tasksys.cpp
(does Futhark use this or it's still single core only?), and then c++ -shared
to build the .so
.
Futhark's ISPC backend uses its own scheduler, not tasksys.cpp
.
Probably a clause needs to be added here to link the correct stuff
Using the ISPC backend I've got a missing symbol (the C backend works fine, and plain
futhark bench --backend=ispc bench_epiloss.fut
also works),I'll poke at it, but wanted to report.