Experiment: See the impact of codegen-units=1 on macOS
#4209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Throwing this up to experiment if setting LLVM's
codegen-unitsflag to 1 has any impact on #4196, per rust-lang/rust#60925 and similar reported issues on macOS.This disables parallel compilation which will likely cast too broad a net on non-affected platforms (assuming this winds up being the issue). A named profile override would have been better, but as that's an unstable nightly feature and I haven't figured out if it's possible to set llvm flags via
cargo testwithout dropping down tocargo rustcand doing it manually, I'll stick with this crude attempt for now to see what happens.