Skip to content
This repository has been archived by the owner on May 5, 2021. It is now read-only.

internal/ge25519: Use the unsafe moveConditionalBytes on more targets #19

Merged
merged 1 commit into from
Feb 6, 2020

Conversation

Yawning
Copy link
Contributor

@Yawning Yawning commented Feb 6, 2020

Instead of only using the subtle.ConstantTimeCopy replacement on
architectures that are indifferent to alignment, check to see if
the arguments are well-aligned, and use the faster path if possible.

This is primarily for the benefit of ARM systems, where this will
improve the key generation and signing performance by up to 30%.

Part of #18.

Instead of only using the subtle.ConstantTimeCopy replacement on
architectures that are indifferent to alignment, check to see if
the arguments are well-aligned, and use the faster path if possible.

This is primarily for the benefit of ARM systems, where this will
improve the key generation and signing performance by up to 30%.
@Yawning Yawning merged commit 2893bee into master Feb 6, 2020
@Yawning Yawning deleted the yawning/feature/faster-move-cond branch February 6, 2020 13:42
@Yawning
Copy link
Contributor Author

Yawning commented Feb 6, 2020

@target111, @iwasaki-kenta This may be of interest to one or both of you, as it dramatically improves key generation and signing performance on ARM targets.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants