llvm-project.git/lldb/source/Plugins/SymbolFile/NativePDB/CodeViewRegisterMapping.h, branch main Unnamed repository; edit this file 'description' to name the repository. [NFC][TargetParser] Remove llvm/ADT/Triple.h 2023-02-07T12:39:46+00:00 Archibald Elliott archibald.elliott@arm.com 2023-02-07T12:21:51+00:00 62c7f035b4392c1933550eead6ddab35122720bc I also ran `git clang-format` to get the headers in the right order for the new location, which has changed the order of other headers in two files. 
I also ran `git clang-format` to get the headers in the right order for
the new location, which has changed the order of other headers in two
files.
[LLDB][NativePDB] Switch to use DWARFLocationList. 2022-08-17T20:37:13+00:00 Zequan Wu zequanwu@google.com 2022-07-29T19:35:22+00:00 71d778f33e8615f525f118db351c6541b40199ab Before, NativePDB uses scoped range as a workaround for value range, that causes problems (e.g. a variable's value can only have one range, but usually a variable's value is located at different address ranges, each at different locations, in optimized build). This patch let NativePDB switch to DWARFLocationList so a variable's value can be described at multiple non-overlapped address ranges and each range maps to a location. Because overlapping ranges exists, here's peference when choosing ranges: 1. Always prefer whole value locations. Suppose a variable size is 8 bytes, one record is that for range [1, 5) first 4 bytes is at ecx, and another record is that for range [2, 8) the 8 bytes value is at rdx. This results: [1, 2) has first 4 bytes at ecx, [2, 8) has the whole value at rdx. 2. Always prefer the locations parsed later. Suppose first record is that for range [1, 5) value is at ecx, second record is that for range [2, 6) value is at eax. This results: [1, 2) -> ecx, [2, 6) -> eax. Differential Revision: https://reviews.llvm.org/D130796 
Before, NativePDB uses scoped range as a workaround for value range, that causes
problems (e.g. a variable's value can only have one range, but usually a
variable's value is located at different address ranges, each at different
locations, in optimized build).
This patch let NativePDB switch to DWARFLocationList so a variable's value can
be described at multiple non-overlapped address ranges and each range maps to a
location.
Because overlapping ranges exists, here's peference when choosing ranges:
1. Always prefer whole value locations. Suppose a variable size is 8 bytes, one record is that for range [1, 5) first 4 bytes is at ecx, and another record is that for range [2, 8) the 8 bytes value is at rdx. This results: [1, 2) has first 4 bytes at ecx, [2, 8) has the whole value at rdx.
2. Always prefer the locations parsed later. Suppose first record is that for range [1, 5) value is at ecx, second record is that for range [2, 6) value is at eax. This results: [1, 2) -> ecx, [2, 6) -> eax.

Differential Revision: https://reviews.llvm.org/D130796
[lldb] Update header guards to be consistent and compliant with LLVM (NFC) 2020-02-18T07:15:40+00:00 Jonas Devlieghere jonas@devlieghere.com 2020-02-17T23:57:45+00:00 cdc514e4c67f268b07863bbac3d8d7e0d088186c LLDB has a few different styles of header guards and they're not very consistent because things get moved around or copy/pasted. This patch unifies the header guards across LLDB and converts everything to match LLVM's style. Differential revision: https://reviews.llvm.org/D74743 
LLDB has a few different styles of header guards and they're not very
consistent because things get moved around or copy/pasted. This patch
unifies the header guards across LLDB and converts everything to match
LLVM's style.

Differential revision: https://reviews.llvm.org/D74743
[NFC] Fix license headers after r352845 2019-02-08T08:48:15+00:00 Aleksandr Urakov aleksandr.urakov@jetbrains.com 2019-02-08T08:48:15+00:00 ee21a66a7b807150148bf61167df87a2eb1689e0 llvm-svn: 353503 
llvm-svn: 353503
[PDB] Fix location retrieval for function local variables and arguments that are 2019-02-01T10:01:18+00:00 Aleksandr Urakov aleksandr.urakov@jetbrains.com 2019-02-01T10:01:18+00:00 758657e56550c0681260bb61b0a2bddb4a5c2e6d stored relative to VFRAME Summary: This patch makes LLDB able to retrieve proper values for function arguments and local variables stored in PDB relative to VFRAME register. Patch contains retrieval of corresponding FPO table entries from PDB and a generic translator from FPO programs to DWARF expressions to get correct VFRAME value. Patch also improves variables-locations.test and makes this test passable on x86. Patch By: leonid.mashinsky Reviewers: zturner, asmith, stella.stamenova, aleksandr.urakov Reviewed By: zturner Subscribers: arphaman, labath, mgorny, aprantl, JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D55122 llvm-svn: 352845 
stored relative to VFRAME

Summary:
This patch makes LLDB able to retrieve proper values for function arguments and
local variables stored in PDB relative to VFRAME register.

Patch contains retrieval of corresponding FPO table entries from PDB and a
generic translator from FPO programs to DWARF expressions to get correct VFRAME
value.

Patch also improves variables-locations.test and makes this test passable on
x86.

Patch By: leonid.mashinsky

Reviewers: zturner, asmith, stella.stamenova, aleksandr.urakov

Reviewed By: zturner

Subscribers: arphaman, labath, mgorny, aprantl, JDevlieghere, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D55122

llvm-svn: 352845