philnik777 wrote:
> Please split the PR by subproject to it is easier to review and approve.
Exactly what I was about to say. I don't understand why this happens again and
again though. Maybe we should add some documentation somewhere that
cross-project patches should be split up if it's not s
Author: Muhammad Omair Javaid
Date: 2025-09-01T01:41:05+05:00
New Revision: eef79c8b49aa45458bbaf895603385a7819cc182
URL:
https://github.com/llvm/llvm-project/commit/eef79c8b49aa45458bbaf895603385a7819cc182
DIFF:
https://github.com/llvm/llvm-project/commit/eef79c8b49aa45458bbaf895603385a7819cc1
https://github.com/clementval commented:
Please split the PR by subproject to it is easier to review and approve.
https://github.com/llvm/llvm-project/pull/156270
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
llvmbot wrote:
@llvm/pr-subscribers-clang-tidy
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. The
@@ -427,7 +427,11 @@ void IRNormalizer::reorderInstructions(Function &F) const {
// Process the remaining instructions.
//
// TODO: Do more a intelligent sorting of these instructions. For
example,
+<<< Updated upstream
// separate between dead ins
@@ -741,7 +741,7 @@ const char *UnicodeNameToCodepointDict =
"GLOVETED PLANT OF PAPERCUBE ROOTPIDERY HAT OF MEATFISH TAILZENE RINGITRA "
"SIGN OVER BALCRESCENDO PLUS SAGT ON BONEFINAL NUN PLUS TUR PLUS ZA7FINAL "
"NGAFINAL MEMPANYANGGAAISED DOTLOWER DOTATTACHED PLU
llvmbot wrote:
@llvm/pr-subscribers-backend-x86
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. Th
llvmbot wrote:
@llvm/pr-subscribers-mlir-llvm
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. Thes
llvmbot wrote:
@llvm/pr-subscribers-backend-spir-v
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project.
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. These ch
llvmbot wrote:
@llvm/pr-subscribers-libc
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. These cha
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
llvmbot wrote:
@llvm/pr-subscribers-backend-aarch64
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project
llvmbot wrote:
@llvm/pr-subscribers-clang-format
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. T
llvmbot wrote:
@llvm/pr-subscribers-clang-static-analyzer-1
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the
llvmbot wrote:
@llvm/pr-subscribers-libcxx
Author: Austin Jiang (AustinBoyuJiang)
Changes
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. These c
https://github.com/AustinBoyuJiang created
https://github.com/llvm/llvm-project/pull/156270
Corrected various spelling mistakes such as 'occurred', 'receiver',
'initialized', 'length', and others in comments, variable names, function
names, and documentation throughout the project. These chang
@@ -450,6 +450,20 @@ def disassemble(self, threadId=None, frameIndex=None):
return disassembled_instructions,
disassembled_instructions[memoryReference]
+def dapCleanup(self, disconnectAutomatically):
+if disconnectAutomatically:
+try:
---
walter-erquinigo wrote:
do you know if destroying the debugger will free the module cache?
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-c
https://github.com/walter-erquinigo approved this pull request.
seems well done
https://github.com/llvm/llvm-project/pull/156131
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,128 @@
+// REQUIRES: lld
+
+// Test that simple types can be found
+// RUN: %build --std=c++20 --nodefaultlib --compiler=clang-cl --arch=64 -o
%t.exe -- %s
+// RUN: lldb-test symbols %t.exe | FileCheck %s
+
+bool *PB;
+bool &RB = *PB;
+bool *&RPB = PB;
+const bool &CRB
@@ -0,0 +1,128 @@
+// REQUIRES: lld
+
+// Test that simple types can be found
+// RUN: %build --std=c++20 --nodefaultlib --arch=64 -o %t.exe -- %s
+// RUN: lldb-test symbols %t.exe | FileCheck %s
+
+bool *PB;
+bool &RB = *PB;
+bool *&RPB = PB;
+const bool &CRB = RB;
+bool *const B
@@ -0,0 +1,128 @@
+// REQUIRES: lld
+
+// Test that simple types can be found
+// RUN: %build --std=c++20 --nodefaultlib --compiler=clang-cl --arch=64 -o
%t.exe -- %s
+// RUN: lldb-test symbols %t.exe | FileCheck %s
+
+bool *PB;
+bool &RB = *PB;
+bool *&RPB = PB;
+const bool &CRB
@@ -0,0 +1,128 @@
+// REQUIRES: lld
+
+// Test that simple types can be found
+// RUN: %build --std=c++20 --nodefaultlib --compiler=clang-cl --arch=64 -o
%t.exe -- %s
+// RUN: lldb-test symbols %t.exe | FileCheck %s
+
+bool *PB;
+bool &RB = *PB;
+bool *&RPB = PB;
+const bool &CRB
@@ -2045,14 +2045,17 @@ TypeSP
SymbolFileNativePDB::CreateTypedef(PdbGlobalSymId id) {
if (!ts)
return nullptr;
- ts->GetNativePDBParser()->GetOrCreateTypedefDecl(id);
+ auto *typedef_decl = ts->GetNativePDBParser()->GetOrCreateTypedefDecl(id);
+
+ CompilerType ct =
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/156250
>From a8c1e427327e64fbb878ffcc57622b420ce28c8f Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Sun, 31 Aug 2025 17:24:02 +0200
Subject: [PATCH 1/2] [LLDB][NativePDB] Use typedef compiler type for typedef
types
--
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: nerix (Nerixyz)
Changes
Before this PR, the native PDB plugin would create the following LLDB `Type`
for `using SomeTypedef = long`:
```
Type{0x2e03} , name = "SomeTypedef", size = 4, compiler_type =
0x02becd8d8620 long
```
with th
https://github.com/Nerixyz created
https://github.com/llvm/llvm-project/pull/156250
Before this PR, the native PDB plugin would create the following LLDB `Type`
for `using SomeTypedef = long`:
```
Type{0x2e03} , name = "SomeTypedef", size = 4, compiler_type =
0x02becd8d8620 long
```
wi
kusmour wrote:
I think this is fine. BTW, do we reset the global settings with lldb-dap server
mode?
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/list
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi edited
https://github.com/llvm/llvm-project/pull/156231
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/royitaqi updated
https://github.com/llvm/llvm-project/pull/156231
>From c35a97fb54dfc046be3bdcde2a6297603aa9b297 Mon Sep 17 00:00:00 2001
From: Roy Shi
Date: Sun, 31 Aug 2025 01:45:23 -0700
Subject: [PATCH] [lldb-dap] Destroy debugger when debug session terminates
---
lldb/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Roy Shi (royitaqi)
Changes
Currently, in Server Mode (i.e. `--connection`), the destroy callbacks of all
debuggers are called at the lldb-dap process's termination. This causes delayed
logging and release of resources. This can also cause
https://github.com/royitaqi created
https://github.com/llvm/llvm-project/pull/156231
Currently, in Server Mode (i.e. `--connection`), the destroy callbacks of all
debuggers are called at the lldb-dap process's termination. This causes delayed
logging and release of resources. This can also cau
@@ -0,0 +1,15 @@
+// This test checks that under implicit modules, different optimization levels
paperchalice wrote:
Is there any reason this test is in `llvm` folder?
https://github.com/llvm/llvm-project/pull/146422
_
37 matches
Mail list logo
