`assembler label '' cannot be undefined` on Windows ARM
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Whenever I try compiling turborepo on Windows ARM, I get the following error when rustc tries to build tokio:
error: assembler label '' can not be undefined
I'd expect this code to compile, since it works fine on other platforms (macOS/Linux/Windows x86).
Meta
rustc --version --verbose:
rustc 1.82.0-nightly (0d634185d 2024-08-29)
binary: rustc
commit-hash: 0d634185dfddefe09047881175f35c65d68dcff1
commit-date: 2024-08-29
host: aarch64-pc-windows-msvc
release: 1.82.0-nightly
LLVM version: 19.1.0
Backtrace
I don't seem to get a backtrace on Windows, even when setting via set RUST_BACKTRACE=1
Here's all I get:
error: assembler label '' can not be undefined
Compiling hyper v1.4.1
Compiling console v0.15.7
Compiling proc-macro-crate v3.1.0
Compiling async-graphql-parser v7.0.7
Compiling crossterm v0.27.0
Compiling turborepo-vercel-api v0.1.0 (C:\Users\nicholas\turbo\crates\turborepo-vercel-api)
Compiling turborepo-ci v0.1.0 (C:\Users\nicholas\turbo\crates\turborepo-ci)
Compiling itertools v0.12.0
Compiling stability v0.1.1
Compiling lru v0.12.2
Compiling memoffset v0.7.1
Compiling encoding_rs v0.8.32
error: could not compile `tokio` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
Contributor guide
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
The report involves rustc 1.82.0-nightly, LLVM 19.1.0, tokio, and the aarch64-pc-windows-msvc target; first reproduce the build on Windows ARM. Trace the compiler or assembler-label path producing the empty-label error, then verify that tokio compiles on this target without regressing the reported working platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100