p256: initial 32-bit scalar backend #636
Merged
Conversation
This file contains 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
tarcieri
force-pushed
the
p256/initial-32-bit-scalar-backend
branch
from
6560067
to
30105c7
Compare
This applies a similar treatment from #635 to the scalar backend, clearing the way to implement a proper 32-bit backend for both the base and scalar fields.
tarcieri
force-pushed
the
p256/initial-32-bit-scalar-backend
branch
from
30105c7
to
a5f4272
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This applies a similar treatment from #635 to the scalar backend, clearing the way to implement a proper 32-bit backend for both the base and scalar fields.