-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[Fuchsia][cmake] Allow using FatLTO when building runtimes #112277
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
Merged
ilovepi
merged 16 commits into
main
from
users/ilovepi/spr/libcxxcmake-allow-using-fatlto-in-libc-builds
Dec 9, 2024
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
1dafa52
[𝘀𝗽𝗿] initial version
ilovepi 350d75e
Rebase on main
ilovepi 38851d2
Remove newline from diff
ilovepi 3990524
Rebase on main
ilovepi 535f2f2
Avoid unecessary changes to libc++ cmake
ilovepi 2ad6038
[𝘀𝗽𝗿] changes introduced through rebase
ilovepi 49ce824
rebase and enable FatLTO for Fuchsia targets
ilovepi 9511215
[𝘀𝗽𝗿] changes introduced through rebase
ilovepi 1b3c34f
Rebase
ilovepi 86c376e
[𝘀𝗽𝗿] changes introduced through rebase
ilovepi 13973d0
Move --as-needed into the correct patch
ilovepi 4b7b3f9
[𝘀𝗽𝗿] changes introduced through rebase
ilovepi b5551cc
update base revision
ilovepi e0d6cbf
[𝘀𝗽𝗿] changes introduced through rebase
ilovepi 52c567e
Rebase on main
ilovepi 8118e04
Rebase
ilovepi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I don't understand why that diff is required since you're setting it properly in your cache files.
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.
Because Fuchsia Targets aren't UNIX. Without this change
-ffat-lto-objects
won't be passed toclang
through CMake. The additional logic is basically to restrict the flag to ELF targets, and it missed Fuchsia when we added it, since we weren't building our runtimes with FatLTO initially, just the toolchain + tests.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.
Sorry, I think I initially read
if (LLVM_ENABLE_FATLTO OR ((UNIX AND NOT APPLE) OR FUCHSIA))
.