Skip to content
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

Nightly Features can be replaced ? #42

Open
albertoazzari opened this issue Jul 22, 2024 · 1 comment
Open

Nightly Features can be replaced ? #42

albertoazzari opened this issue Jul 22, 2024 · 1 comment

Comments

@albertoazzari
Copy link

Hi, might I ask what nightly features are required in krnl?

Generally, nightly builds are quite unstable (some features available in nightly might never make it to stable and could be removed entirely). Relying on stable versions would be more robust, especially if the necessary features can be replaced by macros or crates compatible with stable versions.

@charles-r-earp
Copy link
Owner

Hello! This is somewhat covered in the docs.

krnlc uses nightly to get the crate source in token form, parsed by syn. This is how it locates modules. See rust-lang/rust#43364.

rust-gpu is used to compile kernels to SPIR-V. It replaces Rust's LLVM backend with its own, which requires nightly features and only works (more or less) with that exact nightly. Many other projects, like Rust-CUDA, work in a similar way, with the same limitation. While there is plenty of interest in stabilizing this, I don't see that being realistic anytime soon. See rust-lang/rust#77933.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants