Skip to content

add armv7 target #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

add armv7 target #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .travis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ matrix:
arch: arm64
env: RUSTFLAGS=-Ctarget-cpu=native

# Linux (armv7)
- name: "armv7-unknown-linux-gnueabihf (neon)"
os: linux
arch: arm64
env: RUSTFLAGS=-Ctarget-feature=+neon
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding +neon after the fact to the armv7-unknown-linux-gnueabihf target results in terrible performance due to the mismatch between the pre-built std and what's being built with +neon.

The target that doesn't suffer from this problem is thumbv7neon-unknown-linux-gnueabihf, which bakes the neon option into the target definition and, therefore, comes with neon-enabled std.


# Linux (powerpc64le)
- name: "powerpc64le-unknown-linux-gnu (altivec, vsx, power8-*)"
os: linux
Expand Down