clang-tidy-18: segmentation fault in the modernize-use-constraints check on processing boost::multiprecision::abs
#91872
Assignees
Labels
Comments
|
How to reproduce: |
PiotrZSL
added a commit
to PiotrZSL/llvm-project
that referenced
this issue
May 13, 2024
Improved modernize-use-constraints check by fixing a crash that occurred in some scenarios and excluded system headers from analysis. Problem were with DependentNameTypeLoc having null type location as getQualifierLoc().getTypeLoc(). Fixes llvm#91872
PiotrZSL
added a commit
that referenced
this issue
May 15, 2024
Improved modernize-use-constraints check by fixing a crash that occurred in some scenarios and excluded system headers from analysis. Problem were with DependentNameTypeLoc having null type location as getQualifierLoc().getTypeLoc(). Fixes #91872
mub-at-arm
pushed a commit
to mub-at-arm/llvm-project
that referenced
this issue
May 16, 2024
Improved modernize-use-constraints check by fixing a crash that occurred in some scenarios and excluded system headers from analysis. Problem were with DependentNameTypeLoc having null type location as getQualifierLoc().getTypeLoc(). Fixes llvm#91872
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduced on
clang-18(release) andclang-19(built from sources)Crash report from clang-18:
Full build log is here: https://s3.amazonaws.com/clickhouse-builds/PRs/60469/23cf6d0d8bde07e4ef9e42b8d821dbfb3eb786dc/binary_tidy/build_log.log
It is related to this PR: ClickHouse/ClickHouse#60469
Crash report from master:
I tried to disable clang-tidy for the corresponding source files by adding these lines on top:
but it didn't help.
The source that is related to the crash is here: https://github.com/ClickHouse/boost/blob/ae94606a70f1e298ce2a5718db858079185c4d9c/boost/multiprecision/detail/default_ops.hpp
The text was updated successfully, but these errors were encountered: