icp: Clean up AES-GCM AVX/AVX2 implementation selection #17061
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.
Cleans up the implementation selection proposed in #17058. Depends on #17058 being merged (this branch shares common ancestry)
Motivation and Context
#17058 added the AVX2 implementation of AES-GCM from BoringSSL but subtly broke the
cycle
implementation and would not compile on older assemblers which did not understand the AVX2 instructions.Description
Combine the
use_avx
/use_avx2
flags into an enum, allowing toggling of the different implementations that are available. Also, define different values ofCAN_USE_GCM_ASM
to indicate various levels of compiler support.How Has This Been Tested?
Types of changes
Checklist:
Signed-off-by
.