github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff 22764918b5c1496970ab6bb1547535c554a06347
374784cbaaffe9ca2bac716c996485783b959364 --
https://github.com/kpdev updated https://github.com/llvm/llvm-project/pull/67782
>From 374784cbaaffe9ca2bac716c996485783b959364 Mon Sep 17 00:00:00 2001
From: Pavel Kosov
Date: Tue, 23 Jan 2024 09:37:54 +0300
Subject: [PATCH] [LLDB] Add ability to update string during debugging
This is the
MaskRay wrote:
This PR needs a rebase.. There are quite a few merge commits. Hmm, I don't know
how to squash the changes to rebase them to latest main branch. `git rebase
--keep-base -i main` has quite a few merge conflicts.
(My lld change
DianQK wrote:
Thanks for the fix! I'll merge the blocked patches in a later two days.
https://github.com/llvm/llvm-project/pull/69498
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
bulbazord wrote:
I thought about this more and talked with Jim offline. I think that it makes
sense for Broadcaster to create Events with the event_type and the EventDataSP.
I'm going to switch my approach and abandon this one.
https://github.com/llvm/llvm-project/pull/79064
https://github.com/bulbazord closed
https://github.com/llvm/llvm-project/pull/79064
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ldionne updated
https://github.com/llvm/llvm-project/pull/69498
>From 6f89b118ed56ad7a3af1996e19ccd30cc893c51e Mon Sep 17 00:00:00 2001
From: Louis Dionne
Date: Wed, 14 Jun 2023 17:49:22 -0700
Subject: [PATCH 01/11] [libc++] Fix the behavior of throwing `operator new`
under
@@ -89,8 +89,8 @@ RISCVTargetLowering::RISCVTargetLowering(const TargetMachine
,
if ((ABI == RISCVABI::ABI_ILP32F || ABI == RISCVABI::ABI_LP64F) &&
!Subtarget.hasStdExtF()) {
errs() << "Hard-float 'f' ABI can't be used for a target that "
-"doesn't
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/66915
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ilovepi wrote:
@topperc Is there anything else you think needs to be done for the code
generation?
https://github.com/llvm/llvm-project/pull/66915
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/zahiraam closed
https://github.com/llvm/llvm-project/pull/78330
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/zahiraam edited
https://github.com/llvm/llvm-project/pull/78330
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -135,14 +135,14 @@ void
Thumb1InstrInfo::loadRegFromStackSlot(MachineBasicBlock ,
void Thumb1InstrInfo::expandLoadStackGuard(
MachineBasicBlock::iterator MI) const {
MachineFunction = *MI->getParent()->getParent();
- const TargetMachine = MF.getTarget();
const
Mirko =?utf-8?q?Brkušanin?= ,
Mirko =?utf-8?q?Brkušanin?=
Message-ID:
In-Reply-To:
@@ -305,6 +305,11 @@ class VOP3OpSel_gfx10 op, VOPProfile p> :
VOP3e_gfx10 {
class VOP3OpSel_gfx11_gfx12 op, VOPProfile p> : VOP3OpSel_gfx10;
+class VOP3FP8OpSel_gfx11_gfx12 op, VOPProfile
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Alex Langford (bulbazord)
Changes
Instead of passing the data to BroadcastEventIfUnique to create an Event object
on the behalf of the caller, the caller can create the Event up-front.
---
Full diff:
https://github.com/bulbazord created
https://github.com/llvm/llvm-project/pull/79045
Instead of passing the data to BroadcastEventIfUnique to create an Event object
on the behalf of the caller, the caller can create the Event up-front.
>From 9cb80e3f334d3cf3dafed4bda6f87289ad330054 Mon Sep 17
MaskRay wrote:
> (the commit message seems odd; intentional?)
Hopefully clarified:)
https://github.com/llvm/llvm-project/pull/78950
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -135,14 +135,15 @@ void
Thumb1InstrInfo::loadRegFromStackSlot(MachineBasicBlock ,
void Thumb1InstrInfo::expandLoadStackGuard(
MachineBasicBlock::iterator MI) const {
MachineFunction = *MI->getParent()->getParent();
- const TargetMachine = MF.getTarget();
const
https://github.com/MaskRay updated
https://github.com/llvm/llvm-project/pull/78950
>From 2ce57488682873d2dc005144db57fbb555f29d8a Mon Sep 17 00:00:00 2001
From: Fangrui Song
Date: Mon, 22 Jan 2024 00:29:09 -0800
Subject: [PATCH] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20initia?=
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/78950
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
JDevlieghere wrote:
Is it possible to write a test for this in `DWARFExpressionTest.cpp`?
https://github.com/llvm/llvm-project/pull/78977
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/mordante closed
https://github.com/llvm/llvm-project/pull/78609
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Mark de Wever
Date: 2024-01-22T20:25:14+01:00
New Revision: bfd12f39b16e7ba2c342e120b925499f8504f5b3
URL:
https://github.com/llvm/llvm-project/commit/bfd12f39b16e7ba2c342e120b925499f8504f5b3
DIFF:
https://github.com/llvm/llvm-project/commit/bfd12f39b16e7ba2c342e120b925499f8504f5b3.diff
https://github.com/mordante updated
https://github.com/llvm/llvm-project/pull/78609
>From 31a7604f872116521558dcb9f1b4c2c4f5f9d439 Mon Sep 17 00:00:00 2001
From: Mark de Wever
Date: Thu, 18 Jan 2024 19:21:09 +0100
Subject: [PATCH 1/2] [lldb][libc++] Adds system_clock data formatters.
---
@@ -32,6 +32,106 @@ def test_with_run_command(self):
self.expect("frame variable m", substrs=["m = 4321 months"])
self.expect("frame variable y", substrs=["y = 321 years"])
+self.expect(
+"frame variable ss_tp",
+substrs=["ss_tp
@@ -1073,18 +1073,79 @@ bool
lldb_private::formatters::LibcxxWStringViewSummaryProvider(
bool success;
ValueObjectSP dataobj;
size_t size;
- std::tie( success, dataobj, size ) = LibcxxExtractStringViewData(valobj);
+ std::tie(success, dataobj, size) =
H-G-Hristov wrote:
> This is still broken so I'm going to revert the change.
Thanks! Sorry for the inconvenience. I didn't see your message earlier.
https://github.com/llvm/llvm-project/pull/76449
___
lldb-commits mailing list
https://github.com/clayborg closed
https://github.com/llvm/llvm-project/pull/78605
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Kevin Frei
Date: 2024-01-22T11:09:48-08:00
New Revision: 6d5f8d3e6e473a6890f232dba8b14b7b46140558
URL:
https://github.com/llvm/llvm-project/commit/6d5f8d3e6e473a6890f232dba8b14b7b46140558
DIFF:
https://github.com/llvm/llvm-project/commit/6d5f8d3e6e473a6890f232dba8b14b7b46140558.diff
https://github.com/ldionne updated
https://github.com/llvm/llvm-project/pull/69498
>From 6f89b118ed56ad7a3af1996e19ccd30cc893c51e Mon Sep 17 00:00:00 2001
From: Louis Dionne
Date: Wed, 14 Jun 2023 17:49:22 -0700
Subject: [PATCH 1/8] [libc++] Fix the behavior of throwing `operator new`
under
https://github.com/andykaylor approved this pull request.
lgtm
https://github.com/llvm/llvm-project/pull/78330
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/bulbazord closed
https://github.com/llvm/llvm-project/pull/78773
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Alex Langford
Date: 2024-01-22T10:46:20-08:00
New Revision: 0cea54a382f3187acbe3e81bd0fd7cf2cb1077b8
URL:
https://github.com/llvm/llvm-project/commit/0cea54a382f3187acbe3e81bd0fd7cf2cb1077b8
DIFF:
https://github.com/llvm/llvm-project/commit/0cea54a382f3187acbe3e81bd0fd7cf2cb1077b8.diff
kevinfrei wrote:
Sure. That's probably the solution. I just can't get a reliable repro, so I can
only validate that it doesn't break the mainstream monorepo build. I'm happy to
shepherd any diff you've indicated can tell me it's fixed on your configuration.
I truly appreciate the different
https://github.com/Michael137 approved this pull request.
LGTM (with minor questions)
https://github.com/llvm/llvm-project/pull/78609
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
@@ -32,6 +32,106 @@ def test_with_run_command(self):
self.expect("frame variable m", substrs=["m = 4321 months"])
self.expect("frame variable y", substrs=["y = 321 years"])
+self.expect(
+"frame variable ss_tp",
+substrs=["ss_tp
@@ -1073,18 +1073,79 @@ bool
lldb_private::formatters::LibcxxWStringViewSummaryProvider(
bool success;
ValueObjectSP dataobj;
size_t size;
- std::tie( success, dataobj, size ) = LibcxxExtractStringViewData(valobj);
+ std::tie(success, dataobj, size) =
@@ -0,0 +1,14 @@
+# REQUIRES: x86
+# RUN: mkdir -p %t
+# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin %p/Inputs/libhello.s
-o %t/hello.o
+# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin %s -o %t/main.o
+# RUN: %lld -L %t %t/main.o %t/hello.o -o %t/a.out
jimingham wrote:
Not sure what you mean by this. "frame var" and "target var" are the lldb
command line commands for viewing local and global variables respectively. Why
are these not appropriate for Wasm?
Jim
> On Jan 22, 2024, at 6:37 AM, Quentin Michaud ***@***.***> wrote:
>
>
>
Mirko =?utf-8?q?Brkušanin?=
Message-ID:
In-Reply-To:
@@ -305,6 +305,11 @@ class VOP3OpSel_gfx10 op, VOPProfile p> :
VOP3e_gfx10 {
class VOP3OpSel_gfx11_gfx12 op, VOPProfile p> : VOP3OpSel_gfx10;
+class VOP3FP8OpSel_gfx11_gfx12 op, VOPProfile p> : VOP3e_gfx10
{
+ let
https://github.com/MaskRay closed
https://github.com/llvm/llvm-project/pull/78944
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -664,7 +674,7 @@ void request_attach(const llvm::json::Object ) {
// Run any initialize LLDB commands the user specified in the launch.json
if (llvm::Error err = g_dap.RunInitCommands()) {
-response["success"] = false;
+ response["success"] = false;
@@ -655,6 +663,8 @@ void request_attach(const llvm::json::Object ) {
g_dap.SetFrameFormat(GetString(arguments, "customFrameFormat"));
g_dap.SetThreadFormat(GetString(arguments, "customThreadFormat"));
+ PrintWelcomeMessage();
walter-erquinigo wrote:
https://github.com/MaskRay updated
https://github.com/llvm/llvm-project/pull/78944
>From a72bbb3ae04c7be90af36d2cd025329d4ef2ab16 Mon Sep 17 00:00:00 2001
From: Fangrui Song
Date: Sun, 21 Jan 2024 22:18:48 -0800
Subject: [PATCH] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20initia?=
@@ -305,6 +305,11 @@ class VOP3OpSel_gfx10 op, VOPProfile p> :
VOP3e_gfx10 {
class VOP3OpSel_gfx11_gfx12 op, VOPProfile p> : VOP3OpSel_gfx10;
+class VOP3FP8OpSel_gfx11_gfx12 op, VOPProfile p> : VOP3e_gfx10
{
+ let Inst{11} = !if(p.HasSrc0, src0_modifiers{2}, 0);
+ let
petrhosek wrote:
This is still broken so I'm going to revert the change.
https://github.com/llvm/llvm-project/pull/76449
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/fhahn updated https://github.com/llvm/llvm-project/pull/78113
>From 36b085f21b76d7bf7c9965a86a09d1cef4fe9329 Mon Sep 17 00:00:00 2001
From: Florian Hahn
Date: Sun, 14 Jan 2024 14:13:08 +
Subject: [PATCH 1/4] [VPlan] Add new VPUniformPerUFRecipe, use for step
truncation.
mariusz-sikora-at-amd wrote:
> > Correct, some of these instructions use opsel[1] which in LLVM in stored in
> > src1_modifiers so a dummy src1 is used.
>
> Why can't we just use `SRCMODS.OP_SEL_1` with src0?
When referring to `SRCMODS.OP_SEL_1` you are referring to `src1_modifier`
(second
https://github.com/zahiraam updated
https://github.com/llvm/llvm-project/pull/78330
>From 8f8917528e30d2ba67f669cfd1a893bc85c21121 Mon Sep 17 00:00:00 2001
From: Ammarguellat
Date: Tue, 16 Jan 2024 11:24:03 -0800
Subject: [PATCH 1/6] Fixed a bug in Smith's algorithm and made sure last
option
https://github.com/AaronBallman approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/78330
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
mh4ck-Thales wrote:
Seems like support for reading Wasm local and global variables is available in
your code, but I don't understand how can one effectively read these variables
from the lldb command line. Maybe adding commands to access these can be useful
?
@@ -0,0 +1,14 @@
+# REQUIRES: x86
+# RUN: mkdir -p %t
+# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin %p/Inputs/libhello.s
-o %t/hello.o
+# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin %s -o %t/main.o
+# RUN: %lld -L %t %t/main.o %t/hello.o -o %t/a.out
https://github.com/mariusz-sikora-at-amd edited
https://github.com/llvm/llvm-project/pull/78414
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -626,11 +629,82 @@ class Cvt_PK_F32_F8_Pat;
-foreach Index = [0, -1] in {
- def : Cvt_PK_F32_F8_Pat;
- def : Cvt_PK_F32_F8_Pat;
+let SubtargetPredicate = isGFX9Only in {
+ foreach Index = [0, -1] in {
+def : Cvt_PK_F32_F8_Pat;
+def : Cvt_PK_F32_F8_Pat;
+ }
+}
+
+
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Paolo Severini (paolosevMSFT)
Changes
Add support for `DW_OP_WASM_location` in `DWARFExpression`.
---
Full diff: https://github.com/llvm/llvm-project/pull/78977.diff
1 Files Affected:
- (modified)
https://github.com/paolosevMSFT created
https://github.com/llvm/llvm-project/pull/78977
Add support for `DW_OP_WASM_location` in `DWARFExpression`.
>From 4bcf2b50123b18752108aad163a059577e360aa6 Mon Sep 17 00:00:00 2001
From: Paolo Severini
Date: Mon, 22 Jan 2024 06:06:56 -0800
Subject:
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan =?utf-8?q?Kokemüller?= ,
Jan
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff f02b7770bb04b88455804b371dba1f44a86b90da
db0bc4829b02aedf7a988824b38b56a1564a8125 --
https://github.com/paolosevMSFT updated
https://github.com/llvm/llvm-project/pull/77949
>From 30d932bb0988e1c78c3e023be2270259df5e6664 Mon Sep 17 00:00:00 2001
From: Paolo Severini
Date: Fri, 12 Jan 2024 09:10:59 -0800
Subject: [PATCH 1/3] Add support for source-level debugging of WebAssembly
paolosevMSFT wrote:
> > > A WebAssembly debugging session can be started using the new command:
> > > wasm [:]
> >
> >
> > What about wasm requires a new command, given that you are connecting to a
> > GDB server as existing targets do.
>
> +1! I don't think this needs a new command, it
mbrkusanin wrote:
> > Correct, some of these instructions use opsel[1] which in LLVM in stored in
> > src1_modifiers so a dummy src1 is used.
>
> Why can't we just use `SRCMODS.OP_SEL_1` with src0?
That could work. We would have to make custom encoding classes then since
OP_SEL_1 would have
@@ -626,11 +629,82 @@ class Cvt_PK_F32_F8_Pat;
-foreach Index = [0, -1] in {
- def : Cvt_PK_F32_F8_Pat;
- def : Cvt_PK_F32_F8_Pat;
+let SubtargetPredicate = isGFX9Only in {
+ foreach Index = [0, -1] in {
+def : Cvt_PK_F32_F8_Pat;
+def : Cvt_PK_F32_F8_Pat;
+ }
+}
+
+
@@ -0,0 +1,291 @@
+//===-- ProcessWasm.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:
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
f02b7770bb04b88455804b371dba1f44a86b90da...cbd046618749f229fce7221e012bf51f4789301b
https://github.com/paolosevMSFT updated
https://github.com/llvm/llvm-project/pull/77949
>From 30d932bb0988e1c78c3e023be2270259df5e6664 Mon Sep 17 00:00:00 2001
From: Paolo Severini
Date: Fri, 12 Jan 2024 09:10:59 -0800
Subject: [PATCH 1/2] Add support for source-level debugging of WebAssembly
@@ -626,11 +629,82 @@ class Cvt_PK_F32_F8_Pat;
-foreach Index = [0, -1] in {
- def : Cvt_PK_F32_F8_Pat;
- def : Cvt_PK_F32_F8_Pat;
+let SubtargetPredicate = isGFX9Only in {
+ foreach Index = [0, -1] in {
+def : Cvt_PK_F32_F8_Pat;
+def : Cvt_PK_F32_F8_Pat;
+ }
+}
+
+
kosarev wrote:
> Correct, some of these instructions use opsel[1] which in LLVM in stored in
> src1_modifiers so a dummy src1 is used.
Why can't we just use `SRCMODS.OP_SEL_1` with src0?
https://github.com/llvm/llvm-project/pull/78414
___
https://github.com/tblah commented:
Flang changes LGTM once CI passes.
https://github.com/llvm/llvm-project/pull/75530
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
mbrkusanin wrote:
> > > Why is so there so much special casing in the assembler/disassembler?
> >
> >
> > I'm not an original author of these change, but from what I understand it
> > is a workaround to handle VOP3 instructions which have a single source but
> > require the use of two bits
mbrkusanin wrote:
> > Why is so there so much special casing in the assembler/disassembler?
>
> I'm not an original author of these change, but from what I understand it is
> a workaround to handle VOP3 instructions which have a single source but
> require the use of two bits from OPSEL.
mariusz-sikora-at-amd wrote:
> Why is so there so much special casing in the assembler/disassembler?
I'm not an original author of these change, but from what I understand it is a
workaround to handle VOP3 instructions which have a single source but require
the use of two bits from OPSEL.
https://github.com/felixkellenbenz updated
https://github.com/llvm/llvm-project/pull/78919
>From bf376afe7bd69fd25a006890b2910f2fd32c191b Mon Sep 17 00:00:00 2001
From: Felix Kellenbenz
Date: Mon, 22 Jan 2024 00:49:21 +0100
Subject: [PATCH 1/2] Make llvm-strip not eat the .gnu_debuglink
felixkellenbenz wrote:
Hey thanks for the review,
I will add a test case in a moment.
That's true, my change only impacts `--strip-all`. I tested `llvm-strip` with
the `--strip-debug` flag and this didn't remove the `.gnu_debuglink` section.
This is also seen when using `GNU strip`.
Here
@@ -664,7 +674,7 @@ void request_attach(const llvm::json::Object ) {
// Run any initialize LLDB commands the user specified in the launch.json
if (llvm::Error err = g_dap.RunInitCommands()) {
-response["success"] = false;
+ response["success"] = false;
=?utf-8?q?José?= L. Junior ,
=?utf-8?q?José?= L. Junior
Message-ID:
In-Reply-To:
https://github.com/DavidSpickett closed
https://github.com/llvm/llvm-project/pull/76112
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
Author: José Lira Junior
Date: 2024-01-22T09:08:42Z
New Revision: 7b925c3edb6297df6bcf87dfcfdfd645f03b5388
URL:
https://github.com/llvm/llvm-project/commit/7b925c3edb6297df6bcf87dfcfdfd645f03b5388
DIFF:
https://github.com/llvm/llvm-project/commit/7b925c3edb6297df6bcf87dfcfdfd645f03b5388.diff
https://github.com/Fznamznon closed
https://github.com/llvm/llvm-project/pull/78316
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Fznamznon wrote:
Driver failure seems unrelated.
https://github.com/llvm/llvm-project/pull/78316
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jh7370 requested changes to this pull request.
Hi, thanks for the contribution.
Please could you add a new lit test case to show that this behaviour works as
intended.
I note that this code as-is only impacts `--strip-all` behaviour. This means
that if you use
https://github.com/arsenm commented:
Why is so there so much special casing in the assembler/disassembler?
https://github.com/llvm/llvm-project/pull/78414
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/felixkellenbenz updated
https://github.com/llvm/llvm-project/pull/78919
>From bf376afe7bd69fd25a006890b2910f2fd32c191b Mon Sep 17 00:00:00 2001
From: Felix Kellenbenz
Date: Mon, 22 Jan 2024 00:49:21 +0100
Subject: [PATCH] Make llvm-strip not eat the .gnu_debuglink section
81 matches
Mail list logo
