aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorJason Molenda <jason@molenda.com>2022-12-02 14:39:41 -0800
committerJason Molenda <jason@molenda.com>2022-12-02 14:45:02 -0800
commit0c2b7fa8691e9d1f6c7dd656e44321ef8c84ae87 (patch)
treeed7b27ccdd0c5c3f2cfa57cf0b14f57d5fabb1b3 /clang/lib/Frontend/CompilerInvocation.cpp
parentc6481125925849b1d967ec8c129abfbfc46b8417 (diff)
downloadllvm-0c2b7fa8691e9d1f6c7dd656e44321ef8c84ae87.zip
llvm-0c2b7fa8691e9d1f6c7dd656e44321ef8c84ae87.tar.gz
llvm-0c2b7fa8691e9d1f6c7dd656e44321ef8c84ae87.tar.bz2
Leave DW_OP_addr addresses as load addresses in DWARFExpression
DWARFExpression::Evaluate will convert DW_OP_addr addresses in a DWARF expression into load addresses on the expression stack when there is a StackFrame in the ExecutionContext, this from a change in 2018 in https://reviews.llvm.org/D46362. At the time this was handling a case that came up in swift programs, and is no longer necessary. I generalized this conversion to a load address when a Target is available in https://reviews.llvm.org/D137682 to make a test case possible; this change broke a use case that Ted reported. This change removes my test case, and removes this conversion of a DW_OP_addr into a load address in some instances. Differential Revision: https://reviews.llvm.org/D139226
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions