`hexagon-unknown-linux-musl` target linking generate misaligned/broken binary
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Rust nightly -Z build-std and -W linker-messages
hexagon-unknown-linux-musl target binary can't be run.
warning: linker stdout: Misaligned constant address: 0x80000006 has alignment 2, but the memory access requires 4. The instruction has been replaced with a trap.
Misaligned constant address: 0x80000002 has alignment 2, but the memory access requires 4. The instruction has been replaced with a trap.
Misaligned constant address: 0x80000006 has alignment 2, but the memory access requires 4. The instruction has been replaced with a trap.
Misaligned constant address: 0x80000002 has alignment 2, but the memory access requires 4. The instruction has been replaced with a trap.
│
╰ note: requested on the command line with `-W linker-messages`
I think rust should enable -W linker-messages by default, for better telling programmer some hidden warnings which can incur broken/crashed binary.
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
Start by reproducing the hexagon-unknown-linux-musl build with nightly -Z build-std and -W linker-messages, then inspect the emitted misalignment warnings and resulting binary behavior. Determine whether the linker warnings should be enabled by default and verify that the target binary no longer becomes un runnable or that the warning behavior is clearly covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100