-
Notifications
You must be signed in to change notification settings - Fork 12.1k
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
show linker output even if the linker succeeds #119286
Conversation
|
060a457
to
a34d7ae
Compare
This comment has been minimized.
This comment has been minimized.
64cb47a
to
ab6fb2b
Compare
also i know we settled on not showing stdout by default but it's useful for debugging search paths - maybe we should show it after all? it seems silly to have to pass both |
This comment has been minimized.
This comment has been minimized.
ab6fb2b
to
ba4425d
Compare
@@ -714,7 +714,7 @@ fn test_unstable_options_tracking_hash() { | |||
untracked!(unpretty, Some("expanded".to_string())); | |||
untracked!(unstable_options, true); | |||
untracked!(validate_mir, true); | |||
untracked!(verbose, true); | |||
untracked!(verbose_internals, true); |
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.
Don't diagnostics influenced by this flag end up in the incr cache? It should actually be tracked I think.
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.
hmm, do we cache diagnostic output? even on errors? that seems very strange to me.
i don't mind changing it to tracked, i'm just confused why it's necessary.
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.
On errors we don't finalize the incr comp cache, but non-fatal diagnostics are cached afaik. Otherwise we would have to replay the query in question, which we may not be able to do if the query key is not reconstructible from the dep node fingerprint.
ba4425d
to
43edbe0
Compare
☔ The latest upstream changes (presumably #119662) made this pull request unmergeable. Please resolve the merge conflicts. |
This comment has been minimized.
This comment has been minimized.
hmm. that test has the following comment: rust/tests/incremental/commandline-args.rs Lines 13 to 20 in e9a009f
i suppose those lines are all invalid now, it should be testing that the CGU is not reused? i'm not sure why it's testing --verbose specifically, maybe it's enough to test any untracked CLI arg. i'll change it to --diagnostic-width.
i'm realizing your comments are all about #119129. i feel slightly uncomfortable making unrelated changes in this PR ... how do you feel about splitting them into a separate PR so i can assign michaelwoerister? |
Sure |
I prefer not doing this. It is helpful whenever a linkage issue is opened to not have to ask to rerun with |
☔ The latest upstream changes (presumably #119972) made this pull request unmergeable. Please resolve the merge conflicts. |
the linker arguments can be *very* long, especially for crates with many dependencies. often they are not useful. omit them unless the user specifically requests them.
this avoids warnings from macOS ld
@bors r+ |
@bors rollup=iffy |
show linker output even if the linker succeeds - show stderr by default - show stdout if `--verbose` is passed - remove both from RUSTC_LOG - hide the linker cli args unless `--verbose` is passed fixes rust-lang#83436. fixes rust-lang#38206. fixes rust-lang#109979. helps with rust-lang#46998. cc https://rust-lang.zulipchat.com/#narrow/stream/233931-t-compiler.2Fmajor-changes/topic/uplift.20some.20-Zverbose.20calls.20and.20rename.20to.E2.80.A6.20compiler-team.23706/near/408986134 this is based on rust-lang#119129 for convenience so i didn't have to duplicate the changes around saving `--verbose` in rust-lang@cb6d033#diff-7a49efa20548d6806dbe1c66dd4dc445fda18fcbbf1709520cadecc4841aae12 r? `@bjorn3`
💔 Test failed - checks-actions |
lol what on earth
the first one looks like #112368, probably? that's related to an old linker version, i'm not sure what version we're using in CI. anyway i'm probably not going to put much more time into this pr |
Because getting a newer one is not a trivial task ;)
Oh, that's strange. In the past, Rust used |
@bors r- Probably someone clicked the synchronize button. |
i am not planning to work on this more, someone else can pick it up if they care |
--verbose
is passed--verbose
is passedfixes #83436. fixes #38206. fixes #109979. helps with #46998. cc https://rust-lang.zulipchat.com/#narrow/stream/233931-t-compiler.2Fmajor-changes/topic/uplift.20some.20-Zverbose.20calls.20and.20rename.20to.E2.80.A6.20compiler-team.23706/near/408986134
this is based on #119129 for convenience so i didn't have to duplicate the changes around saving
--verbose
in cb6d033#diff-7a49efa20548d6806dbe1c66dd4dc445fda18fcbbf1709520cadecc4841aae12r? @bjorn3