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

feat: implement 128bit fft #3

Closed
wants to merge 1 commit into from
Closed

feat: implement 128bit fft #3

wants to merge 1 commit into from

Conversation

sarah-quinones
Copy link

No description provided.

Copy link
Member

@IceTDrinker IceTDrinker left a 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 ?

Cargo.toml Outdated Show resolved Hide resolved
src/lib.rs Show resolved Hide resolved
src/fft128/mod.rs Show resolved Hide resolved
src/fft128/mod.rs Show resolved Hide resolved
src/fft128/f128_impl.rs Show resolved Hide resolved
src/fft128/mod.rs Outdated Show resolved Hide resolved
Cargo.toml Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
}

#[inline(always)]
pub(crate) fn _mm256_quick_two_sum(simd: Avx, a: __m256d, b: __m256d) -> (__m256d, __m256d) {
Copy link
Member

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(
Copy link
Member

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 {
Copy link
Member

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also let's keep track the CI task to have tests for all the intrisics combinations (cc @soonum) and fix a toolchain version to avoid random lint breakage #6

@sarah-quinones
Copy link
Author

closed as superseded by #11

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

Successfully merging this pull request may close these issues.

3 participants