Uh oh!
There was an error while loading. Please reload this page.
Fix debuginfo for pointers/references to unsized types - #93006
Conversation
rust-highfive
commented
Jan 17, 2022
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
f57d9de to
3da8b15Comparebors
commented
Jan 18, 2022
☔ The latest upstream changes (presumably #93009) made this pull request unmergeable. Please resolve the merge conflicts. |
3da8b15 to
756a70cComparemichaelwoerister
commented
Jan 19, 2022
This PR makes type names, that are part of a pointer type, fully qualified. For example, @bors try @rust-timer queue |
rust-timer
commented
Jan 19, 2022
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Jan 19, 2022
⌛ Trying commit 756a70c with merge 5d8768a3a4a4ad49d5b52f745a6a48bda4ff3bf0... |
bors
commented
Jan 19, 2022
☀️ Try build successful - checks-actions |
rust-timer
commented
Jan 19, 2022
Queued 5d8768a3a4a4ad49d5b52f745a6a48bda4ff3bf0 with parent 2f004d2, future comparison URL. |
rust-timer
commented
Jan 19, 2022
Finished benchmarking commit (5d8768a3a4a4ad49d5b52f745a6a48bda4ff3bf0): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. @bors rollup=never |
oli-obk
commented
Jan 19, 2022
This lgtm from a pure impl perspective, but I think someone who knows llvm should look over it r? rust-lang/wg-llvm |
oli-obk
commented
Jan 19, 2022
r? @rust-lang/wg-llvm |
michaelwoerister
commented
Jan 20, 2022
There doesn't seem to be an LLVM group in https://github.com/rust-lang/highfive/blob/master/highfive/configs/rust-lang/rust.json yet. r? @davidtwco, who knows debuginfo well (but feel free to re-assign if you don't want to review!) |
davidtwco
left a comment
There was a problem hiding this comment.
This looks good to me, two small nits but otherwise I think this is good.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
michaelwoerister
commented
Jan 21, 2022
Thanks for the reviews! Comments should be addressed now. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…ge doc comment so it is not interpreted as doc-test.
michaelwoerister
commented
Jan 27, 2022
Fix doc-comment so it's not interpreted as doctest. @bors r=davidtwco,oli-obk |
bors
commented
Jan 27, 2022
📌 Commit d33e317 has been approved by |
bors
commented
Jan 28, 2022
⌛ Testing commit d33e317 with merge bcca153730480e04fc3eae2166fc3b6c07942047... |
This comment has been minimized.
This comment has been minimized.
bors
commented
Jan 28, 2022
💔 Test failed - checks-actions |
…t mark fat pointer fields as artificial. LLDB does not seem to see fields if they are marked with DW_AT_artificial which breaks pretty printers that use these fields for decoding fat pointers.
rust-log-analyzer
commented
Jan 28, 2022
The job Click to see the possible cause of the failure (guessed by this bot) |
michaelwoerister
commented
Jan 28, 2022
@rust-lang/infra This is the second time in this PR that there's a core dump in compiletest after mir-opt testing: https://github.com/rust-lang/rust/runs/4978717078?check_suite_focus=true#step:26:3567 |
michaelwoerister
commented
Jan 28, 2022
I was able to reproduce the LLDB test failures on Linux. The last commit removes the @bors r=davidtwco,oli-obk |
bors
commented
Jan 28, 2022
📌 Commit c10f9e7 has been approved by |
bors
commented
Jan 28, 2022
bors
commented
Jan 28, 2022
☀️ Test successful - checks-actions |
rust-timer
commented
Jan 28, 2022
Finished benchmarking commit (427eba2): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
This PR makes the compiler emit fat pointer debuginfo in all cases. Before, we sometimes got thin-pointer debuginfo, making it impossible to fully interpret the pointed to memory in debuggers. The code is actually cleaner now, especially around generation of trait object pointer debuginfo.
Fixes#92718
Blocked on #92729.