aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-objdump/llvm-objdump.cpp
diff options
context:
space:
mode:
authorAdrian Prantl <aprantl@apple.com>2017-02-08 17:44:43 +0000
committerAdrian Prantl <aprantl@apple.com>2017-02-08 17:44:43 +0000
commita5bf2d7003928e5ada8e22d4bbf0c776633eecab (patch)
tree5dfa466d3e37dd36416b2a9be4ddd7a70acd8984 /llvm/tools/llvm-objdump/llvm-objdump.cpp
parentd11a03b263f676bd198711b8e2818577228be648 (diff)
downloadllvm-a5bf2d7003928e5ada8e22d4bbf0c776633eecab.zip
llvm-a5bf2d7003928e5ada8e22d4bbf0c776633eecab.tar.gz
llvm-a5bf2d7003928e5ada8e22d4bbf0c776633eecab.tar.bz2
Fix bitcode upgrade for DIGlobalVariables with a var: field.
This is a follow-up to https://reviews.llvm.org/D29349. It turns out that NeedUpgradeToDIGlobalVariableExpression is always necessary when we encountered a version==0 record because it may always be referenced via a list of globals in a DICompileUnit. My tests weren't good enough to catch this though. To trigger this case, we need much older bitcode produced by LLVM around version 3.7. <rdar://problem/30404262> Differential Revision: https://reviews.llvm.org/D29693 llvm-svn: 294488
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions