-
Notifications
You must be signed in to change notification settings - Fork 8
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
Consider limiting supported targets for initial stabilization #86
Comments
This is a great idea! I've been using Finally, whenever the topic of eeking out performance, or cutting down binary size is brought up, I think something as complex as building the standard library is going to be a hard thing to get right the first time, and to be honest there will always be some target-specific edge cases that most likely cannot be handled. I don't think we should block this feature, or core (heh) bits of this feature that do work well, trying to cater to every edge case both known and unknown. |
For my project, I've been using build-std to build the core lib for the riscv32ima target. See this comment for why I did.: embassy-rs/embassy#1278 (comment) It works great, but since then all dependencies are now able to build on stable rust. The only reason I cannot switch to stable yet, is the build-std feature. I asked around if I could add the target to the growing list of tier 2 Risc32 targets, and the maintainer isn't opposed to doing this, but other people asked questions about the need of adding barely used targets to the list. Stabilizing build-std or supporting targets that are extendible like riscv on stable in some other way, would be really nice. Until then, I will continue to work on nightly. |
Would limiting components to be built also help with initial stabilization? Even just Core would be helpful for many bare-metal projects that target riscv32. |
It seems likely that getting build-std working on all targets is going to be a large effort (small example is #30). If it looks like trying to get every target working is going to be too much effort, we may want to consider somehow only supporting blessed targets (either by specifying which targets are supported, or which ones aren't) for the initial release.
The text was updated successfully, but these errors were encountered: