Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crypto.bcrypt: fix massive speed regression when using stage2 #13518

Merged
merged 1 commit into from
Nov 14, 2022

Conversation

jedisct1
Copy link
Contributor

state: State -> state: *const State

Suggested by @nektro

Fixes #13510

state: State -> state: *const State
Suggested by @nektro

Fixes ziglang#13510
@Daimanta
Copy link

Please also change the feistelF function state param type to "* const State". I notice that with Zig 0.10.0, changing this parameter type really helps( irrespective of the improvements on the copy elission fixes).

@jedisct1
Copy link
Contributor Author

@Daimanta that function doesn't exist any more since 9679353

@jedisct1
Copy link
Contributor Author

Merging, as performance is critical for this function, but this is a band-aid until the root cause is fixed.

@jedisct1 jedisct1 merged commit 7eed028 into ziglang:master Nov 14, 2022
@jedisct1 jedisct1 deleted the bcrypt-regression-fix branch November 14, 2022 15:37
andrewrk pushed a commit that referenced this pull request Jan 9, 2023
state: State -> state: *const State
Suggested by @nektro

Fixes #13510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bcrypt large speed regression
2 participants