Skip to content

Harmonize fpu options on armv7 Linux #31814

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.

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

Merged
merged 1 commit into from
Feb 23, 2016
Merged

Harmonize fpu options on armv7 Linux #31814

merged 1 commit into from
Feb 23, 2016

Conversation

MagaTailor
Copy link

The vfp2 option was a leftover from armv6 compatibility features of the original armhf target.
Gcc defaults to vfp3on armv7 hard-float linux systems so we should make it the default for rustc too.

@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@@ -21,6 +21,6 @@ CFG_UNIXY_armv7-unknown-linux-gnueabihf := 1
CFG_LDPATH_armv7-unknown-linux-gnueabihf :=
CFG_RUN_armv7-unknown-linux-gnueabihf=$(2)
CFG_RUN_TARG_armv7-unknown-linux-gnueabihf=$(call CFG_RUN_armv7-unknown-linux-gnueabihf,,$(2))
RUSTC_FLAGS_armv7-unknown-linux-gnueabihf := -C target-feature=+v7,+vfp2,+neon
RUSTC_FLAGS_armv7-unknown-linux-gnueabihf := -C target-feature=+v7,+vfp3,+neon
Copy link
Member

Choose a reason for hiding this comment

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

This can actually be removed as they're part of the features below as well, would you mind just going ahead and clearing out this line?

@MagaTailor
Copy link
Author

Ah, right - the target's pretty specialised already.

@MagaTailor
Copy link
Author

The only difference it could probably make is stage0; if the snapshot were a standard armhf it would use its default codegen options and not those. It doesn't matter in the long run though.

Wait, I keep forgetting it's a separate target nowadays. Ok, it's done.

@alexcrichton
Copy link
Member

@bors: r+ 8ddd86a

@bors
Copy link
Collaborator

bors commented Feb 23, 2016

⌛ Testing commit 8ddd86a with merge 603e370...

@bors
Copy link
Collaborator

bors commented Feb 23, 2016

💔 Test failed - auto-win-msvc-64-opt

@alexcrichton
Copy link
Member

@bors: retry

On Mon, Feb 22, 2016 at 6:28 PM, bors [email protected] wrote:

[image: 💔] Test failed - auto-win-msvc-64-opt
http://buildbot.rust-lang.org/builders/auto-win-msvc-64-opt/builds/3186


Reply to this email directly or view it on GitHub
#31814 (comment).

bors added a commit that referenced this pull request Feb 23, 2016
The `vfp2` option was a leftover from `armv6` compatibility features of the original armhf target.
Gcc defaults to `vfp3`on `armv7` hard-float linux systems so we should make it the default for rustc too.
@bors
Copy link
Collaborator

bors commented Feb 23, 2016

⌛ Testing commit 8ddd86a with merge be7196a...

@bors bors merged commit 8ddd86a into rust-lang:master Feb 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants