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

Tracking issue for RFC 2574, "SIMD vectors in FFI" #63068

Open
4 tasks
Centril opened this issue Jul 28, 2019 · 0 comments
Open
4 tasks

Tracking issue for RFC 2574, "SIMD vectors in FFI" #63068

Centril opened this issue Jul 28, 2019 · 0 comments
Labels
A-FFI Area: Foreign function interface (FFI) A-SIMD Area: SIMD (Single Instruction Multiple Data) B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-simd_ffi `#![feature(simd_ffi)]` requires-nightly This issue requires a nightly compiler in some way. S-tracking-unimplemented Status: The feature has not been implemented. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.

Comments

@Centril
Copy link
Contributor

Centril commented Jul 28, 2019

This is a tracking issue for the RFC "SIMD vectors in FFI" (rust-lang/rfcs#2574).
The feature gate is #![feature(simd_ffi)].

Steps:

Unresolved questions:

  • Should it be possible to use, e.g., __m128 on C FFI when the avx feature is enabled? Does that change the calling convention and make doing so unsafe ? We could extend this RFC to also require that to use certain types certain features must be disabled.
@Centril Centril added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. A-FFI Area: Foreign function interface (FFI) A-SIMD Area: SIMD (Single Instruction Multiple Data) F-simd_ffi `#![feature(simd_ffi)]` labels Jul 28, 2019
@Centril Centril added the requires-nightly This issue requires a nightly compiler in some way. label Jul 28, 2019
@joshtriplett joshtriplett added S-tracking-design-concerns Status: There are blocking ❌ design concerns. S-tracking-impl-incomplete Status: The implementation is incomplete. and removed S-tracking-design-concerns Status: There are blocking ❌ design concerns. labels Jun 22, 2022
@wesleywiser wesleywiser added S-tracking-unimplemented Status: The feature has not been implemented. and removed S-tracking-impl-incomplete Status: The implementation is incomplete. labels Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-FFI Area: Foreign function interface (FFI) A-SIMD Area: SIMD (Single Instruction Multiple Data) B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-simd_ffi `#![feature(simd_ffi)]` requires-nightly This issue requires a nightly compiler in some way. S-tracking-unimplemented Status: The feature has not been implemented. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants