aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorMuhammad Omair Javaid <omair.javaid@linaro.org>2021-02-08 14:08:19 +0500
committerMuhammad Omair Javaid <omair.javaid@linaro.org>2021-02-08 14:09:15 +0500
commit8561ad9296b70b5a2af1574a1576090520d62a7c (patch)
treeaa23871722e3fd37f485ca7c71ab45a35b86a1ff /clang/lib/Frontend/CompilerInvocation.cpp
parentbec6b5e3cec71a9560cc761fd7804f354c3aca02 (diff)
downloadllvm-8561ad9296b70b5a2af1574a1576090520d62a7c.zip
llvm-8561ad9296b70b5a2af1574a1576090520d62a7c.tar.gz
llvm-8561ad9296b70b5a2af1574a1576090520d62a7c.tar.bz2
Use remote regnums in expedited list, value regs and invalidate regs
Native register descriptions in LLDB specify lldb register numbers in value_regs and invalidate_regs lists. These register numbers may not match with Process gdb-remote register numbers which are generated by native process after counting all registers in its register sets. It was coincidentally not causing any problems as we never came across a native target with dynamically changing register sets and register numbers generated by counter matched with LLDB native register numbers. This came up while testing target AArch64 SVE which can choose register sets based on underlying hardware. This patch fixes this behavior and always tries to use remote register numbers while reading/writing registers over gdb-remote protocol. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D77043
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions