Specialized algorithm for different ranges of values.#11
Merged
llogiq merged 1 commit intollogiq:masterfrom Dec 3, 2016
Merged
Specialized algorithm for different ranges of values.#11llogiq merged 1 commit intollogiq:masterfrom
llogiq merged 1 commit intollogiq:masterfrom
Conversation
Owner
|
The errors seem to be in the benchmark code. Perhaps an incomplete commit? |
Owner
|
We could include a build script to determine the optimum thresholds for the given machine (using binary search). Or at least a secondary program. |
Collaborator
Author
|
It was just a last-minute renaming I forgot to test. Murphy's law and all. |
Owner
|
Benchmarks: |
Collaborator
Author
|
Thanks for the timings. I see no regressions, and some nice wins. |
Owner
|
Yes, I'm also happy about the wins. |
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.
For a one-liner this code sure is getting long.
I worked out the performance issue I was having - LLVM was getting really confused by a by-value
sumtaking a[T; 4]. Changing that to a reference fixed things.I've tuned the specific constants for my machine. Verification that I haven't caused a regression would be helpful. When doing so you might notice there are a lot more benchmarks. This is getting unwieldy, but they've been very useful for me.
Fixes #10.