SIMD runtime detection refactor#1
Merged
Merged
Conversation
byroot
reviewed
Jan 20, 2025
| state->buffer_initial_length = FBUFFER_INITIAL_LENGTH_DEFAULT; | ||
| // TODO ADD RUNTIME CHECKS HERE? | ||
|
|
||
| switch(find_simd_implementation()) { |
There was a problem hiding this comment.
I think you could do this in Init_generator, so it's only done once when the gem is required, rather than on every JSON.generate call.
afd7687 to
4347b8d
Compare
…of the SIMD implementations. Also added a few tests with more characters to ensure the SIMD implementations are tested.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Work In Progress
NOTE Still a lot of refactoring left to do.
Refactor to use runtime detection of the best algorithm.
Running under the Windows Subsystem for Linux on a Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz 2.59 GHz