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

[avx512] General AVX-512 tracking issue #77

Closed
Lokathor opened this issue Jun 8, 2020 · 4 comments
Closed

[avx512] General AVX-512 tracking issue #77

Lokathor opened this issue Jun 8, 2020 · 4 comments

Comments

@Lokathor
Copy link
Owner

Lokathor commented Jun 8, 2020

There's a few problems with adding AVX-512 support:

  • I don't have a device to develop on that even supports AVX-512 (for testing).
  • Within Rust, it's all Nightly-only.

So (for now) we're blocked on adding avx512, but it'd be nice to have "some day".

This wouldn't be a 1.0 blocker, if we got to a state where we were otherwise 1.0 ready.

@Lokathor Lokathor added this to the post-1.0 milestone Jun 16, 2020
@Wunkolo
Copy link

Wunkolo commented Jun 25, 2020

The Intel software development emulator will allow you to at least verify a proper AVX-512 implementation, though debugging may be difficult.

@Lokathor Lokathor removed this from the post-1.0 milestone May 30, 2021
@Lokathor
Copy link
Owner Author

I'm gonna close this since it's been a year and avx-512 is not even fully on Nightly. we can always revisit later

@polarathene
Copy link

With the recent AMD Zen 4 release introducing AVX-512 support too, has much changed since the issue was closed?

So I gather not much has changed, other than hardware availability improving, the support may continue to depend on nightly for a while?


For a device to test on, it might be possible to rent a VPS instance hourly as needed? I think some providers like Amazon also offer a free tier for a year to new sign-ups, which might make that viable? (You can find info on instance types here, eg M6i has AVX-512)

@Lokathor
Copy link
Owner Author

packed_simd_2 exists only so that required bugfixes can be added. Specifically, the person that had publishing rights to packed_simd had left rust development for a while, so we had to fork it and release it under packed_simd_2. Other than that it's not developing as far as I know.

portable-simd is what's in active development, but that intentionally is not attempting to offer specific individual instrinsics.

If any place is going to allow specific individual intrinsics, that would be stdarch I think.

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

No branches or pull requests

3 participants