aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
diff options
context:
space:
mode:
authorFangrui Song <maskray@google.com>2020-02-24 17:54:39 -0800
committerFangrui Song <maskray@google.com>2020-02-25 18:18:13 -0800
commitd0c4277d388628154b647a45cbc6914a1ea5a822 (patch)
treebe818dee2872963d25478770f08fb4a6906c1894 /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
parent6fb70c87251708af8fc27b501fd79e26162f7e65 (diff)
downloadllvm-d0c4277d388628154b647a45cbc6914a1ea5a822.zip
llvm-d0c4277d388628154b647a45cbc6914a1ea5a822.tar.gz
llvm-d0c4277d388628154b647a45cbc6914a1ea5a822.tar.bz2
[MC][ARM] Don't create multiple .ARM.exidx associated to one .text
Fixed an issue exposed by D74006. In clang cc1as, MCContext::UseNamesOnTempLabels is true. When parsing a .fnstart directive, FnStart gets redefined to a temporary symbol of a different name (.Ltmp0, .Ltmp1, ...). MCContext::getELFSection() called by SwitchToEHSection() will create a different .ARM.exidx each time. llvm-mc uses `Ctx.setUseNamesOnTempLabels(false);` and FnStart is unnamed. MCContext::getELFSection() called by SwitchToEHSection() will reuse the same .ARM.exidx . Reviewed By: efriedma Differential Revision: https://reviews.llvm.org/D75095
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions