aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2020-12-10 15:38:21 +0100
committerRaphael Isemann <teemperor@gmail.com>2020-12-10 17:35:03 +0100
commit839e845277894ad37fbca8063cbf1955331fbeff (patch)
tree80979e90c9dc79a6821bb319e40e3c3e60c93dce /clang/lib/Frontend/CompilerInvocation.cpp
parentc9e967af3fc7ce824cd811379c5e99a998819779 (diff)
downloadllvm-839e845277894ad37fbca8063cbf1955331fbeff.zip
llvm-839e845277894ad37fbca8063cbf1955331fbeff.tar.gz
llvm-839e845277894ad37fbca8063cbf1955331fbeff.tar.bz2
[lldb] Remove assumption from Clang-based data formatters that their types are in the scratch AST
Several data formatters assume their types are in the Target's scratch AST and build new types from that scratch AST instance. However, types from different ASTs shouldn't be mixed, so this (unchecked) assumption may lead to problems if we ever have more than one scratch AST or someone somehow invokes data formatters on a type that are not in the scratch AST. Instead we can use in all the formatters just the TypeSystem of the type we're formatting. That's much simpler and avoids all the headache of finding the right TypeSystem that matches the one of the formatted type. Right now LLDB only has one scratch TypeSystemClang instance and we format only types that are in the scratch AST, so this doesn't change anything in the current way LLDB works. The intention here is to allow follow up refactorings that introduce multiple scratch ASTs with the same Target. Differential Revision: https://reviews.llvm.org/D92757
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions