perf: improve add and sub performance by avoiding array::IntoIter
#316
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.
Motivation
array::IntoIter
is known to have worse performance thanslice::Iter
.Solution
Use
slice::Iter
instead ofarray::IntoIter
.This makes codegen of
U256::add
identical to LLVM nativeadd i256
, while slightly improves the one insub
.Rest of changes are
&(\w+)\.limbs
->$1.as_limbs()
.Ideally we would deny inclusion of new
array::IntoIter
calls unless explicitly allowed, but I don't know how to do this since clippy does not catch it withdisallowed-methods
.Test
u256_add
before/after diffu256_sub
before/after diffOptimal codegen
From Zig (Godbolt):
Actual codegen (after this PR)