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).
$ rustc --print cfg --target armv7-unknown-linux-musleabihf | grep neon
target_feature="neon"
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.
In #35814, the
armv7-unknown-linux-gnueabihftarget was changed to not use NEON, but thearmv7-unknown-linux-musleabihftarget 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::newonvld1.32(a NEON instruction).Should
armv7-unknown-linux-musleabihfhave NEON disabled as well? I think it is confusing to have one armv7 target with NEON enabled and the other with it disabled.