Crates.io | rcublas |
lib.rs | rcublas |
version | 0.6.0 |
source | src |
created_at | 2017-06-12 14:10:28.530419 |
updated_at | 2021-11-21 11:13:53.844452 |
description | safe Rust wrapper for CUDA's cuBLAS |
homepage | https://github.com/spearow/juice/tree/master/rcublas |
repository | https://github.com/spearow/juice |
max_upload_size | |
id | 18714 |
size | 55,574 |
rust-cuBLAS provides a safe wrapper for CUDA's cuBLAS library, so you can use cuBLAS comfortably and safely in your Rust application.
As cuBLAS currently relies on CUDA to allocate memory on the GPU, you might also look into [rust-cuda][rust-cuda].
rust-cublas is part of the High-Performance Computation Framework Coaster, for the BLAS Plugin. For an easy, unified interface for BLAS operations, such as those provided by cuBLAS, you might check out Coaster.
For more information,
If you're using Cargo, just add rust-cuBLAS to your Cargo.toml:
[dependencies]
cublas = "0.2.0"
If you're using Cargo Edit, you can call:
$ cargo add cublas
The library can be built by entering cublas/
and cublas-sys/
, and issuing a
cargo build
within each directory.
rust-cublas depends on the cuBLAS runtime libraries, which can be obtained from NVIDIA.
rust-cublas's build script will by default attempt to locate cublas
via pkg-config.
This will not work in some situations, for example,
/usr/lib
).Therefore the build script can be configured by exporting the following environment variables:
CUBLAS_LIB_DIR
If specified, a directory that will be used to find cuBLAS runtime libraries.
e.g. /opt/cuda/lib
CUBLAS_STATIC
If specified, cuBLAS libraries will be statically rather than dynamically linked.
CUBLAS_LIBS
If specified, will be used to find cuBLAS libraries under a different name.
If either CUBLAS_LIB_DIR
or CUBLAS_INCLUDE_DIR
are specified, then the build script will skip the pkg-config step.
If your also need to run the compiled binaries yourself, make sure that they are available:
# Linux; for other platforms consult the instructions that come with cuBLAS
cd <cublas_installpath>
export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH
Want to contribute? Awesome! We have instructions to help you get started contributing code or documentation.
We have a mostly real-time collaboration culture and happens here on Github and on the Gitter Channel.
You can find the release history in the root file CHANGELOG.md.
A changelog is a log or record of all the changes made to a project, such as a website or software project, usually including such records as bug fixes, new features, etc. - Wikipedia
We are using Clog, the Rust tool for auto-generating CHANGELOG files.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.