-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add result checking to the ChaCha benchmark. #34042
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci test |
@swift-ci benchmark |
Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -Onone
Code size: -swiftlibsHow to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
12c1582
to
9d60139
Compare
The results are inexplicable because I only saw a small performance regression at -Onone when building locally. Nonetheless, I reduced the verification so it definitely won't take a significant portion of the run time at -Onone. |
@swift-ci benchmark |
@swift-ci smoke test |
Build failed before running benchmark. |
@swift-ci smoke test osx |
@swift-ci benchmark |
@swift-ci smoke test osx platform |
@swift-ci smoke test OS X platform |
1 similar comment
@swift-ci smoke test OS X platform |
@swift-ci benchmark |
This benchmark was being miscompiled for some time and we did not catch it. I only noticed because a correcteness fix caused a regression.
9d60139
to
eef1cf6
Compare
@swift-ci smoke test |
@swift-ci benchmark |
Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -OnoneCode size: -swiftlibsHow to read the dataThe tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.If you see any unexpected regressions, you should consider fixing the Noise: Sometimes the performance results (not code size!) contain false Hardware Overview
|
This benchmark was being miscompiled for some time and
we did not catch it. I only noticed because a correcteness
fix caused a regression.