Build arm64 with clang to enable AES hardware acceleration - #239
Merged
Merged
Conversation
… hardware acceleration
albertxing
force-pushed
the
axg/arm-aes
branch
from
September 28, 2026 23:17
be86262 to
0da19c2
Compare
albertxing
marked this pull request as ready for review
September 29, 2026 00:00
penberg
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current arm64 binary isn't compiled with AES hardware acceleration, because Multiple Ciphers doesn't include ARM AES hardware detection logic when using gcc. It does include that logic when compiling with clang, so switching to clang should enable hardware acceleration support.
I've tested this with a local cross-compiled build by inspecting the built binary's instructions.
Some alternatives are:
-march=armv8-a+crypto)