Armory format: Pre-check for cracks within parallel section #5424
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 is a controversial change for a slow format like this, but OTOH I don't want my decision not to make this format salt-only (where we'd have to check for cracks in
crypt_all
) to have any obvious performance cost, whereas the number of comparisons percrypt_all
can be significant when there are many threads and SIMD vectors are wide (e.g.,192*8
in my recent test means 1536 comparisons, which when done sequentially out ofcrypt_all
can have a measurable cost).