-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
-Zlto strips pub extern'ed functions provided by extern'ed crates #14500
Comments
This seems like desired behavior? LTO only makes sense on executables, who shouldn't be exporting any symbols besides the entry point anyway. |
LTO makes sense for |
Hm, that's true. I guess ... we need a |
Although I wonder what the use-case is for declaring a function |
Well it's not from your crate and it's not actually public, so it gets On Thu, May 29, 2014 at 10:06 AM, Yehuda Katz [email protected]:
|
Sure. I guess I'm proposing a change to the |
All rust functions are internal implementation details with respect to the ABI exposed by crates, but extern fns are public components of the ABI and shouldn't be stripped. This commit serializes reachable extern fns to metadata, so when LTO is performed all of their symbols are not stripped. Closes rust-lang#14500
All rust functions are internal implementation details with respect to the ABI exposed by crates, but extern fns are public components of the ABI and shouldn't be stripped. This commit serializes reachable extern fns to metadata, so when LTO is performed all of their symbols are not stripped. Closes rust-lang#14500
No description provided.
The text was updated successfully, but these errors were encountered: