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

Why are you using GAS? #41

Open
QRCS-CORP opened this issue Jun 24, 2021 · 2 comments
Open

Why are you using GAS? #41

QRCS-CORP opened this issue Jun 24, 2021 · 2 comments

Comments

@QRCS-CORP
Copy link

Congrats on making it to round 3!

Many modern compilers no longer support this old AT&T style dialect, but all the major compilers including GCC and Clang, support the more modern Intel syntax used in MASM. Windows servers are a huge piece of the market, and the go-to tool for Windows programming is Visual Studio, which does not support this older syntax. As a result, a number of downstream prototyping libraries, including my own, have not implemented the AVX versions of these codes. Please consider changing the ASM to the Intel syntax in Dilithium and Kyber, it would save a lot of people a lot of work.

Cheers,
John

@mberry
Copy link

mberry commented Jan 9, 2023

We have a NASM version of the assembly code:

https://github.com/Argyle-Software/kyber/tree/master/src/avx2/nasm

@YuriMyakotin
Copy link

Intrinsic version instead of gas/nasm - would be good also, for using same code both in windows and *nix.

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