Fix typo: "unkown" -> "unknown" #1
Merged
Conversation
This file contains hidden or 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
Member
|
\o/ Thanks! |
d-e-s-o
added a commit
to d-e-s-o/gimli
that referenced
this pull request
Sep 10, 2025
As it turns out, the Rust compiler uses variable length LEB128 encoded integers internally. It so happens that they spent a fair amount of effort micro-optimizing the decoding functionality [0] [1], as it's in the hot path. With this change we replace our decoding routines with these optimized ones. To make that happen more easily (and to gain some base line speed up), also remove the "shift" return from the respective methods. As a result of these changes, we see a respectable speed up: System gimli-rs#1: Before: test bench_reading_leb128_unsigned ... bench: 235.83 ns/iter (+/- 32.53) After: test bench_reading_leb128_unsigned ... bench: 157.38 ns/iter (+/- 17.09) System gimli-rs#2: Before: test bench_reading_leb128_unsigned ... bench: 183.70 ns/iter (+/- 2.72) After: test bench_reading_leb128_unsigned ... bench: 109.08 ns/iter (+/- 3.11) [0] rust-lang/rust#69050 [1] rust-lang/rust#69157 Signed-off-by: Daniel Müller <[email protected]>
d-e-s-o
added a commit
to d-e-s-o/gimli
that referenced
this pull request
Sep 10, 2025
As it turns out, the Rust compiler uses variable length LEB128 encoded integers internally. It so happens that they spent a fair amount of effort micro-optimizing the decoding functionality [0] [1], as it's in the hot path. With this change we replace our decoding routines with these optimized ones. To make that happen more easily (and to gain some base line speed up), also remove the "shift" return from the respective methods. As a result of these changes, we see a respectable speed up: System gimli-rs#1: Before: test bench_reading_leb128_unsigned ... bench: 235.83 ns/iter (+/- 32.53) After: test bench_reading_leb128_unsigned ... bench: 157.38 ns/iter (+/- 17.09) System gimli-rs#2: Before: test bench_reading_leb128_unsigned ... bench: 183.70 ns/iter (+/- 2.72) After: test bench_reading_leb128_unsigned ... bench: 103.83 ns/iter (+/- 3.28) [0] rust-lang/rust#69050 [1] rust-lang/rust#69157 Signed-off-by: Daniel Müller <[email protected]>
d-e-s-o
added a commit
to d-e-s-o/gimli
that referenced
this pull request
Sep 10, 2025
As it turns out, the Rust compiler uses variable length LEB128 encoded integers internally. It so happens that they spent a fair amount of effort micro-optimizing the decoding functionality [0] [1], as it's in the hot path. With this change we replace our decoding routines with these optimized ones. As a result of these changes, we see a respectable speed up: System gimli-rs#1: Before: test bench_reading_leb128_unsigned ... bench: 235.83 ns/iter (+/- 32.53) After: test bench_reading_leb128_unsigned ... bench: 157.38 ns/iter (+/- 17.09) System gimli-rs#2: Before: test bench_reading_leb128_unsigned ... bench: 183.70 ns/iter (+/- 2.72) After: test bench_reading_leb128_unsigned ... bench: 103.83 ns/iter (+/- 3.28) [0] rust-lang/rust#69050 [1] rust-lang/rust#69157 Signed-off-by: Daniel Müller <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.