-
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
Basic block predecessors in mir textual representation #90868
Conversation
r? @nagisa (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
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.
I think this change is fine, but ideally the comment with predecessors would come after the line that has block name, rather than before the block itself. This is how our remark comments show up in other places.
That is, I think the output should look more like
bb1: { // preds: [bb0]
☔ The latest upstream changes (presumably #91469) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from triage: |
Ping from triage: |
Similiar to how LLVM-IR includes `; preds = %bb1` in its textual output. Makes it a bit nicer to read mir dumps.
25e1011
to
8d48733
Compare
Sorry for the slow response. |
@bors r+ Thanks! |
📌 Commit 8d48733 has been approved by |
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #94174) made this pull request unmergeable. Please resolve the merge conflicts. |
@simonvandel this needs a rebase. |
Ping from triage: I'm closing this due to inactivity, Please reopen when you are ready to continue with this. Thanks for your contribution. @rustbot label: +S-inactive |
Similiar to how LLVM-IR includes
; preds = %bb1
in its textual output.Makes it a bit nicer to read mir dumps.