| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[LLDB][NativePDB] Add MSInheritanceAttr when creating pointer type that is a pointer to member. Differential Revision: https://reviews.llvm.org/D129807 | 3 年前 | |
Re-land "[test] Split LLDB tests into API, Shell & Unit" The original patch got reverted because it broke check-lldb on a clean build. This fixes that. llvm-svn: 374201 | 6 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[LLDB][NativePDB] Fix function decl creation for class methods This is a split of D113724. Calling TypeSystemClang::AddMethodToCXXRecordType to create function decls for class methods. Differential Revision: https://reviews.llvm.org/D113930 | 4 年前 | |
[LLDB][NativePDB] Add MSInheritanceAttr when creating pointer type that is a pointer to member. Differential Revision: https://reviews.llvm.org/D129807 | 3 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[lldb] Require x86 for various NativePDB, Breakpad and Minidump tests These tests fail if you build without the x86 llvm backend. Either because they use an x86 triple or try to backtrace which requires some x86 knowledge to see all frames. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D100194 | 5 年前 | |
[LLDB][NativePDB] Fix function decl creation for class methods This is a split of D113724. Calling TypeSystemClang::AddMethodToCXXRecordType to create function decls for class methods. Differential Revision: https://reviews.llvm.org/D113930 | 4 年前 | |
[clang] retain type sugar in auto / template argument deduction This implements the following changes: * AutoType retains sugared deduced-as-type. * Template argument deduction machinery analyses the sugared type all the way down. It would previously lose the sugar on first recursion. * Undeduced AutoType will be properly canonicalized, including the constraint template arguments. * Remove the decltype node created from the decltype(auto) deduction. As a result, we start seeing sugared types in a lot more test cases, including some which showed very unfriendly type-parameter-*-* types. Signed-off-by: Matheus Izvekov <mizvekov@gmail.com> Reviewed By: rsmith, #libc, ldionne Differential Revision: https://reviews.llvm.org/D110216 | 4 年前 | |
[lldb] Require x86 for various NativePDB, Breakpad and Minidump tests These tests fail if you build without the x86 llvm backend. Either because they use an x86 triple or try to backtrace which requires some x86 knowledge to see all frames. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D100194 | 5 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
Recommit: Compress formatting of array type names (int [4] -> int[4]) Based on post-commit review discussion on 2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith. Other uses of forcing HasEmptyPlaceHolder to false seem OK to me - they're all around pointer/reference types where the pointer/reference token will appear at the rightmost side of the left side of the type name, so they make nested types (eg: the "int" in "int *") behave as though there is a non-empty placeholder (because the "*" is essentially the placeholder as far as the "int" is concerned). This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075c Reverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakages outside of clang - lldb seems to have some strange/strong dependence on "char [N]" versus "char[N]" when printing strings (not due to that name appearing in DWARF, but probably due to using clang to stringify type names) that'll need to be addressed, plus a few other odds and ends in other subprojects (clang-tools-extra, compiler-rt, etc). | 4 年前 | |
[lldb] Fix globals-bss.cpp which was broken in https://reviews.llvm.org/D105055 -S replaced -s, so the test needs to be updated to use the new option | 4 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[LLDB][NativePDB] Fix inline line info in line table It fixes the following case: 0602 line 1 (+1) 0315 code 0x15 (+0x15) 0B2B code 0x20 (+0xB) line 2 (+1) 0602 line 3 (+1) 0311 code 0x31 (+0x11) ... Inline ranges should have following mapping: [0x15, 0x20) -> line 1 [0x20, 0x31) -> line 2 Inline line entries: 0x15, line 1, 0x20, line 2, 0x31, line 3. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D123092 | 4 年前 | |
[LLDB][NativePDB] Create inline function decls This creates inline functions decls in the TUs where the funcitons are inlined and local variable decls inside those functions. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D121967 | 4 年前 | |
[lldb] Skip PDB and NativePDB tests with reproducers | 5 年前 | |
[FastISel] Flush local value map on every instruction Local values are constants or addresses that can't be folded into the instruction that uses them. FastISel materializes these in a "local value" area that always dominates the current insertion point, to try to avoid materializing these values more than once (per block). https://reviews.llvm.org/D43093 added code to sink these local value instructions to their first use, which has two beneficial effects. One, it is likely to avoid some unnecessary spills and reloads; two, it allows us to attach the debug location of the user to the local value instruction. The latter effect can improve the debugging experience for debuggers with a "set next statement" feature, such as the Visual Studio debugger and PS4 debugger, because instructions to set up constants for a given statement will be associated with the appropriate source line. There are also some constants (primarily addresses) that could be produced by no-op casts or GEP instructions; the main difference from "local value" instructions is that these are values from separate IR instructions, and therefore could have multiple users across multiple basic blocks. D43093 avoided sinking these, even though they were emitted to the same "local value" area as the other instructions. The patch comment for D43093 states: Local values may also be used by no-op casts, which adds the register to the RegFixups table. Without reversing the RegFixups map direction, we don't have enough information to sink these instructions. This patch undoes most of D43093, and instead flushes the local value map after(*) every IR instruction, using that instruction's debug location. This avoids sometimes incorrect locations used previously, and emits instructions in a more natural order. In addition, constants materialized due to PHI instructions are not assigned a debug location immediately; instead, when the local value map is flushed, if the first local value instruction has no debug location, it is given the same location as the first non-local-value-map instruction. This prevents PHIs from introducing unattributed instructions, which would either be implicitly attributed to the location for the preceding IR instruction, or given line 0 if they are at the beginning of a machine basic block. Neither of those consequences is good for debugging. This does mean materialized values are not re-used across IR instruction boundaries; however, only about 5% of those values were reused in an experimental self-build of clang. (*) Actually, just prior to the next instruction. It seems like it would be cleaner the other way, but I was having trouble getting that to work. This reapplies commits cf1c774d and dc35368c, and adds the modification to PHI handling, which should avoid problems with debugging under gdb. Differential Revision: https://reviews.llvm.org/D91734 | 5 年前 | |
[LLDB][NativePDB] Fix the case when S_DEFRANGE_SUBFIELD_REGISTERs are out of order. Previously, I was assuming that S_DEFRANGE_SUBFIELD_REGISTERs are always in the increasing order of offset_in_parent until I saw a counter example. Using std::map so that they are sorted by offset_in_parent. Differential Revision: https://reviews.llvm.org/D124061 | 4 年前 | |
[LLDB] Fix NativePDB/local-variables.cpp for AArch64/Windows This patch fixes NativePDB/local-variables.cpp test for AArch64 Windows. There are two changes: 1) Replace function breakpoint with line breakpoint required due to pr56288 2) Adjust "target modules dump ast" test as the output was slightly different on AArch64/Windows. | 3 年前 | |
[lldb] Return StringRef from PluginInterface::GetPluginName There is no reason why this function should be returning a ConstString. While modifying these files, I also fixed several instances where GetPluginName and GetPluginNameStatic were returning different strings. I am not changing the return type of GetPluginNameStatic in this patch, as that would necessitate additional changes, and this patch is big enough as it is. Differential Revision: https://reviews.llvm.org/D111877 | 4 年前 | |
[LLDB][NativePDB] Fix image lookup by address image lookup -a doesn't work because the compilands list is always empty. Create CU at given index if doesn't exit. Differential Revision: https://reviews.llvm.org/D113821 | 4 年前 | |
[LLDB][NativePDB] Don't complete static members' types when completing a record type. UdtRecordCompleter shouldn't complete static members' types. static members' types are going to be completed when the types are called in SymbolFile::CompleteType. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D121030 | 4 年前 | |
[LLDB][NativePDB] Check for missing type info to avoid crash. NativePDB often assumes that all debug info are available. This is one step to make it more pervasive. Differential Revision: https://reviews.llvm.org/D125844 | 4 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[lldb] Require x86 for various NativePDB, Breakpad and Minidump tests These tests fail if you build without the x86 llvm backend. Either because they use an x86 triple or try to backtrace which requires some x86 knowledge to see all frames. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D100194 | 5 年前 | |
[lldb/PDB] Make "native" pdb tests host-independent These test don't execute the binaries they build, and so they don't need to build for the host. By hardcoding the target, we don't have do xfail or skip them for targets which don't have the appropriate support in clang(-cl). | 6 年前 | |
[LLDB][NativePDB] Add support for S_DEFRANGE_REGISTER and S_DEFRANGE_SUBFIELD_REGISTER Differential Revision: https://reviews.llvm.org/D119508 | 4 年前 | |
[LLDB][NativePDB] Fix subfield_register_simple_type.s test | 4 年前 | |
[LLDB][Clang] add AccessSpecDecl for methods and fields in RecordType This allows access type be printed when running lldb-test -dump-ast and lldb-test -dump-clang-ast. Differential Revision: https://reviews.llvm.org/D115062 | 4 年前 | |
Re-land "[test] Split LLDB tests into API, Shell & Unit" The original patch got reverted because it broke check-lldb on a clean build. This fixes that. llvm-svn: 374201 | 6 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 6 年前 |