ocl
Documentation | Change Log
OpenCL™ interfaces for Rust. Makes easy to use the most common features of OpenCL. All interfaces are virtually zero-cost and perform on a par with any C++ libraries.
Interfaces are still mildly unstable. Changes are now being documented in RELEASES.md.
Goals
To provide:
- A simple and intuitive interface with OpenCL devices
- The full functionality of the OpenCL API
- An absolute minimum of boilerplate
- As close as possible to zero performance overhead
- Safe and painless management of API resources and pointers
Installation
Ensure that an OpenCL library is installed for your platform and that clinfo
or some other diagnostic command will run.
Add:
= "0.6"
ocl
to your project's Cargo.toml
.
Example
From 'examples/trivial.rs':
extern crate ocl;
use ;
Platforms
Tested so far only on Linux (and probably OS X - need confirmation). Windows support looks imminent. Please provide feedback about failures and successes on your platform.
Diving Deeper
Already familiar with the standard OpenCL core API? See the core
module for
access to the complete feature set with Rust's safety and convenience.
Taking Requests
Want to bring your OpenCL-ness to Rust but can't find the functionality you need? File an issue and let us know what should come next.
2.0+ Version Support
Due to this developer continuing to have problems getting 2.0 drivers to work properly with his multi-gpu AMD Linux configuration, 2.0 & 2.1 support is on hold. APIs are being designed with their future support in mind however.
On a side note. 1.1 support is intact but intentionally disabled for simplicity. If anyone needs this support for this please file an issue and I will reenable it right away. Automatic best-version support for versions going all the way back to 1.0 will eventually be included once some time can be spent on that.
What About Vulkan™?
The OpenCL API already posesses all of the new attributes of the Vulkan API such as low-overhead, high performance, and unfettered hardware access. For all practical purposes, Vulkan is simply a graphics-focused superset of OpenCL's features (sorta kinda). OpenCL 2.1+ and Vulkan kernels/shaders now both compile into SPIR-V making the device side of things the same. I wouldn't be suprised if most driver vendors will implement the two host APIs identically.
Moving forward it's possible the two may completely merge (or that Vulkan will
absorb OpenCL). Whatever happens, not much will change as far as the front end
of this library is concerned (though the core
module functions / types could
get some renaming, etc. but it wouldn't be for a very long time... version
2.0...). This library will maintain it's focus on the compute side of things.
For the graphics side, see the excellent OpenGL library, glium, and its
younger sibling, vulkano.
Help
If troubleshooting your OpenCL drivers: check that /usr/lib/libOpenCL.so.1
exists. Go ahead and link /usr/lib/libOpenCL.so -> libOpenCL.so.1
just in
case it's not already done (AMD drivers sometimes don't create this link). Intel also has OpenCL libraries for your CPU if you're having trouble getting your GPU to work (AMD used to have some for CPUs too, can't find them anymore).
Please ask questions and provide feedback by opening an issue.
“OpenCL and the OpenCL logo are trademarks of Apple Inc. used by permission by Khronos.” “Vulkan and the Vulkan logo are trademarks of the Khronos Group Inc.”