-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Bridged Strings should have some different/additional overrides for performance (<rdar://problem/26236614>) #20383
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 please benchmark |
|
@swift-ci please test |
|
@Catfish-Man Do you think the comments in the PR that you have put here should be comments in source instead? (Have no opinion, just seems like useful information) |
|
@gottesmm probably so :) good point |
Build comment file:Performance: -O
Performance: -Osize
Performance: -Onone
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 regressions before you merge the PR. Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein). Hardware Overview |
|
Build failed |
|
Looks like the test failure is just the ABI checker complaining, which is expected. We'll see on Linux, I haven't tested it yet. |
|
@swift-ci please benchmark |
1 similar comment
|
@swift-ci please benchmark |
Build comment file:Performance: -O
Performance: -Osize
Performance: -Onone
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 regressions before you merge the PR. Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein). Hardware Overview |
milseman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@swift-ci please benchmark |
2 similar comments
|
@swift-ci please benchmark |
|
@swift-ci please benchmark |
|
Right, the creation and use of the classes should always be behind a resilient function. Good catch |
Build comment file:Performance: -O
Performance: -Osize
Performance: -Onone
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 |
|
Heeeey it worked! I was really expecting that to be a huge regression. Awesome. Ok, gonna get this ready to go. Also, sadly, I have to delete the -UTF8String optimization. I realized that Cocoa jumps through hoops to return non-NULL there, so we need to fall back to the superclass, not return nil, and I haven't figured out how to do that yet. |
|
|
@swift-ci please test and merge |
1 similar comment
|
@swift-ci please test and merge |
|
Sigh… now to figure out why that isn't failing locally |
|
That's a 32-bit build. Try with |
|
Ok yeah, 32 bit failure it is. Fixing this is going to be a lot more challenging sadly, so probably tomorrow. |
|
@swift-ci please test and merge |
5 similar comments
|
@swift-ci please test and merge |
|
@swift-ci please test and merge |
|
@swift-ci please test and merge |
|
@swift-ci please test and merge |
|
@swift-ci please test and merge |
|
Oh I forgot to pull on the machine I was building on, that's why my results don't match this. About that "going to sleep and doing this tomorrow"… |
|
If you want to split off the dropping of |
|
@swift-ci please test and merge |
1 similar comment
|
@swift-ci please test and merge |
This provides specialized overrides of more NSString methods, as well as moving dynamic dispatch boundaries around and sprinkling @_effects in to reduce refcounting overhead.
rdar://problem/26236614