aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorOrlando Cazalet-Hyams <orlando.hyams@sony.com>2024-02-01 10:29:08 +0000
committerGitHub <noreply@github.com>2024-02-01 10:29:08 +0000
commitf34418c73b718abb24cd5b921b5a2846011e7d0c (patch)
tree41be4273f668fa8eb68e5a02922de867d4c1b570 /clang/lib/CodeGen/CodeGenModule.cpp
parent1bbb797e9c7f37aa814b9bbaba2961f730a26891 (diff)
downloadllvm-f34418c73b718abb24cd5b921b5a2846011e7d0c.zip
llvm-f34418c73b718abb24cd5b921b5a2846011e7d0c.tar.gz
llvm-f34418c73b718abb24cd5b921b5a2846011e7d0c.tar.bz2
[HWASAN] Remove DW_OP_LLVM_tag_offset from DIExpression::isImplicit (#79816)
According to its doc-comment `isImplicit` is meant to return true if the expression is an implicit location description (describes an object or part of an object which has no location by computing the value from available program state). There's a brief entry for `DW_OP_LLVM_tag_offset` in the LangRef and there's some info in the original commit fb9ce100d19be130d004d03088ccd4af295f3435. From what I can tell it doesn't look like `DW_OP_LLVM_tag_offset` affects whether or not the location is implicit; the opcode doesn't get included in the final location description but instead is added as an attribute to the variable. This was tripping an assertion in the latest application of the fix to #76545, #78606, where an expression containing a `DW_OP_LLVM_tag_offset` is split into a fragment (i.e., describe a part of the whole variable).
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions