-
-
Notifications
You must be signed in to change notification settings - Fork 842
ICU-23253 Add Link Time Optimization to release flags #3765
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
|
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
|
FYI the following warnings appeared when I used Linux/gcc. Most of the warnings appeared at link time. |
|
@markusicu Do you want to approve this as is, or do you want me to address these new gcc warnings in this pull request too? After a quick look, all of the warnings seem fixable. |
|
Some of the warnings seemed legitimate. I fixed what I could easily fix. The rest require deeper analysis. Here's what's left. |
|
Regarding one of the warnings, the warning on |
|
Is the warnings discussion actually for the other PR about static initialization? |
|
The warnings commentary is due to this option being used. These are new warnings from g++ that I observed. It's doing a deeper analysis of the code that cross function boundaries. |
63e839c to
bd9b80b
Compare
|
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
The runConfigureICU script should add Link Time Optimization (-flto) to the release flags for ongoing testing on macOS. It can provide substantial performance improvements.
Checklist