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

const simd_extract/insert are no longer usable in latest nightly (2020-01-02) #67847

Open
novacrazy opened this issue Jan 3, 2020 · 3 comments
Labels
A-const-eval Area: Constant evaluation (MIR interpretation) A-SIMD Area: SIMD (Single Instruction Multiple Data) B-unstable Blocker: Implemented in the nightly compiler and unstable. requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@novacrazy
Copy link

A few months ago #64738 introduced const simd_insert/simd_extract, which I then integrated into my application via a fork of packed_simd.

However, upon upgrading to the latest nightly (rustc 1.42.0-nightly (0a58f5864 2020-01-02)), it was suddenly non-const.

Furthermore, It seems the ability to make it const via rustc_const_unstable is not possible in user applications, making the const versions of this effectively rustc internal-only now, breaking my fork of packed_simd and my application.

@jonas-schievink jonas-schievink added A-const-eval Area: Constant evaluation (MIR interpretation) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 4, 2020
@mati865
Copy link
Contributor

mati865 commented Jan 4, 2020

cc @oli-obk ?

@oli-obk oli-obk added B-unstable Blocker: Implemented in the nightly compiler and unstable. requires-nightly This issue requires a nightly compiler in some way. and removed C-bug Category: This is a bug. labels Jan 4, 2020
@oli-obk
Copy link
Contributor

oli-obk commented Jan 4, 2020

As mentioned on #64738 you can use stability attributes to get this working again.

If this requires you to add too many annotations to your crate, you can create a crate that solely consists of the intrinsic declarations and exports them. Then your main crate doesn't need any annotations. I do not think there's anything on the compiler end that we will do to further support using very unstable internals of the standard library.

If you want to speed up the stabilization of this, @gnzlbg mentioned moving packed_simd into the libstd. Though I do not know what the status, progress or plans for that are

@workingjubilee
Copy link
Member

workingjubilee commented Sep 10, 2020

@rustbot modify labels: +A-simd
Current status of portable SIMD: Coalescing project group.
EDIT: whoops, wrong link. rust-lang/rfcs#2977

@rustbot rustbot added the A-SIMD Area: SIMD (Single Instruction Multiple Data) label Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-const-eval Area: Constant evaluation (MIR interpretation) A-SIMD Area: SIMD (Single Instruction Multiple Data) B-unstable Blocker: Implemented in the nightly compiler and unstable. requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants