@@ -0,0 +1,101 @@
+//===- LoopLikeInterfaceTest.cpp - Unit tests for Loop Like Interfaces.
---===//
+//
+// 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
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/79924
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -4552,16 +4552,22 @@ struct MemorySanitizerVisitor : public
InstVisitor {
}
if (!ElemTy->isSized())
return;
-Value *SizeVal =
- IRB.CreateTypeSize(MS.IntptrTy, DL.getTypeStoreSize(ElemTy));
+auto Size = DL.getTypeStoreSize(ElemTy);
+Value *Siz
jasonmolenda wrote:
@bulbazord in the most recent commit I moved this internal-only enum from
lldb-enumerations.h to lldb-private-enumerations.h, but I need to use the
constexpr templatey thing that LLDB_MARK_AS_BITMASK_ENUM() defines for the enum
so I can use bit-wise | & operations without c
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/80376
>From 70a518030f2b23ca130a8d0ea667729d7985795c Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 1 Feb 2024 17:46:03 -0800
Subject: [PATCH 1/5] [lldb] Add QSupported key to report watchpoint types
sup
jimingham wrote:
I don't think the C++ or ObjC runtimes would vend their own C language
runtimes. I don't think that would reflect a situation any system has
(different C runtimes for C++ and ObjC). Rather these would just be three
independent plugin instances.
Jim
> On Feb 2, 2024, at 3:5
@@ -1089,9 +1089,9 @@ void SBDebugger::SetSelectedTarget(SBTarget &sb_target) {
Log *log = GetLog(LLDBLog::API);
TargetSP target_sp(sb_target.GetSP());
- if (m_opaque_sp) {
+ if (m_opaque_sp && target_sp)
m_opaque_sp->GetTargetList().SetSelectedTarget(target_sp);
--
@@ -0,0 +1,85 @@
+#include "lldb/Target/VerboseTrapFrameRecognizer.h"
+
+#include "lldb/Core/Module.h"
+#include "lldb/Symbol/Function.h"
+#include "lldb/Symbol/SymbolContext.h"
+#include "lldb/Target/Process.h"
+#include "lldb/Target/Target.h"
+
+#include "lldb/Utility/LLDBLog.h"
@@ -0,0 +1,9 @@
+# RUN: %clang_host -g -O0 %S/Inputs/verbose_trap.cpp -o %t.out
+# RUN: %lldb -b -s %s %t.out | FileCheck %s
+run
+# CHECK: thread #{{.*}}stop reason = __llvm_verbose_trap: Function is not
implemented
adrian-prantl wrote:
Should we hide the `__ll
adrian-prantl wrote:
What will happen in an Objective-C++ frame then? Will there be two C runtimes
because we have both a C++ and an ObjC runtime?
https://github.com/llvm/llvm-project/pull/80368
___
lldb-commits mailing list
lldb-commits@lists.llvm.or
@@ -1089,9 +1089,9 @@ void SBDebugger::SetSelectedTarget(SBTarget &sb_target) {
Log *log = GetLog(LLDBLog::API);
TargetSP target_sp(sb_target.GetSP());
- if (m_opaque_sp) {
+ if (m_opaque_sp && target_sp)
jimingham wrote:
Do we also want to check target
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Greg Clayton (clayborg)
Changes
A user found a crash when they would do code like: (lldb) script
>>> target = lldb.SBTarget()
>>> lldb.debugger.SetSelectedTarget(target)
We were not checking if the target was valid in
SBDebugger::SetSelect
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/80508
A user found a crash when they would do code like: (lldb) script
>>> target = lldb.SBTarget()
>>> lldb.debugger.SetSelectedTarget(target)
We were not checking if the target was valid in
SBDebugger::SetSelectedT
https://github.com/ZijunZhaoCCK updated
https://github.com/llvm/llvm-project/pull/78655
>From f440f44e7e270d4636ad39f4e4223c904e496d3a Mon Sep 17 00:00:00 2001
From: zijunzhao
Date: Fri, 19 Jan 2024 00:47:05 +
Subject: [PATCH 1/8] Make clang report invalid target versions for all
environme
https://github.com/ZijunZhaoCCK updated
https://github.com/llvm/llvm-project/pull/78655
>From f440f44e7e270d4636ad39f4e4223c904e496d3a Mon Sep 17 00:00:00 2001
From: zijunzhao
Date: Fri, 19 Jan 2024 00:47:05 +
Subject: [PATCH 1/7] Make clang report invalid target versions for all
environme
https://github.com/ZijunZhaoCCK updated
https://github.com/llvm/llvm-project/pull/78655
>From f440f44e7e270d4636ad39f4e4223c904e496d3a Mon Sep 17 00:00:00 2001
From: zijunzhao
Date: Fri, 19 Jan 2024 00:47:05 +
Subject: [PATCH 1/7] Make clang report invalid target versions for all
environme
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread edited https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -220,6 +220,31 @@ def LoopLikeOpInterface :
OpInterface<"LoopLikeOpInterface"> {
/*defaultImplementation=*/[{
return ::mlir::failure();
}]
+>,
+InterfaceMethod<[{
+Add a zero-trip-check around the loop to check if the loop body is ever
--
@@ -4552,16 +4552,22 @@ struct MemorySanitizerVisitor : public
InstVisitor {
}
if (!ElemTy->isSized())
return;
-Value *SizeVal =
- IRB.CreateTypeSize(MS.IntptrTy, DL.getTypeStoreSize(ElemTy));
+auto Size = DL.getTypeStoreSize(ElemTy);
+Value *Siz
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/80376
>From 70a518030f2b23ca130a8d0ea667729d7985795c Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 1 Feb 2024 17:46:03 -0800
Subject: [PATCH 1/4] [lldb] Add QSupported key to report watchpoint types
sup
@@ -220,6 +220,31 @@ def LoopLikeOpInterface :
OpInterface<"LoopLikeOpInterface"> {
/*defaultImplementation=*/[{
return ::mlir::failure();
}]
+>,
+InterfaceMethod<[{
+Add a zero-trip-check around the loop to check if the loop body is ever
+
https://github.com/pirama-arumuga-nainar approved this pull request.
https://github.com/llvm/llvm-project/pull/78655
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ZijunZhaoCCK updated
https://github.com/llvm/llvm-project/pull/78655
>From f440f44e7e270d4636ad39f4e4223c904e496d3a Mon Sep 17 00:00:00 2001
From: zijunzhao
Date: Fri, 19 Jan 2024 00:47:05 +
Subject: [PATCH 1/7] Make clang report invalid target versions for all
environme
https://github.com/ZijunZhaoCCK updated
https://github.com/llvm/llvm-project/pull/78655
>From f440f44e7e270d4636ad39f4e4223c904e496d3a Mon Sep 17 00:00:00 2001
From: zijunzhao
Date: Fri, 19 Jan 2024 00:47:05 +
Subject: [PATCH 1/6] Make clang report invalid target versions for all
environme
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH 1/2] [CMAKE] Enable FatLTO as a build option for LLVM
---
clang/cma
https://github.com/ZijunZhaoCCK edited
https://github.com/llvm/llvm-project/pull/78655
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH 1/2] [CMAKE] Enable FatLTO as a build option for LLVM
---
clang/cma
@@ -1251,6 +1253,10 @@ elseif(LLVM_ENABLE_LTO)
endif()
endif()
+if(LLVM_ENABLE_FATLTO AND (FUCHSIA OR UNIX))
+append("-ffat-lto-objects" CMAKE_EXE_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS)
ilovepi wrote:
Dang, I thought I had done that. That's probably w
@@ -1251,6 +1253,10 @@ elseif(LLVM_ENABLE_LTO)
endif()
endif()
+if(LLVM_ENABLE_FATLTO AND (FUCHSIA OR UNIX))
+append("-ffat-lto-objects" CMAKE_EXE_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS)
petrhosek wrote:
I think you also need to append this flag to `CM
ilovepi wrote:
This speeds up a 2 stage build by about 3 minutes, tests time are still much
closer than expected. Locally I saw a bout a 5-8% speedup to build clang unit
tests, but maybe the unit tests are too small in the overall test regime to
make a difference.
I'll try to collect more per
krzysz00 wrote:
@piotrAMD Thanks for the thorough testing! I found the issue (stale pointer)
and your code also gave me an unrelated crash, namely that I wasn't correctly
handling unreachable intrinssics.
https://github.com/llvm/llvm-project/pull/77952
_
@@ -1219,8 +1222,25 @@ VersionTuple Triple::getEnvironmentVersion() const {
StringRef Triple::getEnvironmentVersionString() const {
StringRef EnvironmentName = getEnvironmentName();
+
+ // none is a valid environment type - it basically amounts to a freestanding
+ // envir
https://github.com/MaskRay approved this pull request.
A better title may be:
[Driver] Report invalid target triple versions for all environment types.
"Driver" is better than "clang" as it is specific about where the error arises.
https://github.com/llvm/llvm-project/pull/78655
__
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/78655
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Paul Kirth (ilovepi)
Changes
Since LLVM supports `-ffat-lto-objects` we should enable this as an option in
the LLVM build. FatLTO should improve the time it takes to build tests for LTO
enabled builds of the compiler by not linking w/ the
https://github.com/ilovepi ready_for_review
https://github.com/llvm/llvm-project/pull/80480
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -220,6 +220,31 @@ def LoopLikeOpInterface :
OpInterface<"LoopLikeOpInterface"> {
/*defaultImplementation=*/[{
return ::mlir::failure();
}]
+>,
+InterfaceMethod<[{
+Add a zero-trip-check around the loop to check if the loop body is ever
+
@@ -220,6 +220,31 @@ def LoopLikeOpInterface :
OpInterface<"LoopLikeOpInterface"> {
/*defaultImplementation=*/[{
return ::mlir::failure();
}]
+>,
+InterfaceMethod<[{
+Add a zero-trip-check around the loop to check if the loop body is ever
--
Author: David Blaikie
Date: 2024-02-02T20:01:51Z
New Revision: f6b387589d648945372528a4ac77c58f310e5165
URL:
https://github.com/llvm/llvm-project/commit/f6b387589d648945372528a4ac77c58f310e5165
DIFF:
https://github.com/llvm/llvm-project/commit/f6b387589d648945372528a4ac77c58f310e5165.diff
LOG:
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH] [CMAKE] Enable FatLTO as a build option for LLVM
---
clang/cmake/c
https://github.com/jasonmolenda updated
https://github.com/llvm/llvm-project/pull/80376
>From 70a518030f2b23ca130a8d0ea667729d7985795c Mon Sep 17 00:00:00 2001
From: Jason Molenda
Date: Thu, 1 Feb 2024 17:46:03 -0800
Subject: [PATCH 1/3] [lldb] Add QSupported key to report watchpoint types
sup
jasonmolenda wrote:
> Just to record that I thought about it, I agree with not trying to make the
> names architecture neutral.
>
> For example one might say that because range watchpoints on mips and aarch64
> have overlapping functionality (no pun intended) that we could report that we
> ha
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -403,6 +403,22 @@ void GDBRemoteCommunicationClient::GetRemoteQSupported() {
x.split(compressions, ',');
if (!compressions.empty())
MaybeEnableCompression(compressions);
+ } else if (x.consume_front("SupportedWatchpointTypes=")) {
+llvm
https://github.com/alexey-bataev updated
https://github.com/llvm/llvm-project/pull/80164
>From cfd0dcfa1f5fabd12cf4d7bf8d5a10bd324ace0a Mon Sep 17 00:00:00 2001
From: Alexey Bataev
Date: Wed, 31 Jan 2024 16:47:49 +
Subject: [PATCH] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20initia?=
@@ -220,6 +220,28 @@ def LoopLikeOpInterface :
OpInterface<"LoopLikeOpInterface"> {
/*defaultImplementation=*/[{
return ::mlir::failure();
}]
+>,
+InterfaceMethod<[{
+Add a zero-trip-check around the loop to check if the loop body is ever
+
https://github.com/pzread updated
https://github.com/llvm/llvm-project/pull/80331
>From 70f54b51bef87bde5e3f5ee067c0f2414d34e915 Mon Sep 17 00:00:00 2001
From: Jerry Wu
Date: Thu, 1 Feb 2024 19:57:26 +
Subject: [PATCH 1/3] Add replaceWithZeroTripCheck to LoopLikeOpInterface
---
.../mlir/I
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
pzread wrote:
> Can you add some tests for this?
Done.
https://github.com/llvm/llvm-project/pull/80331
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/pzread updated
https://github.com/llvm/llvm-project/pull/80331
>From 70f54b51bef87bde5e3f5ee067c0f2414d34e915 Mon Sep 17 00:00:00 2001
From: Jerry Wu
Date: Thu, 1 Feb 2024 19:57:26 +
Subject: [PATCH 1/2] Add replaceWithZeroTripCheck to LoopLikeOpInterface
---
.../mlir/I
paolosevMSFT wrote:
The logic to manage `DW_OP_WASM_location` in `DWARFExpression` is moved to a
separate PR: https://github.com/llvm/llvm-project/pull/78977, which should be
reviewed (and hopefully approved :-)) before we can complete work on this PR>
https://github.com/llvm/llvm-project/pul
paolosevMSFT 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 ?
The idea for this patch w
paolosevMSFT wrote:
> I see, thanks for the clarification. In the patch, the WasmLocal and
> WasmGlobal calls are done in ReadRegister, so it seems like those are being
> presented as register values? `register read` should show them. BTW, we
> shouldn't make a top level `wasm` command, we rea
https://github.com/MaskRay closed
https://github.com/llvm/llvm-project/pull/80255
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/MaskRay updated
https://github.com/llvm/llvm-project/pull/80255
>From 8ce25b59ac48e3b0a69c28e8af3abe6d7cbf0c42 Mon Sep 17 00:00:00 2001
From: Fangrui Song
Date: Wed, 31 Jan 2024 23:25:23 -0800
Subject: [PATCH] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20initia?=
=?UTF
@@ -0,0 +1,27 @@
+// RUN: mlir-translate -mlir-to-llvmir -split-input-file %s | FileCheck %s
+
+// Decoding the attribute does not work on big-endian platforms currently
+// XFAIL: target=s390x-{{.*}}
efriedma-quic wrote:
LLVM tests use "host-byteorder-little-end
jimingham wrote:
I think that makes the most sense.
Jim
> On Feb 2, 2024, at 1:45 AM, Michael Buch ***@***.***> wrote:
>
>
> The patch looks fine to me, but I'm a bit bugged by the fact that it is in
> Target. In my mind, this is part of the C LanguageRuntime, except we don't
> yet have a C
paolosevMSFT wrote:
> > But currently a simple gdb-remote [:] does not enable the "wasm' plugin. Is
> > there a way to detect that we are debugging WebAssembly at connect time?
>
> Tracing down from `platform connect `, I get to
> `Process::FindPlugin`, which creates a process of all the regis
https://github.com/paolosevMSFT reopened
https://github.com/llvm/llvm-project/pull/77949
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/paolosevMSFT closed
https://github.com/llvm/llvm-project/pull/77949
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
paolosevMSFT wrote:
> might be a noobie question, but is compatible with split dwarf ?
Yes, it is :-).
For that to work, it expects that the Wasm module contains a custom section
named `.external_debug_info` that contains the path to another Wasm module that
contains the DWARF symbols section
https://github.com/Fznamznon updated
https://github.com/llvm/llvm-project/pull/73099
>From 1d70b7726e7d1f11622a6d5c8246b0737e024c8d Mon Sep 17 00:00:00 2001
From: "Podchishchaeva, Mariya"
Date: Tue, 19 Sep 2023 08:37:18 -0700
Subject: [PATCH 01/10] [C23] Implement N3018: The constexpr specifier
https://github.com/Bryce-MW updated
https://github.com/llvm/llvm-project/pull/77964
>From d4c312b9dbf447d0a53dda0e6cdc482bd908430b Mon Sep 17 00:00:00 2001
From: Bryce Wilson
Date: Fri, 12 Jan 2024 16:01:32 -0600
Subject: [PATCH 01/16] [X86] Use RORX over SHR imm
---
llvm/lib/Target/X86/X86In
Bryce-MW wrote:
I spent some time trying out something much more complex: starting at the user
of flags that has other inputs (ADC, SBB, CMOVcc are the main ones), trace back
the non-flags inputs to see if the node producing the flags inputs is along
their paths then check the path from there
https://github.com/Bryce-MW ready_for_review
https://github.com/llvm/llvm-project/pull/77964
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Just to record that I thought about it, I agree with not trying to make the
names architecture neutral.
For example one might say that because range watchpoints on mips and aarch64
have overlapping functionality (no pun intended) that we could report that we
have "range"
@@ -403,6 +403,22 @@ void GDBRemoteCommunicationClient::GetRemoteQSupported() {
x.split(compressions, ',');
if (!compressions.empty())
MaybeEnableCompression(compressions);
+ } else if (x.consume_front("SupportedWatchpointTypes=")) {
+llvm
@@ -403,6 +403,22 @@ void GDBRemoteCommunicationClient::GetRemoteQSupported() {
x.split(compressions, ',');
if (!compressions.empty())
MaybeEnableCompression(compressions);
+ } else if (x.consume_front("SupportedWatchpointTypes=")) {
+llvm
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
@@ -38,7 +38,44 @@ read packet: +
read packet: $OK#9a
send packet: +
+//--
+// "QSupported"
+//
+// BRIEF
+// Query the GDB remote server for features it supports
+//
+// PRIORITY TO IMPLEMENT
+// Optional.
Fznamznon wrote:
Ping.
https://github.com/llvm/llvm-project/pull/73099
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
eaeltsin wrote:
> #80050 opened. Nevertheless, a reproducer for future work would be
> appreciated.
I'm running a reduction, but it progresses extremely slowly. Will post as soon
as it converges to something meaningful (or I'll get some time to reduce the
test case by hand).
https://github.
Michael137 wrote:
> The patch looks fine to me, but I'm a bit bugged by the fact that it is in
> Target. In my mind, this is part of the C LanguageRuntime, except we don't
> yet have a C Language Runtime... But in any case, somewhere more specific
> than Target.
Seems reasonable to me. Should
https://github.com/dstutt updated
https://github.com/llvm/llvm-project/pull/67104
>From 259138920126f09149b488fc54e8d2a7da969ca4 Mon Sep 17 00:00:00 2001
From: David Stuttard
Date: Thu, 24 Aug 2023 16:45:50 +0100
Subject: [PATCH 1/4] [AMDGPU] Add pal metadata 3.0 support to callable pal
funcs
https://github.com/joker-eph closed
https://github.com/llvm/llvm-project/pull/80246
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
85 matches
Mail list logo
