Skip to content
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

use of unstable library feature 'stdsimd' #57

Closed
ous51m1 opened this issue Feb 8, 2020 · 10 comments
Closed

use of unstable library feature 'stdsimd' #57

ous51m1 opened this issue Feb 8, 2020 · 10 comments

Comments

@ous51m1
Copy link

ous51m1 commented Feb 8, 2020

how can i move on with my life

error[E0658]: use of unstable library feature 'stdsimd'
   --> /home/oussama/.cargo/registry/src/github.com-1ecc6299db9ec823/blake3-0.1.4/src/platform.rs:266:12
    |
266 |         if is_x86_feature_detected!("avx512f") && is_x86_feature_detected!("avx512vl") {
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: for more information, see https://github.com/rust-lang/rust/issues/27731
    = help: add `#![feature(stdsimd)]` to the crate attributes to enable
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `blake3`.
@oconnor663
Copy link
Member

oconnor663 commented Feb 8, 2020

This is a bug in nightly. See #56 and rust-lang/rust#68905.

Until this is fixed, if you have to use nightly, you will need to use a nightly version from before this bug was introduced. I don't know exactly when that was yet, but probably a couple weeks ago would be fine?

@ous51m1
Copy link
Author

ous51m1 commented Feb 8, 2020

thanks @oconnor663 i switched to stable and my problem is now resolved :)

@oconnor663
Copy link
Member

It looks like nightly-2020-02-06 is the first compiler version with this issue. Anything prior to that should work.

@oconnor663
Copy link
Member

oconnor663 commented Feb 10, 2020

I've released version 0.1.5, which is a backport of af2e791. This should unbreak nightly builds of the blake3 crate with the default feature set. Only callers who enable the c_avx512 feature (which includes b3sum) will remain broken on nightly.

EDIT: The c_avx512 feature has been replaced with the c feature in version 0.2.0, but the situation is the same otherwise.

@oconnor663 oconnor663 changed the title add #![feature(stdsimd)] to the crate attributes to enable use of unstable library feature 'stdsimd' Feb 12, 2020
oconnor663 added a commit that referenced this issue Feb 12, 2020
Version 0.1.5 was a backport release to mitigate
#57. This is a no-op merge
to make sure that the 0.1.5 branch shows up in `git log master`.
@oconnor663 oconnor663 pinned this issue Feb 28, 2020
@zaynetro
Copy link

zaynetro commented Mar 2, 2020

Can confirm that stable compiler can compile b3sum.

$ rustc --version
rustc 1.41.1 (f3e1a954d 2020-02-24)

oconnor663 added a commit to oconnor663/blake3-py that referenced this issue Mar 4, 2020
This allows us to enable the underlying "c" feature, which is failing to
build on current nightlies. See related issues:

BLAKE3-team/BLAKE3#56
BLAKE3-team/BLAKE3#57
rust-lang/rust#68905
@sneves sneves unpinned this issue Mar 22, 2020
@oconnor663
Copy link
Member

This is fixed as of rustc 1.44.0-nightly (38114ff16 2020-03-21) and rustc 1.43.0-beta.596 (1eaaee956 2020-03-22).

@OfekShochat
Copy link

I get this problem with the fully updated nightly stable and beta now (1.54.0-nightly (5dc8789e3 2021-05-21), rustc 1.53.0-beta.2 (4bac69dd2 2021-05-07), rustc 1.51.0 (2fd73fabe 2021-03-23))

@oconnor663
Copy link
Member

@OfekShochat are you saying that b3sum fails to build for you on all three toolchains? With an error message about stdsimd? I need you to give a lot more detail about what platform you're on and what commands you're running to have any chance of understanding the problem. Could you please file a new issue, with as much detail as possible?

@jianshu93
Copy link

I still have this error on 1.57. it is really strange. Any idea how to fix?

Jianshu

@ChaseLewis
Copy link

Yeah i'm getting this with avx instructions on nightly like _mm_maskz_div_ps in 1.69.0 - nightly

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

No branches or pull requests

6 participants