aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/AST/ByteCode/Program.cpp
diff options
context:
space:
mode:
authorMichael Buch <michaelbuch12@gmail.com>2025-11-08 00:21:03 +0000
committerGitHub <noreply@github.com>2025-11-08 00:21:03 +0000
commitd5b62fabd17ee14805f4c5c5ac7b0be9bf488211 (patch)
tree7e8881d80386863b61cbad6d824839fb5319265d /clang/lib/AST/ByteCode/Program.cpp
parent8552a8fbffd0573331ce2790784d090349fd885b (diff)
downloadllvm-d5b62fabd17ee14805f4c5c5ac7b0be9bf488211.zip
llvm-d5b62fabd17ee14805f4c5c5ac7b0be9bf488211.tar.gz
llvm-d5b62fabd17ee14805f4c5c5ac7b0be9bf488211.tar.bz2
[lldb][ClangModulesDeclVendor] Print Clang module loading errors to expression log instead of console (#166964)
Depends on: * https://github.com/llvm/llvm-project/pull/166917 * https://github.com/llvm/llvm-project/pull/166940 While these errors can contribute to an expression failing, they are never *the* reason the expression failed. I.e., they are always just 'note:' diagnostics that we hand-emit. Because they are quite noisy (and we potentially have many of them if we auto-load all modules in a CU), this patch logs the errors to the `expr` log, instead of the console. Previously these errors would only get omitted when the expression itself failed. Meaning if the expression failed, we'd dump these 'note' module load errors in next to the actual expression error, obscuring the output. Moreover, if the expression succeeded, any module load errors would be dropped. Now we always log all module loading errors to the expression log, regardless of whether the expression fails or not.
Diffstat (limited to 'clang/lib/AST/ByteCode/Program.cpp')
0 files changed, 0 insertions, 0 deletions