Skip to content

musl ARMv7 uses NEON #47765

@jminer

Description

@jminer

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.

Activity

alexcrichton

alexcrichton commented on Jan 26, 2018

@alexcrichton
Member

Ah yeah seems like an oversight on our part! I think it'd be fine to remove neon for consistency with the gnu target

added
A-codegenArea: Code generation
O-ArmTarget: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
on Jan 26, 2018
added a commit that references this issue on Mar 3, 2018
414dddf
added a commit that references this issue on Mar 3, 2018
ae6fe8f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-codegenArea: Code generationO-ArmTarget: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @alexcrichton@nagisa@jminer

        Issue actions

          musl ARMv7 uses NEON · Issue #47765 · rust-lang/rust