Clean up a few tests using clang_lto_profgen #92335
Closed
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.
(1) clang_lto_profgen will add
-flto
(or-flto=thin
) whenlto_supported
:llvm-project/compiler-rt/test/profile/lit.cfg.py
Line 67 in ec36145
llvm-project/compiler-rt/test/lit.common.cfg.py
Line 775 in f0b3654
so we may not need to add
-flto
explicitly (otherwise there is someconfusing about which is used)
(2) two tests use
clang_lto_profgen
, but only one requireslto
.It seems like both should require
lto
since it intends to testclang_lto_profgen
.Item (2) may partially help with #90692 (comment)
At the moment, some bots see LLD, but is using an old copy of LLD which
will break if we increase the
ModuleSummaryIndex::BitCodeSummaryVersion
since the old copy of LLD does not understand the new version.