-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Propagate SIMD flags into sub-makes #5598
Comments
The reason for @CFLAGS@ not being "it" is probably because of historical confusion about john.o special treatment, for CPU fallback. Current top Makefile.in
We could rework that and edit
For #5593 I think we should amend |
Yes, that's OK with me. Thank you! |
This commit only applies to autoconf builds. Closes openwall#5598
This commit only applies to autoconf builds. Closes openwall#5598
This commit only applies to autoconf builds. Closes openwall#5598
This commit only applies to autoconf builds. Closes openwall#5598
As noticed in #5593, the
CFLAGS
we use to build the.a
libraries in subdirectories do not include the main build's SIMD flags. This is non-optimal at least in that it doesn't enable usage of the same CPU features, and potentially worse - it may cause slow transitions between VEX-encoded and legacy SSE code.The text was updated successfully, but these errors were encountered: