https://github.com/labath closed
https://github.com/llvm/llvm-project/pull/122933
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Pavel Labath
Date: 2025-01-15T10:37:06+01:00
New Revision: eb96c8c105226956c8ed5ab30699206f53de74f7
URL:
https://github.com/llvm/llvm-project/commit/eb96c8c105226956c8ed5ab30699206f53de74f7
DIFF:
https://github.com/llvm/llvm-project/commit/eb96c8c105226956c8ed5ab30699206f53de74f7.diff
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/123046
I think the only issue here was that we would erroneously consider functions
which are "in the middle" of the function were stepping to as a part of the
function, and would try to step into them (likely stepping
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
I think the only issue here was that we would erroneously consider functions
which are "in the middle" of the function were stepping to as a part of the
function, and would try to step into them (likely steppi
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r
7201cae106260aeb3e97d5291ff30f05076a...74d436310319d17cb43ba598836b70a92c827111
lldb/
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/123046
>From 74d436310319d17cb43ba598836b70a92c827111 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 15 Jan 2025 12:41:23 +0100
Subject: [PATCH 1/2] [lldb] Fix SBThread::StepOverUntil for discontinuous
function
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/123054
Anonymous namespaces are supposed to be optional when looking up types. This
was not working in combination with -gsimple-template-names, because the way it
was constructing the complete (with template args) nam
@@ -2740,18 +2738,11 @@ void SymbolFileDWARF::FindTypes(const TypeQuery &query,
TypeResults &results) {
// Copy our match's context and update the basename we are looking for
// so we can use this only to compare the context correctly.
m_index->GetTypesWithQu
dlav-sc wrote:
> Hi @dlav-sc I am looking at commits that warrant a release note for LLDB 20,
> and I think this is one of them. If you want to do that yourself you can send
> a PR adding a bullet point to
> https://github.com/llvm/llvm-project/blob/main/llvm/docs/ReleaseNotes.md#changes-to-ll
@@ -511,22 +513,58 @@ ValueObjectSP
StackFrame::GetValueForVariableExpressionPath(
VariableSP &var_sp, Status &error) {
ExecutionContext exe_ctx;
CalculateExecutionContext(exe_ctx);
+
bool use_DIL = exe_ctx.GetTargetRef().GetUseDIL(&exe_ctx);
+
if (use_DIL)
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `openmp-s390x-linux`
running on `systemz-1` while building `clang,lldb` at step 6 "test-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/88/builds/6804
Here is the relevant piece of the build l
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/123005
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -165,10 +169,14 @@ bool SBInstructionList::GetDescription(Stream &sref) {
addr, eSymbolContextEverything, sc);
}
+if (next_addr && addr != next_addr)
labath wrote:
It doesn't *need* to be because `std::optional` defines an ope
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/122933
>From dd5dba70fe99d2510e9e1903b7f1f9a141f1572d Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Tue, 14 Jan 2025 17:17:28 +0100
Subject: [PATCH 1/2] [lldb] Implement (SB)Function::GetInstructions for
discontinu
https://github.com/DavidSpickett approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/122933
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -377,7 +377,12 @@ ParsedDWARFTypeAttributes::ParsedDWARFTypeAttributes(const
DWARFDIE &die) {
break;
case DW_AT_object_pointer:
- object_pointer = form_value.Reference();
+ // GetAttributes follows DW_AT_specification.
+ // DW_TAG_subprogram defini
https://github.com/jeffreytan81 approved this pull request.
https://github.com/llvm/llvm-project/pull/123125
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/123148
This patch cleans up some code and allows users to not have to specify a size
and now get a more realistic value when reading modules from memory. This patch
is in preparation for starting to have the dynamic
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Greg Clayton (clayborg)
Changes
This patch cleans up some code and allows users to not have to specify a size
and now get a more realistic value when reading modules from memory. This patch
is in preparation for starting to have the dynami
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/123132
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,72 @@
+%feature("docstring",
+"A container for options to use when saving a core file.
JDevlieghere wrote:
```suggestion
"A container to specify how to save a core file.
```
https://github.com/llvm/llvm-project/pull/123132
@@ -0,0 +1,72 @@
+%feature("docstring",
+"A container for options to use when saving a core file.
+
+SBSaveCoreOptions includes API's to specify the memory regions and threads to
include
+when generating a core file. These options are not exclusive the existing
SaveCoreStyle opt
@@ -0,0 +1,72 @@
+%feature("docstring",
+"A container for options to use when saving a core file.
+
+SBSaveCoreOptions includes API's to specify the memory regions and threads to
include
+when generating a core file. These options are not exclusive the existing
SaveCoreStyle opt
https://github.com/JDevlieghere commented:
I left a few suggestions in terms of wordsmithing.
https://github.com/llvm/llvm-project/pull/123132
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/ll
https://github.com/adrian-prantl approved this pull request.
Either returning true or false is perfectly fine. The only argument I can come
up for returning true is that now all call sites need to replicate this check
as to not call this function with a size of 0.
https://github.com/llvm/llvm-
clayborg wrote:
Going to give others time to give feedback before merging.
https://github.com/llvm/llvm-project/pull/123125
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123089
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/123107
>From f83e29d9b6fc747584485bae3f519dcd34a5bb0b Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Wed, 15 Jan 2025 10:42:35 -0800
Subject: [PATCH 1/2] [lldb] Handle a byte size of zero in
CompilerType:
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jacob Lalonde (Jlalond)
Changes
SBSaveCoreOptions has been around for awhile now, so I decided to draft up some
Docstrings describing the functionality better. Some of my wording sounded a
bit clunky due the optionality of each method call
https://github.com/Jlalond created
https://github.com/llvm/llvm-project/pull/123132
SBSaveCoreOptions has been around for awhile now, so I decided to draft up some
Docstrings describing the functionality better. Some of my wording sounded a
bit clunky due the optionality of each method call so
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/123125
There was a bug in both the GNU and libc++ library synthetic child providers
when a typedef was used in the type of the variable. Previous code was looking
at the top level typename to try and determine if std
llvmbot wrote:
@llvm/pr-subscribers-clang-modules
Author: Chuanqi Xu (ChuanqiXu9)
Changes
Part for relanding https://github.com/llvm/llvm-project/pull/122887.
I split this to test where the performance regession comes from if modules are
not used.
---
Full diff: https://github.com/llvm/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Chuanqi Xu (ChuanqiXu9)
Changes
Part for relanding https://github.com/llvm/llvm-project/pull/122887.
I split this to test where the performance regession comes from if modules are
not used.
---
Full diff: https://github.com/llvm/llvm-proj
https://github.com/ChuanqiXu9 created
https://github.com/llvm/llvm-project/pull/123152
Part for relanding https://github.com/llvm/llvm-project/pull/122887.
I split this to test where the performance regession comes from if modules are
not used.
>From 15e0af0c7a7f93a2f4fce6c996ef50726770a4ea M
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Chuanqi Xu (ChuanqiXu9)
Changes
Part for relanding https://github.com/llvm/llvm-project/pull/122887.
I split this to test where the performance regession comes from if modules are
not used.
---
Full diff: https://github.com/llvm/llvm-pro
ChuanqiXu9 wrote:
@nikic hi, could you test if this patch may trigger the compilation time
regression?
https://github.com/llvm/llvm-project/pull/123152
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
https://github.com/ChuanqiXu9 updated
https://github.com/llvm/llvm-project/pull/123152
>From 3b3a9575f47c786db93fc0524d019fad5ef7cd61 Mon Sep 17 00:00:00 2001
From: Chuanqi Xu
Date: Thu, 16 Jan 2025 11:30:30 +0800
Subject: [PATCH] [AST] Add OriginalDC argument to
ExternalASTSource::FindExterna
Author: Greg Clayton
Date: 2025-01-15T16:30:45-08:00
New Revision: b7722fbcab4d769be54ae3001f311b2955ef6134
URL:
https://github.com/llvm/llvm-project/commit/b7722fbcab4d769be54ae3001f311b2955ef6134
DIFF:
https://github.com/llvm/llvm-project/commit/b7722fbcab4d769be54ae3001f311b2955ef6134.diff
https://github.com/clayborg closed
https://github.com/llvm/llvm-project/pull/123125
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Chuanqi Xu
Date: 2025-01-16T10:23:11+08:00
New Revision: 731db2a03e096fe42196f0ae6531179b998b0bf8
URL:
https://github.com/llvm/llvm-project/commit/731db2a03e096fe42196f0ae6531179b998b0bf8
DIFF:
https://github.com/llvm/llvm-project/commit/731db2a03e096fe42196f0ae6531179b998b0bf8.diff
LO
https://github.com/felipepiovezan created
https://github.com/llvm/llvm-project/pull/123145
Currently, an LLDB target option controls whether plugins report all threads.
However, it seems natural for this knowledge could come from the plugin itself.
To support this, this commits adds a virtual
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Felipe de Azevedo Piovezan (felipepiovezan)
Changes
Currently, an LLDB target option controls whether plugins report all threads.
However, it seems natural for this knowledge could come from the plugin itself.
To support this, this commits
Author: Augusto Noronha
Date: 2025-01-15T15:19:30-08:00
New Revision: 3241d915b1b8257fd6234461b04e4775fc7ed9fb
URL:
https://github.com/llvm/llvm-project/commit/3241d915b1b8257fd6234461b04e4775fc7ed9fb
DIFF:
https://github.com/llvm/llvm-project/commit/3241d915b1b8257fd6234461b04e4775fc7ed9fb.dif
arichardson wrote:
Sanitizer build has been fixed but I know this will also break the Fuchsia
build bots if we reland it (see
https://github.com/llvm/llvm-project/pull/115379#issuecomment-2469268557) - not
sure if there is any plan to update those builders to use installed toolchains
for the
ChuanqiXu9 wrote:
> Looks like this change has some compile-time impact even if modules are not
> used:
> https://llvm-compile-time-tracker.com/compare.php?from=edc02351dd11cc4a39b7c541b26b71c6f36c8e55&to=7201cae106260aeb3e97d5291ff30f05076a&stat=instructions:u
> It seems to add about 0.5%
@@ -511,22 +513,58 @@ ValueObjectSP
StackFrame::GetValueForVariableExpressionPath(
VariableSP &var_sp, Status &error) {
ExecutionContext exe_ctx;
CalculateExecutionContext(exe_ctx);
+
bool use_DIL = exe_ctx.GetTargetRef().GetUseDIL(&exe_ctx);
+
if (use_DIL)
@@ -511,22 +513,58 @@ ValueObjectSP
StackFrame::GetValueForVariableExpressionPath(
VariableSP &var_sp, Status &error) {
ExecutionContext exe_ctx;
CalculateExecutionContext(exe_ctx);
+
bool use_DIL = exe_ctx.GetTargetRef().GetUseDIL(&exe_ctx);
+
if (use_DIL)
@@ -0,0 +1,228 @@
+//===-- DILAST.cpp
===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -401,12 +399,28 @@ static CompilerContext GetContextEntry(DWARFDIE die) {
return ctx(CompilerContextKind::Typedef);
case DW_TAG_base_type:
return ctx(CompilerContextKind::Builtin);
+ case DW_TAG_class_type:
+ case DW_TAG_structure_type:
+ case DW_TAG_union_type:
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/122128
>From f6aee6ad61745e20079d7d56a643dc61a49132b8 Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 8 Jan 2025 15:27:30 +
Subject: [PATCH] faster indexing
---
.../Plugins/SymbolFile/DWARF/DWARFUnit.h
nikic wrote:
Looks like this change has some compile-time impact even if modules are not
used:
https://llvm-compile-time-tracker.com/compare.php?from=edc02351dd11cc4a39b7c541b26b71c6f36c8e55&to=7201cae106260aeb3e97d5291ff30f05076a&stat=instructions:u
It seems to add about 0.5% to C++ compi
@@ -401,12 +399,28 @@ static CompilerContext GetContextEntry(DWARFDIE die) {
return ctx(CompilerContextKind::Typedef);
case DW_TAG_base_type:
return ctx(CompilerContextKind::Builtin);
+ case DW_TAG_class_type:
+ case DW_TAG_structure_type:
+ case DW_TAG_union_type:
https://github.com/Michael137 created
https://github.com/llvm/llvm-project/pull/123089
In https://github.com/llvm/llvm-project/pull/122742 we will start attaching
DW_AT_object_pointer to method declarations (in addition to definitions).
Currently when LLDB parses a `DW_TAG_subprogram` definiti
https://github.com/Michael137 ready_for_review
https://github.com/llvm/llvm-project/pull/123089
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Michael Buch (Michael137)
Changes
In https://github.com/llvm/llvm-project/pull/122742 we will start attaching
DW_AT_object_pointer to method declarations (in addition to definitions).
Currently when LLDB parses a `DW_TAG_subprogram` defini
@@ -401,12 +399,28 @@ static CompilerContext GetContextEntry(DWARFDIE die) {
return ctx(CompilerContextKind::Typedef);
case DW_TAG_base_type:
return ctx(CompilerContextKind::Builtin);
+ case DW_TAG_class_type:
+ case DW_TAG_structure_type:
+ case DW_TAG_union_type:
@@ -377,7 +377,12 @@ ParsedDWARFTypeAttributes::ParsedDWARFTypeAttributes(const
DWARFDIE &die) {
break;
case DW_AT_object_pointer:
- object_pointer = form_value.Reference();
+ // GetAttributes follows DW_AT_specification.
+ // DW_TAG_subprogram defini
https://github.com/Jlalond updated
https://github.com/llvm/llvm-project/pull/122541
>From 5a756db04b1e5124b99fa44c162439fbf8385aee Mon Sep 17 00:00:00 2001
From: Jacob Lalonde
Date: Fri, 10 Jan 2025 14:26:10 -0800
Subject: [PATCH 1/8] Make the thread list for SBSaveCoreOptions iterable
---
ll
@@ -377,7 +377,12 @@ ParsedDWARFTypeAttributes::ParsedDWARFTypeAttributes(const
DWARFDIE &die) {
break;
case DW_AT_object_pointer:
- object_pointer = form_value.Reference();
+ // GetAttributes follows DW_AT_specification.
+ // DW_TAG_subprogram defini
https://github.com/jimingham approved this pull request.
That looks better. The one functional change - not telling a bunch of threads
to set themselves up for running when we know they aren't going to get to run -
is better behavior, and I can't see how it would cause problems.
https://githu
@@ -859,7 +859,9 @@ SBError SBThread::StepOverUntil(lldb::SBFrame &sb_frame,
addr_t step_addr =
sc.line_entry.range.GetBaseAddress().GetLoadAddress(target);
if (step_addr != LLDB_INVALID_ADDRESS) {
-if (fun_range.ContainsLoadAddress(step_addr, targ
ldionne wrote:
IIUC, the build that encountered issues in this patch ([in the comment
above](https://github.com/llvm/llvm-project/pull/115380#issuecomment-2590801533))
is a flavour of (2), right? That seems surprising to me though since we also
use the same flags when configuring libc++:
http
rocallahan wrote:
Great, thanks! Hopefully someone can merge this?
https://github.com/llvm/llvm-project/pull/120817
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,134 @@
+import lldb
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test import lldbutil
+
+
+class StepUntilTestCase(TestBase):
jimingham wrote:
Do you need to rename this? It's the same as the test cla
vitalybuka wrote:
> IIUC, the build that encountered issues in this patch ([in the comment
> above](https://github.com/llvm/llvm-project/pull/115380#issuecomment-2590801533))
> is a flavour of (2), right? That seems surprising to me though since we also
> use the same flags when configuring li
arichardson wrote:
> IIUC, the build that encountered issues in this patch ([in the comment
> above](https://github.com/llvm/llvm-project/pull/115380#issuecomment-2590801533))
> is a flavour of (2), right? That seems surprising to me though since we also
> use the same flags when configuring l
@@ -5,6 +5,13 @@ struct Outer {
struct Inner {};
};
+namespace NS {
+namespace {
+template struct Struct {};
+} // namespace
+} // namespace NS
+
int main() {
Outer::Inner oi;
+ NS::Struct ns_struct;
Michael137 wrote:
Just for test completeness, could
https://github.com/Michael137 approved this pull request.
https://github.com/llvm/llvm-project/pull/123054
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -376,7 +378,8 @@ lldb_private::Type *DWARFDIE::ResolveTypeUID(const DWARFDIE
&die) const {
return nullptr;
}
-static CompilerContext GetContextEntry(DWARFDIE die) {
+static CompilerContext GetContextEntry(DWARFDIE die,
+ bool complet
@@ -401,12 +399,28 @@ static CompilerContext GetContextEntry(DWARFDIE die) {
return ctx(CompilerContextKind::Typedef);
case DW_TAG_base_type:
return ctx(CompilerContextKind::Builtin);
+ case DW_TAG_class_type:
+ case DW_TAG_structure_type:
+ case DW_TAG_union_type:
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123054
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123054
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123054
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123054
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/123054
>From 1aff68c333c9a12a4b67cca717eba6d96d4afb5a Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Wed, 20 Nov 2024 14:37:37 +0100
Subject: [PATCH 1/3] [lldb] Fix lookup of types in anonymous namespaces with
-gsim
Author: Brad Smith
Date: 2025-01-15T11:03:33-05:00
New Revision: 3986cffe81128061b774c06d0ba42ff7340f2d76
URL:
https://github.com/llvm/llvm-project/commit/3986cffe81128061b774c06d0ba42ff7340f2d76
DIFF:
https://github.com/llvm/llvm-project/commit/3986cffe81128061b774c06d0ba42ff7340f2d76.diff
LO
https://github.com/brad0 closed https://github.com/llvm/llvm-project/pull/123005
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -376,7 +378,8 @@ lldb_private::Type *DWARFDIE::ResolveTypeUID(const DWARFDIE
&die) const {
return nullptr;
}
-static CompilerContext GetContextEntry(DWARFDIE die) {
+static CompilerContext GetContextEntry(DWARFDIE die,
+ bool complet
@@ -401,12 +399,28 @@ static CompilerContext GetContextEntry(DWARFDIE die) {
return ctx(CompilerContextKind::Typedef);
case DW_TAG_base_type:
return ctx(CompilerContextKind::Builtin);
+ case DW_TAG_class_type:
+ case DW_TAG_structure_type:
+ case DW_TAG_union_type:
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jonas Devlieghere (JDevlieghere)
Changes
A bit or byte size of 0 is not a bug. It can legitimately (and frequently)
happen in Swift and C, just not in C++. However, it doesn't make sense to read
a scalar of zero bytes.
Currently, when thi
labath wrote:
This looks like some sort of a problem with the test infrastructure. It thinks
the test "passed unexpectedly" even though it has no "expected failure"
annotations and the test itself reports it succeeded.
https://github.com/llvm/llvm-project/pull/122358
__
@@ -377,7 +377,12 @@ ParsedDWARFTypeAttributes::ParsedDWARFTypeAttributes(const
DWARFDIE &die) {
break;
case DW_AT_object_pointer:
- object_pointer = form_value.Reference();
+ // GetAttributes follows DW_AT_specification.
+ // DW_TAG_subprogram defini
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/123089
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
jimingham wrote:
LGTM modulo the couple little niggles. Thanks for the extra testing!
https://github.com/llvm/llvm-project/pull/123046
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-comm
arichardson wrote:
> https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
It looks like
https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
tries to run `ninja c
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -511,22 +513,58 @@ ValueObjectSP
StackFrame::GetValueForVariableExpressionPath(
VariableSP &var_sp, Status &error) {
ExecutionContext exe_ctx;
CalculateExecutionContext(exe_ctx);
+
bool use_DIL = exe_ctx.GetTargetRef().GetUseDIL(&exe_ctx);
+
if (use_DIL)
@@ -0,0 +1,62 @@
+//===-- DILEval.h ---*- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apa
@@ -0,0 +1,161 @@
+//===-- DILAST.h *- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
arichardson wrote:
> > > https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
> >
> >
> > It looks like
> > https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
>
vitalybuka wrote:
> > https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
>
> It looks like
> https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/sanitizer_common/symbolizer/scripts/build_symbolizer.sh
> tries to run
https://github.com/JDevlieghere created
https://github.com/llvm/llvm-project/pull/123107
A bit or byte size of 0 is not a bug. It can legitimately (and frequently)
happen in Swift and C, just not in C++. However, it doesn't make sense to read
a scalar of zero bytes.
Currently, when this happe
@@ -0,0 +1,166 @@
+//===-- DILLexer.h --*- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,117 @@
+//===-- DILEval.cpp
---===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,191 @@
+//===-- DILLexer.cpp
--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
@@ -0,0 +1,191 @@
+//===-- DILLexer.cpp
--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
1 - 100 of 115 matches
Mail list logo
