-
Notifications
You must be signed in to change notification settings - Fork 67
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
Update libsodium
#206
Update libsodium
#206
Conversation
@jedisct1 Thanks so much for dropping by, it's much appreciated! 🙏 |
In the original build system, only the files that actually require AVX2 are compiled with the But it looks like this CMakefile is applying the same flags, which includes non-portable flags, to all the files. So the result is indeed non portable. Since the introduction of the Zig build system, files requiring specific extensions also enable them individually, using clang/gcc extensions. That should be fine in your case. |
@jedisct1 glad to see you there Jedi Sector One, we used to code on HP48SX a while ago, thanks for the fix very appreciated! |
84d5378
to
95b153c
Compare
@jedisct1 So far, so good; I've updated Lines 429 to 438 in 95b153c
|
Wow, that was a looooong time ago! But I miss these good old days! |
How does it fail on Windows? |
Use the |
Without
|
Maybe the compiler toolchain is too old. You can undefine |
This applies to both RDRAND, AVX, AVX2, and AVX512F on Windows though and at least AVX2 and AVX512F are automatically enabled by |
That's for Visual Studio. |
Clang defines |
You may remember Kewl/FFT, I'm a heavy user of libsodium, keep on the good work! |
FUCK FRANCE TELECOM! |
Ah ok. But that just indicates that these headers are present, it doesn't enable compiler features. |
I'm not sure that LLVM agrees as it refuses to compile the code on Windows without those features being explicitly enabled using the corresponding |
It actually looks like an already known bug in Clang: llvm/llvm-project#53520 |
@jedisct1 Everything seems to be compiling correctly now, thanks so much for the assistance! The only remaining issue, which may very well be a non-issue, is some warnings emitted when compiling for Windows:
|
Superseded by #207. |
No description provided.