Tracking Issue for GPU-offload #131513
Labels
B-experimental
Blocker: In-tree experiment; RFC pending, not yet approved or unneeded (requires FCP to stabilize).
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
F-gpu_offload
`#![feature(gpu_offload)]`
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
Comments
ZuseZ4
added
the
C-tracking-issue
jieyouxu
added
T-lang
Zalathar
added a commit
to Zalathar/rust
that referenced
this issue
Oct 26, 2024
…, r=Kobzol Enable the llvm offload build configuration Tracking: - rust-lang#131513
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 26, 2024
…r=Kobzol Enable the llvm offload build configuration Tracking: - rust-lang#131513
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 26, 2024
…r=Kobzol Enable the llvm offload build configuration Tracking: - rust-lang#131513
traviscross
added
the
B-experimental
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for the GPU offload experiment.
The feature gate for the issue will be
#![feature(gpu_offload)].This work is part of the project goal for Scientific Computing in Rust.
This project will use LLVM's offload infrastructure, which is already used to support OpenMP Offload in other languages like C++.
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
Unresolved Questions
TODO.
Implementation history
The text was updated successfully, but these errors were encountered: