mstorsjo wrote:
> > Right - I see. But why does this build configuration have to affect whether
> > it should build lldb-rpc-gen or not? Is it because the clang in this build
> > can't manage to process the lldb headers (which are built for the current
> > host)?
>
> Right, "the clang in this
mstorsjo wrote:
> @chelcassanova @mstorsjo
>
> > But this seems to assume that everybody's cross builds are done in some
> > specific sequence, with regards to how LLVM_HOST_TRIPLE and
> > LLVM_DEFAULT_TARGET_TRIPLE are set (in my case, I just cross build with one
> > single step, and both of
mstorsjo wrote:
Now I've had time to study lldb-rpc-gen a little bit closer...
For myself and others, to clarify what lldb-rpc-gen does (as how command
options flow into it that aren't immediately obvious): It is a tool that
includes clang tooling libraries. It runs at the regular LLVM/LLDB bu
https://github.com/mstorsjo requested changes to this pull request.
This doesn't yet work as it should.
https://github.com/llvm/llvm-project/pull/151603
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
@@ -326,27 +326,19 @@ endif()
# In a cross-compile build, we need to skip building the generated
# lldb-rpc sources in the first phase of host build so that they can
# get built using the just-built Clang toolchain in the second phase.
-if (NOT DEFINED LLDB_CAN_USE_LLDB_RPC_SER
https://github.com/mstorsjo edited
https://github.com/llvm/llvm-project/pull/151603
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -18,6 +18,11 @@ add_lldb_tool(lldb-rpc-gen
Support
)
-if (NOT DEFINED LLDB_RPC_GEN_EXE)
- set(LLDB_RPC_GEN_EXE $ CACHE STRING "Executable
that generates lldb-rpc-server")
+if (CMAKE_CROSSCOMPILING)
+ setup_host_tool(lldb-rpc-gen LLDB_RPC_GEN_EXE lldb_rpc_gen_exe
@@ -18,6 +18,11 @@ add_lldb_tool(lldb-rpc-gen
Support
)
-if (NOT DEFINED LLDB_RPC_GEN_EXE)
- set(LLDB_RPC_GEN_EXE $ CACHE STRING "Executable
that generates lldb-rpc-server")
+if (CMAKE_CROSSCOMPILING)
+ setup_host_tool(lldb-rpc-gen LLDB_RPC_GEN_EXE lldb_rpc_gen_exe
mstorsjo wrote:
> On some cross compile builds, the tool is not correctly set and the command
> that runs the tool has an empty path for the tool, causing the build to fail.
I'd rather skip the "some" word here, this happens whenever cmake things we're
cross compiling - it's not just an odd ca
mstorsjo wrote:
/cherry-pick 98ec927fcb8697a6f6df64298835917aa1d0d3c1
https://github.com/llvm/llvm-project/pull/150886
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/mstorsjo milestoned
https://github.com/llvm/llvm-project/pull/150886
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/mstorsjo closed
https://github.com/llvm/llvm-project/pull/150886
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
mstorsjo wrote:
Tested that this still silences the warnings, on both 32 and 64 bit.
https://github.com/llvm/llvm-project/pull/150886
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/mstorsjo updated
https://github.com/llvm/llvm-project/pull/150886
From 4ee1be1011c4579325b513f3e7459ac8d0c32a5a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Storsj=C3=B6?=
Date: Mon, 28 Jul 2025 09:27:36 +0300
Subject: [PATCH 1/2] [lldb] [Windows] Silence format string w
mstorsjo wrote:
> Oh but is there a Mingw detail here that means the cast is better?
No, mingw should conform quite closely regarding such details. I just didn't
feel like assuming such details about the type of DWORD, but you're right, and
it should be fine to do that instead. Will update.
h
https://github.com/mstorsjo created
https://github.com/llvm/llvm-project/pull/150886
This fixes the following build warnings in a mingw environment:
../../lldb/source/Host/windows/MainLoopWindows.cpp:226:50: warning: format
specifies type 'int' but the argument has type 'IOObject::Waitable
https://github.com/mstorsjo approved this pull request.
Not sure if this is the best/nicest fix, but it works for unbreaking my builds,
so thanks!
https://github.com/llvm/llvm-project/pull/150699
___
lldb-commits mailing list
lldb-commits@lists.llvm.o
mstorsjo wrote:
Also, another less fatal annoyance: If compiling LLDB with GCC, this now
produces warnings like these:
```
[1/78] Processing file
/home/martin/code/llvm-project/lldb/include/lldb/API/SBAddress.h.
warning: unknown warning option '-Wno-class-memaccess'; did you mean
'-Wno-class-v
https://github.com/mstorsjo approved this pull request.
This fixes compilation on 64 bit mingw for me at least.
https://github.com/llvm/llvm-project/pull/146632
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/ma
mstorsjo wrote:
> They put up #146632 to fix it, if one of you wants to check it works.
Thanks - it looks like that does fix some issues, but it only lets the build
proceed slightly further to hit other errors caused by this patch:
```
../../lldb/source/Host/windows/MainLoopWindows.cpp:120:3: e
mstorsjo wrote:
This broke compilation on mingw (for 64 bit targets, a 32 bit test build is
still pending):
```
../../lldb/source/Host/posix/ConnectionFileDescriptorPosix.cpp:455:29: error:
cast from pointer to smaller type 'lldb::socket_t' (aka 'unsigned int') loses
information
455 | se
mstorsjo wrote:
> truncate the section names, as [sections in PE/COFF executable images can't
> be longer than 8
> bytes](https://learn.microsoft.com/en-us/windows/win32/debug/pe-format#section-table-section-headers).
First off, this probably meant to say "section names can't be longer than 8
https://github.com/mstorsjo approved this pull request.
LGTM
IIRC @petrhosek had commented on this before, and was generally in favour of
it, but I'd still leave it open for a couple days if he wants to comment
further on it.
https://github.com/llvm/llvm-project/pull/138587
__
mstorsjo wrote:
> > Therefore, this situation should only be an issue with older kernels, so
> > perhaps it not something that regular user mode applications should need to
> > worry about (unless specifically wanting to run with older kernels).
>
> I will test this PR with an older kernel as
mstorsjo wrote:
> I rebased this on top of #138783 and adjusted the title and description. Now
> it should be in a good state to push cmake changes for other projects.
The changes look good, but it looks like the changes from #138783 still show up
when viewing the changes; can you check that y
https://github.com/mstorsjo approved this pull request.
LGTM, thanks! I can confirm that this fixes compilation on mingw targets, on
both 32 and 64 bit.
https://github.com/llvm/llvm-project/pull/139711
___
lldb-commits mailing list
lldb-commits@lists.
mstorsjo wrote:
Hi Pavel!
Unfortunately, it seems like this change has broken compilation of LLDB for
mingw, on all architectures. With MSVC and clang-cl, it is broken for 32 bit
platforms, while the issue only shows up as a warning for 64 bit architectures
there.
On 64 bit mingw:
```
llvm-p
mstorsjo wrote:
> Closing this since Docker on macOS simply disabled SME, SVE, etc. I believe
> this is still an issue in theory for users with Linux installed directly on
> M4 hardware but if such a user exists I haven't heard of them.
Wouldn't this still be an issue if running virtualized Li
Author: Martin Storsjö
Date: 2025-04-05T16:55:36+03:00
New Revision: fcead25550bb727215919ecf2dfad17765223c19
URL:
https://github.com/llvm/llvm-project/commit/fcead25550bb727215919ecf2dfad17765223c19
DIFF:
https://github.com/llvm/llvm-project/commit/fcead25550bb727215919ecf2dfad17765223c19.diff
mstorsjo wrote:
> Thanks, for the report, will be fixed by #132551
Thanks for the quick fix, I can confirm that Qt builds fine for me again!
https://github.com/llvm/llvm-project/pull/132401
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
htt
mstorsjo wrote:
This change broke building Qt (tested with 6.8), ending up with errors like
this:
```
qtbase/src/corelib/kernel/qcoreapplication.cpp:2946:78: error: 'this' cannot be
used in a static member function declaration
2946 | : slotObject(std::move(slotObject)), context(co
mstorsjo wrote:
> For the record, this PR was finally re-landed as #126988 after four separate
> commits to address issues found in CI testing when I originally merged this.
FWIW, it looks like my smoke tests are still passing fine after these changes
have been relanded now:
https://github.co
mstorsjo wrote:
> When we decided to allow C++11 usage in lldb I think we opted into requiring
> platforms that have relatively complete support for the C++11 additions. I
> don't think it makes sense to try to limit the use of C++11 to some "minimal
> supported subset".
Yeah, I don’t disagre
mstorsjo wrote:
FYI, this had a small impact on deployability on macOS; I used to build LLVM
with 10.9 as a deployment target, but now get these errors:
```
/Users/runner/work/llvm-mingw/llvm-mingw/llvm-project/lldb/include/lldb/Target/StackFrameList.h:161:16:
error: 'shared_mutex' is unavaila
https://github.com/mstorsjo approved this pull request.
LGTM, this seems reasonable - I guess the new form should match both
`breakpoint 1` and `breakpoint 1.1`.
https://github.com/llvm/llvm-project/pull/115318
___
lldb-commits mailing list
lldb-commi
mstorsjo wrote:
> Interesting. Based on a conversation at the dev meeting, I was under the
> impression that the DIA-based implementation was in worse shape and the
> native one in better shape. I also have a memory of bug reports about PDB
> parsing where originators were asked to check with
mstorsjo wrote:
> Remove `SymbolFilePDB` in favor of always using `SymbolFileNativePDB`. This
> effectively makes `LLDB_USE_NATIVE_PDB_READER` the default. The non-native
> (DIA based) PDB symbol file implementation was unmaintained and known to have
> issues.
While this certainly is true, un
mstorsjo wrote:
> The amount of churn is already pretty high -- please make sure the original
> commit, fixes, and reverts get added to
> https://github.com/llvm/llvm-project/blob/main/.git-blame-ignore-revs. At the
> end of the day, we have a number of tests and files which are sensitive to
mstorsjo wrote:
> > if all tests would have been cleaned up before this
>
> That was most certainly my intention, and I saw green before merging, so I
> must've looked in the wrong place
Ah, right - as we've seen that the CI runner normally only updates an existing
checkout, where changes to
mstorsjo wrote:
> This patch is about respecting local config, which is the exact opposite of
> that suggestion. It would be a way to solve the line-ending issue by fiat,
> not by co-operation, so I'm against it on principle. To be clear I very much
> don't like CRLF, but I also very much don'
mstorsjo wrote:
> I think this is due to a subtly of config. Setting `core.autocrlf` to `false`
> doesn't actually do anything since it's the default.
In Git for Windows, the default actually is `core.autocrlf` set to `true`. When
manually installing, the installer wizard used to ask the user
mstorsjo wrote:
> I must have missed this PR originally. I oppose letting Git change any line
> endings. It always ends like this.
Also just for context - the Clang precommit CI is allegedly still broken,
because those buildbots happened to be restarted when we had these
gitattributes in plac
mstorsjo wrote:
> So if I've read that correctly, `core.autocrlf=false` is a red herring and
> you should really set `core.eol=lf` if you want git to use `lf` on windows.
That perhaps may be the case, but all common docs and all common practices
around this revolve around setting `core.autocrl
mstorsjo wrote:
> > > It's my understanding that text=auto does not override core.autocrlf. As
> > > far as I can tell from the documentation it honours the user's
> > > configuration for core.eol in combination with core.autocrlf - from git
> > > config --help:
>
> > This doesn't match my ex
mstorsjo wrote:
> This seems to have broken precommit CI on Windows:
> https://buildkite.com/llvm-project/github-pull-requests/builds/65#0192a01b-d3ac-44ad-abff-e53ac4a206ab
> all of the failures look related to line endings, and I noticed that I got a
> ton of command line messages of the
mstorsjo wrote:
> > a number of test input files need to be in LF form to work
>
> Which ones?
A whole bunch of them. @AaronBallman's link to
https://buildkite.com/llvm-project/github-pull-requests/builds/65#0192a01b-d3ac-44ad-abff-e53ac4a206ab
shows mostly what I saw. If including `clang
mstorsjo wrote:
This breaks a number of tests on Windows.
Previously, to have tests working on Windows, one would do `git config --global
core.autocrlf false` or similar, before checking out llvm-project - a number of
test input files _need_ to be in LF form to work. This was brought up earlie
mstorsjo wrote:
This causes lots of build time warnings when building with GCC, like this:
```
[271/4090] Building CXX object lib/Obj...akeFiles/LLVMObject.dir/Minidump.cpp.o
In file included from ../include/llvm/Object/Minidump.h:16,
from ../lib/Object/Minidump.cpp:9:
../include
mstorsjo wrote:
I pushed a fix in a81a4b2a7ac2d0b8195bb008b2c0f464cfbda223.
https://github.com/llvm/llvm-project/pull/107968
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Martin Storsjö
Date: 2024-09-12T22:26:02+03:00
New Revision: a81a4b2a7ac2d0b8195bb008b2c0f464cfbda223
URL:
https://github.com/llvm/llvm-project/commit/a81a4b2a7ac2d0b8195bb008b2c0f464cfbda223
DIFF:
https://github.com/llvm/llvm-project/commit/a81a4b2a7ac2d0b8195bb008b2c0f464cfbda223.diff
mstorsjo wrote:
> This broke building in mingw configurations, and possibly a few others as
> well.
>
> The `ReportWarning` function takes a pointer to a `std::once_flag`, while
> this is passing it with a `llvm::once_flag`. In many configurations, these
> are the same type, but in a couple o
mstorsjo wrote:
This broke building in mingw configurations, and possibly a few others as well.
The `ReportWarning` function takes a pointer to a `std::once_flag`, while this
is passing it with a `llvm::once_flag`. In many configurations, these are the
same type, but in a couple ones, they're
mstorsjo wrote:
Thanks for the quick fix!
https://github.com/llvm/llvm-project/pull/107388
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
mstorsjo wrote:
> Oops, I copied `shared_fd_t` from #104238 by mistake
>
> ```
> Status GDBRemoteCommunication::StartDebugserverProcess(... , shared_fd_t
> pass_comm_fd) {
> ```
>
> It will break the Windows build. I can replace it with `int` or we can apply
> #107553. Please advise.
As some
mstorsjo wrote:
> > FYI, I also ran into failures due to this change, when debugging on Windows
> > (with DWARF). See the run in
> > https://github.com/mstorsjo/actions-test/actions/runs/10020326811 vs
> > https://github.com/mstorsjo/actions-test/actions/runs/10020393197. Thanks
> > for rever
mstorsjo wrote:
FYI, I also ran into failures due to this change, when debugging on Windows
(with DWARF). See the run in
https://github.com/mstorsjo/actions-test/actions/runs/10020326811 vs
https://github.com/mstorsjo/actions-test/actions/runs/10020393197. Thanks for
reverting; hopefully it’s
mstorsjo wrote:
This causes build errors with GCC (11):
```
../../lldb/unittests/ValueObject/DumpValueObjectOptionsTests.cpp: In member
function ‘virtual void ValueObjectMockProcessTest_EmptyEnum_Test::TestBody()’:
../../lldb/unittests/ValueObject/DumpValueObjectOptionsTests.cpp:134:22: error:
@@ -593,6 +593,10 @@ TEST_F(GDBRemoteCommunicationClientTest, WriteMemoryTags) {
"E03", false);
}
+// Prior to this verison, constructing a std::future for a type without a
+// default constructor is not possible.
+//
https://developercommunity.visualstudio.c
mstorsjo wrote:
+1, this fixes my build errors for Windows targets as well:
https://github.com/mstorsjo/llvm-mingw/actions/runs/9167001362/job/25206642195
https://github.com/llvm/llvm-project/pull/92870
___
lldb-commits mailing list
lldb-commits@lists
https://github.com/mstorsjo closed
https://github.com/llvm/llvm-project/pull/76137
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -44,6 +44,10 @@ endif()
if (WIN32)
add_definitions(-D_ENABLE_EXTENDED_ALIGNED_STORAGE)
+ if (NOT MSVC)
mstorsjo wrote:
This was never defined for clang-cl/MSVC builds before. Note that the existing
define I'm removing is within this context:
```
#if !
https://github.com/mstorsjo created
https://github.com/llvm/llvm-project/pull/76137
We previously were defining _BSD_SOURCE right before including getopt.h.
However, on mingw-w64, getopt.h is also transitively included by unistd.h, and
unistd.h can be transitively included by many headers (rec
mstorsjo wrote:
> > BTW, when compiling the file I also get a bunch of warnings in this style:
>
> @mstorsjo maybe `unsigned long` is 32 bits on that platform... what's the
> target triple?
Ah, indeed - yes, Windows has 32 bit `long`s. The triples are
`aarch64-windows-gnu` or `aarch64-windows
mstorsjo wrote:
This commit broken building compiler-rt builtins for Windows on aarch64;
building now hits these errors:
```
llvm-project/compiler-rt/lib/builtins/cpu_model.c:1192:2: error: No support for
checking for lse atomics on this platfrom yet.
1192 | #error No support for checking for
mstorsjo wrote:
Could we please land this now?
https://github.com/llvm/llvm-project/pull/74580
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -642,18 +642,8 @@ get_sanitizer_flags(SANITIZER_FLAGS
"${LLVM_USE_SANITIZER}")
# Link system libraries ===
function(cxx_link_system_libraries target)
-
-# In order to remove just libc++ from the link step
-# we need to us
@@ -642,18 +642,8 @@ get_sanitizer_flags(SANITIZER_FLAGS
"${LLVM_USE_SANITIZER}")
# Link system libraries ===
function(cxx_link_system_libraries target)
-
-# In order to remove just libc++ from the link step
-# we need to us
Author: Martin Storsjö
Date: 2023-10-04T14:34:12+03:00
New Revision: d918b813c852fb4632875c683f4b9552eddea30d
URL:
https://github.com/llvm/llvm-project/commit/d918b813c852fb4632875c683f4b9552eddea30d
DIFF:
https://github.com/llvm/llvm-project/commit/d918b813c852fb4632875c683f4b9552eddea30d.diff
Author: Yuxuan Shui
Date: 2023-08-30T15:53:31+03:00
New Revision: 9a4b3fdb82327e808213070fd157be3c557b8b9d
URL:
https://github.com/llvm/llvm-project/commit/9a4b3fdb82327e808213070fd157be3c557b8b9d
DIFF:
https://github.com/llvm/llvm-project/commit/9a4b3fdb82327e808213070fd157be3c557b8b9d.diff
L
Author: Martin Storsjö
Date: 2023-08-10T12:59:35+03:00
New Revision: 68744ffbdd7daac41da274eef9ac0d191e11c16d
URL:
https://github.com/llvm/llvm-project/commit/68744ffbdd7daac41da274eef9ac0d191e11c16d
DIFF:
https://github.com/llvm/llvm-project/commit/68744ffbdd7daac41da274eef9ac0d191e11c16d.diff
Author: Martin Storsjö
Date: 2023-02-15T14:44:17+02:00
New Revision: a8483b9b30385807790882b3b770fa6d016a0aa4
URL:
https://github.com/llvm/llvm-project/commit/a8483b9b30385807790882b3b770fa6d016a0aa4
DIFF:
https://github.com/llvm/llvm-project/commit/a8483b9b30385807790882b3b770fa6d016a0aa4.diff
Author: Martin Storsjö
Date: 2022-10-18T11:54:19+03:00
New Revision: b2a5dd12a47a784f09628f1c10ab369c3b2c3c88
URL:
https://github.com/llvm/llvm-project/commit/b2a5dd12a47a784f09628f1c10ab369c3b2c3c88
DIFF:
https://github.com/llvm/llvm-project/commit/b2a5dd12a47a784f09628f1c10ab369c3b2c3c88.diff
Author: Martin Storsjö
Date: 2022-10-01T14:27:48+03:00
New Revision: e9e3a612ecd18a42f931c09223898128da3142f6
URL:
https://github.com/llvm/llvm-project/commit/e9e3a612ecd18a42f931c09223898128da3142f6
DIFF:
https://github.com/llvm/llvm-project/commit/e9e3a612ecd18a42f931c09223898128da3142f6.diff
Author: Alvin Wong
Date: 2022-09-30T13:51:56+03:00
New Revision: fe17e026959cc263c12fafa3a8e9e83503f9a18b
URL:
https://github.com/llvm/llvm-project/commit/fe17e026959cc263c12fafa3a8e9e83503f9a18b
DIFF:
https://github.com/llvm/llvm-project/commit/fe17e026959cc263c12fafa3a8e9e83503f9a18b.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:12+03:00
New Revision: 8a67a05e93349e341d1325f1a6428d1373f77177
URL:
https://github.com/llvm/llvm-project/commit/8a67a05e93349e341d1325f1a6428d1373f77177
DIFF:
https://github.com/llvm/llvm-project/commit/8a67a05e93349e341d1325f1a6428d1373f77177.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:11+03:00
New Revision: acf7d081198f380d6ad2a1b859930e50a9cf2dae
URL:
https://github.com/llvm/llvm-project/commit/acf7d081198f380d6ad2a1b859930e50a9cf2dae
DIFF:
https://github.com/llvm/llvm-project/commit/acf7d081198f380d6ad2a1b859930e50a9cf2dae.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:11+03:00
New Revision: 7ebff6ab26aa03423c61e0370377f11725184199
URL:
https://github.com/llvm/llvm-project/commit/7ebff6ab26aa03423c61e0370377f11725184199
DIFF:
https://github.com/llvm/llvm-project/commit/7ebff6ab26aa03423c61e0370377f11725184199.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:11+03:00
New Revision: 20c2f94c3cc10c41ab45e1be156540a06306cdf1
URL:
https://github.com/llvm/llvm-project/commit/20c2f94c3cc10c41ab45e1be156540a06306cdf1
DIFF:
https://github.com/llvm/llvm-project/commit/20c2f94c3cc10c41ab45e1be156540a06306cdf1.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:10+03:00
New Revision: 0870afc68e1a1ec303af1d0dbf952dd2c41f478a
URL:
https://github.com/llvm/llvm-project/commit/0870afc68e1a1ec303af1d0dbf952dd2c41f478a
DIFF:
https://github.com/llvm/llvm-project/commit/0870afc68e1a1ec303af1d0dbf952dd2c41f478a.diff
LO
Author: Alvin Wong
Date: 2022-09-28T12:57:10+03:00
New Revision: bf0cda9ed2783a34efed3fc9804d784f7d1df242
URL:
https://github.com/llvm/llvm-project/commit/bf0cda9ed2783a34efed3fc9804d784f7d1df242
DIFF:
https://github.com/llvm/llvm-project/commit/bf0cda9ed2783a34efed3fc9804d784f7d1df242.diff
LO
Author: Alvin Wong
Date: 2022-09-27T13:09:45+03:00
New Revision: a426753ef0290362a0268f917dba46d6b9744b02
URL:
https://github.com/llvm/llvm-project/commit/a426753ef0290362a0268f917dba46d6b9744b02
DIFF:
https://github.com/llvm/llvm-project/commit/a426753ef0290362a0268f917dba46d6b9744b02.diff
LO
Author: Alvin Wong
Date: 2022-09-27T13:09:59+03:00
New Revision: f4991bfa891eaf9f36aa3b79da6fed4228b69de9
URL:
https://github.com/llvm/llvm-project/commit/f4991bfa891eaf9f36aa3b79da6fed4228b69de9
DIFF:
https://github.com/llvm/llvm-project/commit/f4991bfa891eaf9f36aa3b79da6fed4228b69de9.diff
LO
Author: Martin Storsjö
Date: 2022-09-26T11:05:42+03:00
New Revision: 8a3597d73c8f694ca8c991d8cb4bb97a4ac8ba8c
URL:
https://github.com/llvm/llvm-project/commit/8a3597d73c8f694ca8c991d8cb4bb97a4ac8ba8c
DIFF:
https://github.com/llvm/llvm-project/commit/8a3597d73c8f694ca8c991d8cb4bb97a4ac8ba8c.diff
Author: Martin Storsjö
Date: 2022-08-30T10:07:44+03:00
New Revision: 118038e878cf7c169c74cdf31de019913775e881
URL:
https://github.com/llvm/llvm-project/commit/118038e878cf7c169c74cdf31de019913775e881
DIFF:
https://github.com/llvm/llvm-project/commit/118038e878cf7c169c74cdf31de019913775e881.diff
Author: Martin Storsjö
Date: 2022-08-29T13:25:38+03:00
New Revision: 5f0080fbe810caae3750d159da62bac04dbd844f
URL:
https://github.com/llvm/llvm-project/commit/5f0080fbe810caae3750d159da62bac04dbd844f
DIFF:
https://github.com/llvm/llvm-project/commit/5f0080fbe810caae3750d159da62bac04dbd844f.diff
Author: Martin Storsjö
Date: 2022-08-22T14:53:29+03:00
New Revision: b21de9b38f4b5f2ae6d49f973b683f118b9d58cb
URL:
https://github.com/llvm/llvm-project/commit/b21de9b38f4b5f2ae6d49f973b683f118b9d58cb
DIFF:
https://github.com/llvm/llvm-project/commit/b21de9b38f4b5f2ae6d49f973b683f118b9d58cb.diff
Author: Martin Storsjö
Date: 2022-08-12T00:35:32+03:00
New Revision: a5881e8a810bac74af2efcdcf12c741d52a1970a
URL:
https://github.com/llvm/llvm-project/commit/a5881e8a810bac74af2efcdcf12c741d52a1970a
DIFF:
https://github.com/llvm/llvm-project/commit/a5881e8a810bac74af2efcdcf12c741d52a1970a.diff
Author: Martin Storsjö
Date: 2022-08-02T10:57:33+03:00
New Revision: b7c5683fac3de2f3349d57b9e133ac53204b1148
URL:
https://github.com/llvm/llvm-project/commit/b7c5683fac3de2f3349d57b9e133ac53204b1148
DIFF:
https://github.com/llvm/llvm-project/commit/b7c5683fac3de2f3349d57b9e133ac53204b1148.diff
Author: Martin Storsjö
Date: 2022-07-13T23:57:01+03:00
New Revision: a1568fa27885d12c504e42dd02b0ce3687863fd8
URL:
https://github.com/llvm/llvm-project/commit/a1568fa27885d12c504e42dd02b0ce3687863fd8
DIFF:
https://github.com/llvm/llvm-project/commit/a1568fa27885d12c504e42dd02b0ce3687863fd8.diff
Author: Martin Storsjö
Date: 2022-07-13T12:57:04+03:00
New Revision: 306fc2cd87f2a52c21eb3606eff33d78e25d9368
URL:
https://github.com/llvm/llvm-project/commit/306fc2cd87f2a52c21eb3606eff33d78e25d9368
DIFF:
https://github.com/llvm/llvm-project/commit/306fc2cd87f2a52c21eb3606eff33d78e25d9368.diff
Author: Martin Storsjö
Date: 2022-07-11T23:41:35+03:00
New Revision: 66cdd6548ac51f2039b9f0bc10ec03f387b210c4
URL:
https://github.com/llvm/llvm-project/commit/66cdd6548ac51f2039b9f0bc10ec03f387b210c4
DIFF:
https://github.com/llvm/llvm-project/commit/66cdd6548ac51f2039b9f0bc10ec03f387b210c4.diff
Author: Martin Storsjö
Date: 2022-07-06T12:13:36+03:00
New Revision: 4270c9cd44f2703bc5376ff085d0add156af9080
URL:
https://github.com/llvm/llvm-project/commit/4270c9cd44f2703bc5376ff085d0add156af9080
DIFF:
https://github.com/llvm/llvm-project/commit/4270c9cd44f2703bc5376ff085d0add156af9080.diff
Author: Alvin Wong
Date: 2022-06-22T20:49:30+03:00
New Revision: a1ee0b947d46c9be1cc2ea8db21603bac84efb18
URL:
https://github.com/llvm/llvm-project/commit/a1ee0b947d46c9be1cc2ea8db21603bac84efb18
DIFF:
https://github.com/llvm/llvm-project/commit/a1ee0b947d46c9be1cc2ea8db21603bac84efb18.diff
LO
Author: Martin Storsjö
Date: 2022-06-22T18:48:04+03:00
New Revision: 0bc7105cd1447c2d85716c3dcd2924595decc939
URL:
https://github.com/llvm/llvm-project/commit/0bc7105cd1447c2d85716c3dcd2924595decc939
DIFF:
https://github.com/llvm/llvm-project/commit/0bc7105cd1447c2d85716c3dcd2924595decc939.diff
Author: Alvin Wong
Date: 2022-06-22T17:16:06+03:00
New Revision: 3c867898c7be7ed2b5d119a2478a836a0c85f19b
URL:
https://github.com/llvm/llvm-project/commit/3c867898c7be7ed2b5d119a2478a836a0c85f19b
DIFF:
https://github.com/llvm/llvm-project/commit/3c867898c7be7ed2b5d119a2478a836a0c85f19b.diff
LO
Author: Alvin Wong
Date: 2022-06-22T17:16:06+03:00
New Revision: 4d123783957e547009e55346bf3a8ae43a88fa14
URL:
https://github.com/llvm/llvm-project/commit/4d123783957e547009e55346bf3a8ae43a88fa14
DIFF:
https://github.com/llvm/llvm-project/commit/4d123783957e547009e55346bf3a8ae43a88fa14.diff
LO
Author: Alvin Wong
Date: 2022-06-22T17:16:05+03:00
New Revision: 2bae9560575362ffd756f193efa1de2d5c2f4cfd
URL:
https://github.com/llvm/llvm-project/commit/2bae9560575362ffd756f193efa1de2d5c2f4cfd
DIFF:
https://github.com/llvm/llvm-project/commit/2bae9560575362ffd756f193efa1de2d5c2f4cfd.diff
LO
Author: Martin Storsjö
Date: 2022-06-22T17:16:05+03:00
New Revision: 8a64dd5b06146f073a4a326f0e24fa18e571b281
URL:
https://github.com/llvm/llvm-project/commit/8a64dd5b06146f073a4a326f0e24fa18e571b281
DIFF:
https://github.com/llvm/llvm-project/commit/8a64dd5b06146f073a4a326f0e24fa18e571b281.diff
Author: Martin Storsjö
Date: 2022-06-22T16:11:59+03:00
New Revision: 9846a1f2d4723a8c060370638bbd52360638d0fc
URL:
https://github.com/llvm/llvm-project/commit/9846a1f2d4723a8c060370638bbd52360638d0fc
DIFF:
https://github.com/llvm/llvm-project/commit/9846a1f2d4723a8c060370638bbd52360638d0fc.diff
Author: Martin Storsjö
Date: 2022-06-21T00:19:09+03:00
New Revision: c9fc4336d4b35cd1ed8083336c997c159f286794
URL:
https://github.com/llvm/llvm-project/commit/c9fc4336d4b35cd1ed8083336c997c159f286794
DIFF:
https://github.com/llvm/llvm-project/commit/c9fc4336d4b35cd1ed8083336c997c159f286794.diff
1 - 100 of 147 matches
Mail list logo
