Skip to content

Don't use SSE4.1 instructions unless the target supports it #140

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

Closed
wants to merge 1 commit into from

Conversation

mbrubeck
Copy link
Contributor

@mbrubeck mbrubeck commented Jun 14, 2016

Fixes #48. r? @pcwalton

Enabling the SIMD code path now requires building with
RUSTFLAGS="-C target-feature=+sse4.1" or similar.


This change is Reviewable

Fixes servo#48.

Enabling the SIMD code path now requires building with
`RUSTFLAGS="-C target-feature=+sse4.1"` or similar.
@metajack
Copy link
Contributor

Can we not use features somehow for this? Using RUSTFLAGS is not something we're supposed to be doing is what I understood from the Cargo team.

@Manishearth
Copy link
Member

We can, we need to add a build script that checks for features and adds to cargo: rustc-args. I'm not sure if all args (e.g. -C) can be touched with this argument, though.

@bors-servo
Copy link
Contributor

☔ The latest upstream changes (presumably #141) made this pull request unmergeable. Please resolve the merge conflicts.

@nox
Copy link
Contributor

nox commented Aug 2, 2016

Is there no way for rustc to be hinted to use SSE4.1 by itself if it can, with the naive code?

bors-servo pushed a commit that referenced this pull request Jan 17, 2018
Don't use SSE4.1 instructions unless the target supports it

This is a rebase of #140.

Fixes #140, fixes #48.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/euclid/263)
<!-- Reviewable:end -->
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