-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-SIMDArea: SIMD (Single Instruction Multiple Data)Area: SIMD (Single Instruction Multiple Data)C-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.PG-portable-simdProject group: Portable SIMD (https://github.com/rust-lang/project-portable-simd)Project group: Portable SIMD (https://github.com/rust-lang/project-portable-simd)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Description
Feature gate: #![feature(portable_simd )]
mul_add presents under core_simd::Simd in rust-lang/portable-simd but is missing from std::simd::Simd
Below code (playground) does not compile
error[E0599]: no method named
mul_add
found for structSimd
in the current scope
--> src/main.rs:8:15
|
8 | let _ = a.mul_add(b, c);
| ^^^^^^^ method not found inSimd<f64, 8_usize>
For more information about this error, try rustc --explain E0599
.
error: could not compile playground
due to previous error
Public API
#![feature(portable_simd)]
use std::simd::f64x8;
// This works
// use core_simd::f64x8;
fn main() {
let a = f64x8::splat(0f64);
let b = f64x8::splat(0f64);
let c = f64x8::splat(0f64);
let _ = a.mul_add(b, c);
}
Steps / History
- Implementation: #...
- Final comment period (FCP)
- Stabilization PR
Unresolved Questions
- None yet.
Metadata
Metadata
Assignees
Labels
A-SIMDArea: SIMD (Single Instruction Multiple Data)Area: SIMD (Single Instruction Multiple Data)C-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.PG-portable-simdProject group: Portable SIMD (https://github.com/rust-lang/project-portable-simd)Project group: Portable SIMD (https://github.com/rust-lang/project-portable-simd)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.