-
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
Remove -Zinline-in-all-cgus and clean up tests/codegen-units/ #133929
base: master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9827f7e
to
b2b3983
Compare
This comment has been minimized.
This comment has been minimized.
b2b3983
to
5dd9c96
Compare
5dd9c96
to
3db04a3
Compare
This PR modifies cc @jieyouxu |
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 can only comment on the compiler/ changes and the run-make test removal, which LGTM. The actual codegen-units test diffs is probably better suited for @nnethercote to review after their vacation.
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.
Thanks for adding these docss 💙
``` | ||
MONO_ITEM <item> @@ <cgu name>[<linkage>] <other cgu name>[<linkage in other cgu>] | ||
``` | ||
DO NOT add tests to this suite that use `-Zprint-mono-items=eager`, that flag changes the way that MonoItem collection works in rather fundamental ways that are otherwise only used by `-Clink-dead-code`, and thus the MonoItems collected and their linkage under `-Zprint-mono-items=eager` does not correlate very well with normal compilation behavior. |
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.
Remark: almost makes me think this should be a separate codegen-units-partitioning
suite, which bans -Zprint-mono-items=eager
in compile-flags
, but anyway.
I just ran into this as well. The README you added is only for the @jieyouxu you unassigned yourself without picking a new reviewer. Was that deliberate? Someone should be in charge of the PR... r? compiler |
Just to avoid reviewer hot-potato: |
Could not assign reviewer from: |
They are all based on I want to work on the item-collection tests separately, because they are mostly but not all based on |
No, I thought nnethercote was already assigned... |
☔ The latest upstream changes (presumably #134299) made this pull request unmergeable. Please resolve the merge conflicts. |
3db04a3
to
512b3e3
Compare
# codegen-units/partitioning tests | ||
|
||
This test suite is designed to test that codegen unit partitioning works as intended. | ||
Note that it does not evaluate whether CGU partitioning is *good*, that is the job of the compiler benchmark suite. |
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.
This sentence has a comma splice which you don't need to fix but lots of people don't know about them so I thought I'd mention it for educational purposes :) (I'd change the comma to a period to fix it.)
``` | ||
MONO_ITEM <item> @@ <cgu name>[<linkage>] <other cgu name>[<linkage in other cgu>] | ||
``` | ||
DO NOT add tests to this suite that use `-Zprint-mono-items=eager`, that flag changes the way that MonoItem collection works in rather fundamental ways that are otherwise only used by `-Clink-dead-code`, and thus the MonoItems collected and their linkage under `-Zprint-mono-items=eager` does not correlate very well with normal compilation behavior. |
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.
The first comma is another comma splice, lol
Removes a crusty old r=me, I'll let you fix the tiny English flaws, only the "of" one matters at all. |
512b3e3
to
a721dd6
Compare
I fixed all of them, surely this PR is flawless now :) |
@bors r=nnethercore rollup |
…, r=nnethercore Remove -Zinline-in-all-cgus and clean up tests/codegen-units/ Implementation of rust-lang/compiler-team#814 I've taken some liberties with cleaning up the CGU partitioning tests, because that's the only place this flag was used and also mattered. I've often fought a lot with the contents of `tests/codegen-units` and it has never been clear to me when a test failure indicates a problem with my changes as opposed to a test just needing to be manually blessed. Hopefully the combination of the new README, new comments, and using `-Zprint-mono-items=lazy` in the partitioning tests improves that. I've also deleted some of the `tests/run-make/sepcomp` tests. I think all the "sepcomp" tests have been obviated for years by better-designed (less flaky, clearer failures) test suites, but here I'm just deleting the ones I'm confident in.
Implementation of rust-lang/compiler-team#814
I've taken some liberties with cleaning up the CGU partitioning tests, because that's the only place this flag was used and also mattered. I've often fought a lot with the contents of
tests/codegen-units
and it has never been clear to me when a test failure indicates a problem with my changes as opposed to a test just needing to be manually blessed. Hopefully the combination of the new README, new comments, and using-Zprint-mono-items=lazy
in the partitioning tests improves that.I've also deleted some of the
tests/run-make/sepcomp
tests. I think all the "sepcomp" tests have been obviated for years by better-designed (less flaky, clearer failures) test suites, but here I'm just deleting the ones I'm confident in.