-
Notifications
You must be signed in to change notification settings - Fork 14.4k
[clang-tidy][NFC] fix compilation by disambiguating equality operator #147048
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
[clang-tidy][NFC] fix compilation by disambiguating equality operator #147048
Conversation
Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers. If you have further questions, they may be answered by the LLVM GitHub User Guide. You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums. |
@llvm/pr-subscribers-clang-tools-extra @llvm/pr-subscribers-clang-tidy Author: Gregor Jasny (gjasny) ChangesThis fixes an issue compiling LLVM 20.1.7 on Ubuntu 22.04 with the Ubuntu provided Clang 14 and C++20. That's probably happening due to incomplete C++20 support in either Clang 14 or the GNU libstdc++ 12. The actual error is:
I know that clang-14 in combination with the GNU libstdc++ 12 might not be 100% C++20 compliant. But this is the only error we see when compiling LLVM 20.1.7 and it looks very fixable. Would it be possible to cherry-pick the fix to the Thanks, Full diff: https://github.com/llvm/llvm-project/pull/147048.diff 1 Files Affected:
diff --git a/clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp b/clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
index db0ac281ddfcf..7a4d43fc49320 100644
--- a/clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
+++ b/clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
@@ -144,7 +144,7 @@ TaggedUnionMemberCountCheck::getNumberOfEnumValues(const EnumDecl *ED) {
if (EnableCountingEnumHeuristic && LastEnumConstant &&
isCountingEnumLikeName(LastEnumConstant->getName()) &&
- (LastEnumConstant->getInitVal() == (EnumValues.size() - 1))) {
+ (LastEnumConstant->getInitVal() == llvm::APSInt::getUnsigned(EnumValues.size() - 1u))) {
return {EnumValues.size() - 1, LastEnumConstant};
}
|
✅ With the latest revision this PR passed the C/C++ code formatter. |
7452d3c
to
2585b9c
Compare
clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
Outdated
Show resolved
Hide resolved
2585b9c
to
df2f97d
Compare
Current standard that LLVM use is c++17. But we generally should support compilers at least 3 years of compilers.
I don't have much knowledge on cherry-picking to release, but the latest release of 20.x could be on Jul 8th (if it even happens, see https://llvm.org/). I have a slight feeling that it's not worth cherry-picking, If LLVM is compiled from source, would it be feasible to just use 21st LLVM branch that will be released soon, gjasny? |
clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
Outdated
Show resolved
Hide resolved
Correct, but we also want to support being able to compile with C++20. I think there are build bots for that set up.
The compile error is in a cpp file, so it would only happen to people compiling the clang-tidy libs with C++20 which has an even smaller chance of happening, but still. IMO this should just go into LLVM 20, it's a trivial fix. |
I don't oppose, then just note that we don't have much time till 20th final release. |
This fixes a compilation issue on Ubuntu 22.04 with the Ubuntu provided Clang 14 and C++20. That's probably happening due to incomplete C++20 support in either Clang 14 or the GNU libstdc++ 12. Signed-off-by: Gregor Jasny <[email protected]>
df2f97d
to
f1ff857
Compare
All builds are green, now. |
clang-tools-extra/clang-tidy/bugprone/TaggedUnionMemberCountCheck.cpp
Outdated
Show resolved
Hide resolved
I see you are a member, but it seems like this is your first contribution. |
Hello Victor,
You're right. Besides some bug reports I never landed a commit in llvm. Is there anything I could do right now (besides waiting for reviews)?
Thanks for the heads-up. I cleared the commit description. |
@gjasny Congratulations on having your first Pull Request (PR) merged into the LLVM Project! Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR. Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues. How to do this, and the rest of the post-merge process, is covered in detail here. If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again. If you don't get any reports, no action is required from you. Your changes are working as expected, well done! |
This fixes an issue compiling LLVM 20.1.7 on Ubuntu 22.04 with the Ubuntu provided Clang 14 and C++20. That's probably happening due to incomplete C++20 support in either Clang 14 or the GNU libstdc++ 12.
The actual error is:
I know that clang-14 in combination with the GNU libstdc++ 12 might not be 100% C++20 compliant. But this is the only error we see when compiling LLVM 20.1.7 and it looks very fixable. Would it be possible to cherry-pick the fix to the
release/20.x
branch?Thanks,
Gregor