aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/TargetParser.cpp
diff options
context:
space:
mode:
authorKadir Cetinkaya <kadircet@google.com>2022-01-20 17:22:09 +0100
committerKadir Cetinkaya <kadircet@google.com>2022-01-21 12:37:20 +0100
commit597eae998a874a872b67d1a22a04d7c45d2ef94b (patch)
tree3529de03fe4d89cc33298eee6fd928450697f21a /llvm/lib/Support/TargetParser.cpp
parentbfbdb5e43e50484e179122bfb66cff8165e4b084 (diff)
downloadllvm-597eae998a874a872b67d1a22a04d7c45d2ef94b.zip
llvm-597eae998a874a872b67d1a22a04d7c45d2ef94b.tar.gz
llvm-597eae998a874a872b67d1a22a04d7c45d2ef94b.tar.bz2
[clangd][Background] Make index validation logs verbose
These errors are non-harmful and should be transient. They either imply: - compilation database returned stale results for TUs and it'll be fixed once it's updated to match project state. - a TUs dependencies has changed and some headers no longer exist. this should be fixed with the next indexing cycle. In either case the user will have some stale symbols in their index until clangd restarts and the underlying issue is resolved. On the downside these logs are confusing users when there's another issue. Differential Revision: https://reviews.llvm.org/D117792
Diffstat (limited to 'llvm/lib/Support/TargetParser.cpp')
0 files changed, 0 insertions, 0 deletions