-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support Pocl for CPU-only OpenCL implementation #69
Comments
Sample usage on Pocl and Travis: https://github.com/boostorg/compute/blob/master/.travis.yml |
PoW linking to Pocl was not functioned as expected:
Reported by
|
The reason might be that I only configure GPU devices on the dcurl. Line 171 in 5dc6479
|
@jserv Should we create a now BUILD option in Makefile for CI test? E.g.
|
Never write code dedicated to CI. We can provide some shotcuts or helper functions instead. |
Maybe we should reserve the flexibility to let the user can configure their own OpenCL implementation. And we can provide some pre-tested config file like GPU or Pocl. |
I agree with the way to improve the flexibility of adopting various OpenCL implementations like Pocl. |
Since the current CI system is |
Close the historical issue |
Current GPU-accelerated PoW is implemented via OpenCL, and Travis-CI in general doesn't have GPUs. The good thing about OpenCL is that you can use a CPU implementation of OpenCL, such as Pocl, which uses Clang as an OpenCL C frontend and LLVM for kernel compiler implementation, and as a portability layer.
Pocl packages are available in recent Debian/Ubuntu repositories:
Utilities such as
clinfo
can find the new pocl ICD viaThe text was updated successfully, but these errors were encountered: