rust-lang / rust-lang/rust-playground
Allow compiling and running for different target architectures
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
I'd like to be able to check the assembly and LLVM-IR generated for different targets in the playground. For that I think the playground should allow at least compiling to different targets, even if the code is never run.
Maybe have a target menu that allows the user to select a target, and which indicates which targets can be run and which targets cannot be run.
Running code for different targets could be allowed in the future, e.g., by using qemu-user as a binary runner like libc,rust, and stdsimd do in their CI to run tests on different targets.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the playground currently compiles and runs Rust code, then identify the entry points for selecting targets and exposing assembly or LLVM-IR. Done means users can choose target architectures, compile for them, and see which targets can be run; qemu-user execution is described as future work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100