-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollback part of pr 104137 that broke wasm linker overriding #108996
Rollback part of pr 104137 that broke wasm linker overriding #108996
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
These commits modify compiler targets. |
(note: I definitely am not wedded to this particular approach. In the associated zulip thread, I described a number of alternatives that I would be equally happy with. I'm looking to @petrochenkov and to the WASM stakeholders like @bjorn3, @alexcrichton , and @sunfishcode to guide us here.) |
(also, I am nearly certain that this unit test is not constructed properly. Or at least, on my host system, I know that the included unit test did not suffice to expose the problem, because of the |
I at least personally don't know how the self-containedness support in rustc relates to wasm, or in other words I don't think I know enough about the way the fix is applied here to comment on it. If this issue is only showing up when users switch the wasm linker to |
wow, I ... was so sure I did a local build here... (but the nature of that failure shows that I clearly didn't) |
ceb41ed
to
8bccd4e
Compare
These commits modify compiler targets. |
Replicates problem on my machine. To exercise the test, I had to use a config.toml that has: ``` [build] target = ["x86_64-unknown-linux-gnu","wasm32-unknown-unknown"] nodejs = "node" [rust] lld = true ```
8bccd4e
to
568b722
Compare
@bors r=petrochenkov rollup=iffy |
⌛ Testing commit 568b722 with merge c9807ee2ed61b1b8db5c1b69e6293253ecd1e9dc... |
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 568b722 with merge c18255d641f1403e74209d0dc837d4a9482028cc... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors r- (was inadvertently re-queued by a homu sync) |
uhhhh, do we not have access to clang on the CI? Or is this something where I need to modify a docker image or something to make the CI install clang as part of its setup here? |
I'm going to rip out the regression test (i.e. revise this PR so that it just has the rollback), and then file a separate issue about making a regression test for this |
removing regression test
removing regression test
@bors r=petrochenkov rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (17c1167): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. |
This is a quick fix to address #108910