-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Tracking Issue for -C export-executable-symbols
#84161
Comments
RFC-2841: add codegen flag export symbols from executable Closes rust-lang#84161 r? ``@nikomatsakis`` ``@Mark-Simulacrum``
RFC-2841: add codegen flag export symbols from executable Closes rust-lang#84161 r? ```@nikomatsakis``` ```@Mark-Simulacrum```
RFC-2841: add codegen flag export symbols from executable Closes rust-lang#84161 r? ``@nikomatsakis`` ``@Mark-Simulacrum``
RFC-2841: add codegen flag export symbols from executable Closes rust-lang#84161 r? `@nikomatsakis` `@Mark-Simulacrum`
This should not have been closed. |
The |
What’s stopping this from moving forward? Can I do something to help? |
Triage: Incidentally I just created a new label for this feature before I saw your comment on this issue. A good first step would be to go through the issues in this query and triage them appropriately: https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Aopen+Zexport-executable-symbols Maybe #34131 can be closed as "covered by the tracking issue", for example. |
Thanks! I think I’ll look into #101610 first, because it affects the promised semantics of the flag. |
What's the current progress on this feature? It's been 3 years. |
It's still buggy afaik and I don't think anyone has been working to work on fixing the bugs it has. |
@g-mero It’s somewhere on my backlog, but I can’t promise getting to it soon. I think the problem in #101610 is either with version script or with linker arguments, so if you’d like to help, you can try to check whether symbols get to the version script. If they do, I think we should either use |
This is a tracking issue for the RFC "2841" (rust-lang/rfcs#2841).
The feature gate for the issue is
#![feature(export_executable_symbols)]
.About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Unresolved Questions
Implementation history
The text was updated successfully, but these errors were encountered: