This is a fix for #53963.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM! Can you also add a release note for the fix?
I'm happy to land this on your behalf if you'd prefer, but given that you've had several quality commits already, you might want to consider asking for your commit privileges: https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access.
Thank you for the review and the recommendation to become a committer! I have just been granted the privileges and have landed the change on the main branch including a mention of the fix in the release notes. I hope this is all right.
Congrats!
I double-checked the commit and everything looks correct to me. Thanks for the fix!
Note that __int128_t is not available everywhere, generally only on 64-bit platforms.
clang-tools-extra/test/clang-tidy/checkers/bugprone-sizeof-expression.cpp | ||
---|---|---|
175 | This causes test failures on 32-bit architectures: /home/tcwg-buildbot/worker/clang-armv7-2stage/stage2/tools/clang/tools/extra/test/clang-tidy/checkers/Output/bugprone-sizeof-expression.cpp.tmp.cpp:175:11: error: unknown type name '__int128_t' [clang-diagnostic-error] template <__int128_t N> ^ It's probably best to wrap this in #ifdef __SIZEOF_INT128__ lest we disable the entire test on the affected platforms. |
clang-tools-extra/test/clang-tidy/checkers/bugprone-sizeof-expression.cpp | ||
---|---|---|
175 | Good catch! @SimplyDanny, can you fix up the test? |
clang-tools-extra/test/clang-tidy/checkers/bugprone-sizeof-expression.cpp | ||
---|---|---|
175 | Sure. I will fix it. Sorry for the issue ... What is the process in this case? Push the fix directly to main or go the normal path via Phabricator review? |
clang-tools-extra/test/clang-tidy/checkers/bugprone-sizeof-expression.cpp | ||
---|---|---|
175 | When fixing a broken test, you can generally push directly to main. (And if the fix requires thought, it's usually best to revert the broken commit from main until you have the test fixed, then push the fixed commit back to main). |
This causes test failures on 32-bit architectures:
It's probably best to wrap this in #ifdef __SIZEOF_INT128__ lest we disable the entire test on the affected platforms.