-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[DO NOT MERGE][stdlib] Make assert(), _debugPreconditions() noops #35065
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
This is just an experiment to verify a potential optimization problem.
@swift-ci benchmark |
Performance: -O
Code size: -OPerformance: -Osize
Code size: -Osize
Performance: -Onone(Hidden because these are irrelevant)
Code size: -swiftlibs
How 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
|
Yep, this is not great. |
This comment has been minimized.
This comment has been minimized.
1 similar comment
@swift-ci benchmark |
Performance: -O
Code size: -OPerformance: -Osize
Code size: -Osize
Performance: -OnoneDebug performance isn't relevant; click here to see if you are curious
Code size: -swiftlibs
How 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
|
Every symptom here can be explained by one of these three cases:
|
This is just an experiment to verify a potential optimization problem.
(If this patch affects performance benchmarks in any way, then my hare-brained theory in #34961 (comment) is probably correct.)