-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[do not merge] Proof of concept implementation of forward compatible v0 symbols (MCP 737) #125487
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[do not merge] Proof of concept implementation of forward compatible v0 symbols (MCP 737) This PR changes v0 symbol names to enable graceful degradation for demanglers that don't support newer language features yet (as described in [MCP 737](rust-lang/compiler-team#737)). The corresponding changes in rustc-demangle are at /~https://github.com/michaelwoerister/rustc-demangle/tree/skip_unknown. This proof-of-concept implementation is meant to help evaluating if MCP 737 is viable. r? `@ghost`
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
The above perf run includes the changes due to making v0 the default. The performance comparison that is actually relevant uses v0=default as baseline: |
I'm somewhat skeptical about the results though, since I'll investigate with cachegrind diff when I get a chance. |
We discussed this in the compiler team design meeting on Jun 14, and decided to not pursue this any further for now. |
This PR changes v0 symbol names to enable graceful degradation for demanglers that don't support newer language features yet (as described in MCP 737).
The corresponding changes in rustc-demangle are at /~https://github.com/michaelwoerister/rustc-demangle/tree/skip_unknown.
This proof-of-concept implementation is meant to help evaluating if MCP 737 is viable.
r? @ghost