Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
I find some trivial (and obviously irrelevant) changes to UTF8 validation code may cause big variances to benchmark result.
UTF8 validation functions are inlined and called directly in benchmark. The compiler may try to optimize them together with the benchmark loop.
Un-inline the benchmark-ed functions makes the result predictable and explainable.
Attachments
Issue Links
- links to