You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a lot of testing, I have determined that it is not a memory alignment or cpu cache problem. And the results of repeated tests are the same, is this not strange?
#39060
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.
When you are down to a few nanoseconds per operation, it could be the exact alignment of the code in memory, it could be the CPU's memory caching algorithm, it could be the branch predictor, it could be the phase of the moon. Microbenchmarking is hard.
We don't use the issue tracker to discuss issues like this. Use a forum instead. If you identify a problem in the compiler or assembler or linker, then by all means open an issue with details. But the odds are that this is effectively chance, and not something that can be fixed.
When you are down to a few nanoseconds per operation, it could be the exact alignment of the code in memory, it could be the CPU's memory caching algorithm, it could be the branch predictor, it could be the phase of the moon. Microbenchmarking is hard.
We don't use the issue tracker to discuss issues like this. Use a forum instead. If you identify a problem in the compiler or assembler or linker, then by all means open an issue with details. But the odds are that this is effectively chance, and not something that can be fixed.
Originally posted by @ianlancetaylor in #39059 (comment)
The text was updated successfully, but these errors were encountered: