You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #35814, the armv7-unknown-linux-gnueabihf target was changed to not use NEON, but the armv7-unknown-linux-musleabihf target was not changed. I just used the musl target to compile a binary for my router (OpenWRT uses musl), but it dies with "Illegal instruction" in Mutex::new on vld1.32 (a NEON instruction).
Should armv7-unknown-linux-musleabihf have NEON disabled as well? I think it is confusing to have one armv7 target with NEON enabled and the other with it disabled.
The text was updated successfully, but these errors were encountered:
Ah yeah seems like an oversight on our part! I think it'd be fine to remove neon for consistency with the gnu target
nagisa
added
A-codegen
Area: Code generation
O-Arm
Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
labels
Jan 26, 2018
Disable NEON on musl ARMv7
`armv7-unknown-linux-musleabihf` target diverged a bit from `armv7-unknown-linux-gnueabihf` target. This PR re-syncs them.
Fixrust-lang#47765.
kennytm
added a commit
to kennytm/rust
that referenced
this issue
Mar 3, 2018
Disable NEON on musl ARMv7
`armv7-unknown-linux-musleabihf` target diverged a bit from `armv7-unknown-linux-gnueabihf` target. This PR re-syncs them.
Fixrust-lang#47765.
In #35814, the
armv7-unknown-linux-gnueabihf
target was changed to not use NEON, but thearmv7-unknown-linux-musleabihf
target was not changed. I just used the musl target to compile a binary for my router (OpenWRT uses musl), but it dies with "Illegal instruction" inMutex::new
onvld1.32
(a NEON instruction).Should
armv7-unknown-linux-musleabihf
have NEON disabled as well? I think it is confusing to have one armv7 target with NEON enabled and the other with it disabled.The text was updated successfully, but these errors were encountered: