Author: Owen Pan
Date: 2024-09-01T10:20:55+02:00
New Revision: 1ccd19c4b297e9a2bd1b2bb6bbb9d9ad2acbab40
URL:
https://github.com/llvm/llvm-project/commit/1ccd19c4b297e9a2bd1b2bb6bbb9d9ad2acbab40
DIFF:
https://github.com/llvm/llvm-project/commit/1ccd19c4b297e9a2bd1b2bb6bbb9d9ad2acbab40.diff
LOG:
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106439
>From 491375504831aae3da85ffb288ca3c8b3c94b1ea Mon Sep 17 00:00:00 2001
From: Joseph Huber
Date: Tue, 6 Aug 2024 21:33:25 -0500
Subject: [PATCH] Revert "[LinkerWrapper] Extend with usual pass options
(#96704)" (#102
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/105967
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/102881
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106390
>From f88180bbc489a587954adfce40cc5c90adc74962 Mon Sep 17 00:00:00 2001
From: Krasimir Georgiev
Date: Wed, 28 Aug 2024 13:45:17 +0200
Subject: [PATCH] [clang-format] js handle anonymous classes (#106242)
Addresses a
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/105516
>From f565cbd194c54a3fec64236330ade3760f473965 Mon Sep 17 00:00:00 2001
From: Balazs Benics
Date: Wed, 21 Aug 2024 14:24:56 +0200
Subject: [PATCH 1/2] [analyzer] Limit `isTainted()` by skipping complicated
symbols (
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106853
>From 816fde1cbb700ebcc8b3df81fb93d675c04c12cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?=
Date: Thu, 29 Aug 2024 20:57:25 +0200
Subject: [PATCH] [clang] Install scan-build-py into plain "lib"
tru wrote:
That does sound like it should be acceptable to merge if it's only blocking a
out-of-tree implementation, since we don't officially support that config in
that case. There is also the question as if we need to backport this - since if
the main complaint for it not going into main is
tru wrote:
Yeah I tend to agree that this is a seemingly nice to have thing, but it's not
really qualifying for a bugfix or a regression.
https://github.com/llvm/llvm-project/pull/106008
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.
tru wrote:
You can just close this PR and open a new one with both commits by running the
cherry-pick comment command again with both sha's listed.
https://github.com/llvm/llvm-project/pull/106729
___
llvm-branch-commits mailing list
llvm-branch-commi
tru wrote:
@tstellar several of the builds fail even after a rebase. Some of them seem
related (especially the macOS ones, so I won't merge this until you had some
time to look at it.
https://github.com/llvm/llvm-project/pull/106480
___
llvm-branch-c
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106900
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106985
>From d9cb501ec0012de5d4e1c6310df55f4e8af011a9 Mon Sep 17 00:00:00 2001
From: Hans
Date: Mon, 2 Sep 2024 15:04:13 +0200
Subject: [PATCH] Win release packaging: Don't try to use rpmalloc for 32-bit
x86 (#106969)
bec
Author: Hans
Date: 2024-09-03T09:02:01+02:00
New Revision: d9cb501ec0012de5d4e1c6310df55f4e8af011a9
URL:
https://github.com/llvm/llvm-project/commit/d9cb501ec0012de5d4e1c6310df55f4e8af011a9
DIFF:
https://github.com/llvm/llvm-project/commit/d9cb501ec0012de5d4e1c6310df55f4e8af011a9.diff
LOG: Win
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106985
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106989
>From 9b6180ed2ecbbb54f26caa78082e7b955a634117 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?kadir=20=C3=A7etinkaya?=
Date: Mon, 2 Sep 2024 15:25:26 +0200
Subject: [PATCH] [clangd] Update TidyFastChecks for release/19.x (
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106989
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: kadir çetinkaya
Date: 2024-09-03T09:03:13+02:00
New Revision: 9b6180ed2ecbbb54f26caa78082e7b955a634117
URL:
https://github.com/llvm/llvm-project/commit/9b6180ed2ecbbb54f26caa78082e7b955a634117
DIFF:
https://github.com/llvm/llvm-project/commit/9b6180ed2ecbbb54f26caa78082e7b955a634117.dif
tru wrote:
> Ah, I've just checked and I can't set miilestones, though :-//
I can do it for you - what's the issue or PR?
https://github.com/llvm/llvm-project/pull/106729
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106518
>From e3abd19242dd908e6186639d091f6ecc219963f0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Storsj=C3=B6?=
Date: Thu, 8 Aug 2024 13:51:07 +0300
Subject: [PATCH] [compiler-rt] Support building runtimes for Window
Author: Martin Storsjö
Date: 2024-09-03T16:04:12+02:00
New Revision: e3abd19242dd908e6186639d091f6ecc219963f0
URL:
https://github.com/llvm/llvm-project/commit/e3abd19242dd908e6186639d091f6ecc219963f0
DIFF:
https://github.com/llvm/llvm-project/commit/e3abd19242dd908e6186639d091f6ecc219963f0.diff
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106518
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Nikita Popov
Date: 2024-09-03T16:04:37+02:00
New Revision: e594b284810c73b09da9436fdc6f1cbbfb4a7924
URL:
https://github.com/llvm/llvm-project/commit/e594b284810c73b09da9436fdc6f1cbbfb4a7924
DIFF:
https://github.com/llvm/llvm-project/commit/e594b284810c73b09da9436fdc6f1cbbfb4a7924.diff
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106892
>From e594b284810c73b09da9436fdc6f1cbbfb4a7924 Mon Sep 17 00:00:00 2001
From: Nikita Popov
Date: Wed, 28 Aug 2024 12:54:14 +0200
Subject: [PATCH] [IndVars] Check if WideInc available before trying to use it
WideInc/
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107058
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106892
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107058
>From 2d90e8f7402b0a8114978b6f014cfe76c96c94a1 Mon Sep 17 00:00:00 2001
From: Owen Pan
Date: Mon, 2 Sep 2024 01:40:13 -0700
Subject: [PATCH] [clang-format] Correctly annotate braces in macro definition
(#106662)
Fi
Author: Owen Pan
Date: 2024-09-03T16:04:58+02:00
New Revision: 2d90e8f7402b0a8114978b6f014cfe76c96c94a1
URL:
https://github.com/llvm/llvm-project/commit/2d90e8f7402b0a8114978b6f014cfe76c96c94a1
DIFF:
https://github.com/llvm/llvm-project/commit/2d90e8f7402b0a8114978b6f014cfe76c96c94a1.diff
LOG:
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107060
>From f3da9af3fd2696fbbe437dea599eda088fcb5592 Mon Sep 17 00:00:00 2001
From: Jeremy Morse
Date: Mon, 2 Sep 2024 11:56:40 +0100
Subject: [PATCH] [DebugInfo][RemoveDIs] Find types hidden in DbgRecords
(#106547)
MIME-
Author: Jeremy Morse
Date: 2024-09-03T16:05:46+02:00
New Revision: f3da9af3fd2696fbbe437dea599eda088fcb5592
URL:
https://github.com/llvm/llvm-project/commit/f3da9af3fd2696fbbe437dea599eda088fcb5592
DIFF:
https://github.com/llvm/llvm-project/commit/f3da9af3fd2696fbbe437dea599eda088fcb5592.diff
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107082
>From 830b7ebac09ebef91671f0863986aee1a1d60e5e Mon Sep 17 00:00:00 2001
From: Patryk Wychowaniec
Date: Fri, 30 Aug 2024 15:25:54 +0200
Subject: [PATCH 1/2] [AVR] Fix parsing & emitting relative jumps (#106722)
Ever
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107060
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Patryk Wychowaniec
Date: 2024-09-03T16:07:37+02:00
New Revision: a01d631a1c2c3902b383b6491f27b72d63f6257b
URL:
https://github.com/llvm/llvm-project/commit/a01d631a1c2c3902b383b6491f27b72d63f6257b
DIFF:
https://github.com/llvm/llvm-project/commit/a01d631a1c2c3902b383b6491f27b72d63f6257b.
Author: Patryk Wychowaniec
Date: 2024-09-03T16:07:37+02:00
New Revision: 830b7ebac09ebef91671f0863986aee1a1d60e5e
URL:
https://github.com/llvm/llvm-project/commit/830b7ebac09ebef91671f0863986aee1a1d60e5e
DIFF:
https://github.com/llvm/llvm-project/commit/830b7ebac09ebef91671f0863986aee1a1d60e5e.
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107082
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru approved this pull request.
https://github.com/llvm/llvm-project/pull/107132
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
@AaronBallman Are we ready to merge this into the -final version?
https://github.com/llvm/llvm-project/pull/102070
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-b
tru wrote:
> @tru can I do something to help get that release note ^ into the release?
I think for the initial release we'll just use the release notes document in
the docs folder as usual. So I would add it to LLVM release notes and give me
PR for that.
https://github.com/llvm/llvm-project/p
https://github.com/tru approved this pull request.
https://github.com/llvm/llvm-project/pull/107826
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Yeah I'll merge it - I just do it in batches when I have time to review and
integrate them all (I can't use the merge button either - you have to do it
with a script ... due to reasons ...)
https://github.com/llvm/llvm-project/pull/107826
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/102070
>From 8664666823b3eb8d96fde58f79d71d36bd7f9115 Mon Sep 17 00:00:00 2001
From: Eli Friedman
Date: Thu, 1 Aug 2024 16:18:20 -0700
Subject: [PATCH] Fix codegen of consteval functions returning an empty class,
and relat
Author: Eli Friedman
Date: 2024-09-10T08:15:48+02:00
New Revision: 8664666823b3eb8d96fde58f79d71d36bd7f9115
URL:
https://github.com/llvm/llvm-project/commit/8664666823b3eb8d96fde58f79d71d36bd7f9115
DIFF:
https://github.com/llvm/llvm-project/commit/8664666823b3eb8d96fde58f79d71d36bd7f9115.diff
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/102070
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
ping @tstellar
https://github.com/llvm/llvm-project/pull/106480
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107132
>From e657e0256509f6f665917904078a5389684fc716 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 26 Jul 2024 07:38:53 -0700
Subject: [PATCH] workflows: Fix tag name for release sources job (#100752)
(cherry pic
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107132
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107183
>From 5cf78453b3de39247364ddf97b1c18c011283948 Mon Sep 17 00:00:00 2001
From: Yingwei Zheng
Date: Wed, 4 Sep 2024 13:36:32 +0800
Subject: [PATCH] [Clang][CodeGen] Don't emit assumptions if current block is
unreachab
Author: Yingwei Zheng
Date: 2024-09-10T08:20:55+02:00
New Revision: 5cf78453b3de39247364ddf97b1c18c011283948
URL:
https://github.com/llvm/llvm-project/commit/5cf78453b3de39247364ddf97b1c18c011283948
DIFF:
https://github.com/llvm/llvm-project/commit/5cf78453b3de39247364ddf97b1c18c011283948.diff
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107183
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
This has a conflict in the release notes file.
https://github.com/llvm/llvm-project/pull/107214
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
Author: Sander de Smalen
Date: 2024-09-10T08:22:18+02:00
New Revision: 52e5a72e9200667e8a62436268fdaff4411f7216
URL:
https://github.com/llvm/llvm-project/commit/52e5a72e9200667e8a62436268fdaff4411f7216
DIFF:
https://github.com/llvm/llvm-project/commit/52e5a72e9200667e8a62436268fdaff4411f7216.di
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107212
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107435
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107826
>From 64015eee93062b34df290338c45e87868fa750a9 Mon Sep 17 00:00:00 2001
From: Hans Wennborg
Date: Mon, 9 Sep 2024 10:56:37 +0200
Subject: [PATCH] Release note about targets built in the Windows packages
LLVM_TARGETS
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107826
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
W
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107435
>From 52e5a72e9200667e8a62436268fdaff4411f7216 Mon Sep 17 00:00:00 2001
From: Sander de Smalen
Date: Thu, 5 Sep 2024 17:54:57 +0100
Subject: [PATCH] [AArch64] Remove redundant COPY from loadRegFromStackSlot
(#107396
Author: Hans Wennborg
Date: 2024-09-10T08:22:48+02:00
New Revision: 64015eee93062b34df290338c45e87868fa750a9
URL:
https://github.com/llvm/llvm-project/commit/64015eee93062b34df290338c45e87868fa750a9
DIFF:
https://github.com/llvm/llvm-project/commit/64015eee93062b34df290338c45e87868fa750a9.diff
tru wrote:
> It introduces a performance regression. I have filed an issue to track this:
> https://github.com/llvm/llvm-project/issues/107946.
Is this something you also expect to backport in this case? do we want to wait
for this fix to be available before we merge? In that case - would it b
tru wrote:
Thanks for your detailed answer! I think this can go in 19.1.0
https://github.com/llvm/llvm-project/pull/106952
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bran
Author: Hua Tian
Date: 2024-09-10T16:46:49+02:00
New Revision: 2651d09ec9c4d87d09ae72d8bf42fab566fb02d0
URL:
https://github.com/llvm/llvm-project/commit/2651d09ec9c4d87d09ae72d8bf42fab566fb02d0
DIFF:
https://github.com/llvm/llvm-project/commit/2651d09ec9c4d87d09ae72d8bf42fab566fb02d0.diff
LOG:
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107338
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107338
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
I'll take it for 19 if we can get a reviewer to approve it.
https://github.com/llvm/llvm-project/pull/107466
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107531
>From 327ca6c02f0dbf13dd6f039d30d320a7ba1456b8 Mon Sep 17 00:00:00 2001
From: Owen Pan
Date: Thu, 5 Sep 2024 23:59:11 -0700
Subject: [PATCH] [clang-format] Correctly annotate braces in macro definition
(#107352)
Th
Author: Owen Pan
Date: 2024-09-10T16:48:49+02:00
New Revision: 327ca6c02f0dbf13dd6f039d30d320a7ba1456b8
URL:
https://github.com/llvm/llvm-project/commit/327ca6c02f0dbf13dd6f039d30d320a7ba1456b8
DIFF:
https://github.com/llvm/llvm-project/commit/327ca6c02f0dbf13dd6f039d30d320a7ba1456b8.diff
LOG:
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107531
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
this was merged - not sure why github shows it as closed instead.
https://github.com/llvm/llvm-project/pull/107338
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-b
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107214
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/108422
>From 32a8b56bbf0a3c7678d44ba690427915446a9a72 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Thu, 12 Sep 2024 09:50:57 -0700
Subject: [PATCH] workflows/release-binaries: Fix automatic upload (#107315)
(cherry pi
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/108422
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/104747
>From e475814473c5990a1409e24d4ecd56ce01546fd0 Mon Sep 17 00:00:00 2001
From: Alexey Bataev
Date: Thu, 15 Aug 2024 07:21:10 -0700
Subject: [PATCH 1/2] [SLP][NFC]Add a test with incorrect minbitwidth analysis
for red
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/104747
>From 373180b440d04dc3cc0f6111b06684d18779d7c8 Mon Sep 17 00:00:00 2001
From: Alexey Bataev
Date: Thu, 15 Aug 2024 07:21:10 -0700
Subject: [PATCH] [SLP]Fix PR104422: Wrong value truncation
The minbitwidth restrictio
Author: Alexey Bataev
Date: 2024-09-13T07:58:38+02:00
New Revision: 373180b440d04dc3cc0f6111b06684d18779d7c8
URL:
https://github.com/llvm/llvm-project/commit/373180b440d04dc3cc0f6111b06684d18779d7c8
DIFF:
https://github.com/llvm/llvm-project/commit/373180b440d04dc3cc0f6111b06684d18779d7c8.diff
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/104747
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106008
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
This will have to wait for LLVM 20. I know it's not optimal for zig, but
getting it in this late and it being abi breaking is tricky.
https://github.com/llvm/llvm-project/pull/106008
___
llvm-branch-commits mailing list
llvm-branch-commits@
tru wrote:
Can this be reviewed @cor3ntin @mizvekov
https://github.com/llvm/llvm-project/pull/106043
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
tru wrote:
Just re-run the cherry-pick comment on the updated SHA.
https://github.com/llvm/llvm-project/pull/107990
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-comm
Author: Jay Foad
Date: 2024-09-13T08:04:58+02:00
New Revision: 93998aff7662d9b3f94d9627179dffe342e2b399
URL:
https://github.com/llvm/llvm-project/commit/93998aff7662d9b3f94d9627179dffe342e2b399
DIFF:
https://github.com/llvm/llvm-project/commit/93998aff7662d9b3f94d9627179dffe342e2b399.diff
LOG:
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/106977
>From 93998aff7662d9b3f94d9627179dffe342e2b399 Mon Sep 17 00:00:00 2001
From: Jay Foad
Date: Tue, 27 Aug 2024 17:09:40 +0100
Subject: [PATCH] [AMDGPU] Fix sign confusion in performMulLoHiCombine
(#105831)
SMUL_LOHI
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/106977
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/tru updated https://github.com/llvm/llvm-project/pull/107466
>From f0010d131b79a1b401777aa32e96defc4a935c9d Mon Sep 17 00:00:00 2001
From: R-Goc <131907007+r-...@users.noreply.github.com>
Date: Wed, 4 Sep 2024 20:10:36 +0200
Subject: [PATCH] [Windows SEH] Fix crash on empty seh
Author: R-Goc
Date: 2024-09-13T08:05:50+02:00
New Revision: f0010d131b79a1b401777aa32e96defc4a935c9d
URL:
https://github.com/llvm/llvm-project/commit/f0010d131b79a1b401777aa32e96defc4a935c9d
DIFF:
https://github.com/llvm/llvm-project/commit/f0010d131b79a1b401777aa32e96defc4a935c9d.diff
LOG: [W
https://github.com/tru closed https://github.com/llvm/llvm-project/pull/107466
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
tru wrote:
Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
pick at this point. Can you please respond to the following questions to help
me understand if this has to be included in the final release or not.
Is this PR a fix for a regression or a critical issue?
901 - 1000 of 2019 matches
Mail list logo