-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: implement 128bit fft #3
Conversation
89f2e8d
to
4e94b00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not have time to read everything, do you have some paper resource on the f128 format/approach you take ?
4e94b00
to
5efab2c
Compare
a96ee67
to
eccd8fa
Compare
} | ||
|
||
#[inline(always)] | ||
pub(crate) fn _mm256_quick_two_sum(simd: Avx, a: __m256d, b: __m256d) -> (__m256d, __m256d) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as was discussed, move away from the intel intrisics notations
|
||
impl Avx { | ||
#[inline(always)] | ||
pub fn _mm256_add_estimate_f128_f128( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as was discussed bench and compare the non estimate versions to be able to have the choice potentially for intrisics to select between estimate and more precise implementations
} | ||
|
||
#[cfg(test)] | ||
mod tests { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as discussed make sure all permutations are well tested
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closed as superseded by #11 |
No description provided.