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 90d0d4888954f7642b6d0b84b09088150347a444
21a52dd8627325f31f4bc9455b15f2f79a3e896e --e
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/107137
>From 50c021b09950cf7d6a8f25b1ac0dec246f2325f5 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Tue, 3 Sep 2024 11:38:04 -0700
Subject: [PATCH 1/2] update pseudoprobe-decoding-inline.test
Created using spr 1.3.4
aaupov wrote:
The latest version has even more compact encoding.
On top of related change #107970 which drops blocks without counters from BAT
YAML profile, this version achieves the following, for the same inputs as above:
- Profile without probe information: 33MB, 3.8MB compressed (baseline)
https://github.com/aaupov edited
https://github.com/llvm/llvm-project/pull/107137
___
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/aaupov updated
https://github.com/llvm/llvm-project/pull/99891
>From 36197b175681d07b4704e576fb008cec3cc1e05e Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Wed, 28 Aug 2024 21:10:25 +0200
Subject: [PATCH 1/2] Reworked block probe matching
Use new probe ifaces
Get all func
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/99891
>From 36197b175681d07b4704e576fb008cec3cc1e05e Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Wed, 28 Aug 2024 21:10:25 +0200
Subject: [PATCH 1/2] Reworked block probe matching
Use new probe ifaces
Get all func
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
github-actions[bot] wrote:
@efriedma-quic (or anyone else). If you would like to add a note about this fix
in the release notes (completely optional). Please reply to this comment with a
one or two sentence description of the fix. When you are done, please add the
release:note label to this P
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
github-actions[bot] wrote:
@tstellar (or anyone else). If you would like to add a note about this fix in
the release notes (completely optional). Please reply to this comment with a
one or two sentence description of the fix. When you are done, please add the
release:note label to this PR.
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
github-actions[bot] wrote:
@cor3ntin (or anyone else). If you would like to add a note about this fix in
the release notes (completely optional). Please reply to this comment with a
one or two sentence description of the fix. When you are done, please add the
release:note label to this PR.
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
github-actions[bot] wrote:
@dtcxzyw (or anyone else). If you would like to add a note about this fix in
the release notes (completely optional). Please reply to this comment with a
one or two sentence description of the fix. When you are done, please add the
release:note label to this PR.
h
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
github-actions[bot] wrote:
@sdesmalen-arm (or anyone else). If you would like to add a note about this fix
in the release notes (completely optional). Please reply to this comment with a
one or two sentence description of the fix. When you are done, please add the
release:note label to this P
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
github-actions[bot] wrote:
@zmodem (or anyone else). If you would like to add a note about this fix in the
release notes (completely optional). Please reply to this comment with a one or
two sentence description of the fix. When you are done, please add the
release:note label to this PR.
ht
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
prj- wrote:
> Is this PR a fix for a regression or a critical issue?
This is a fix for a regression that you merged in `release/19.x` after the
release of RC4. See discussion here
https://github.com/llvm/llvm-project/pull/107058#issuecomment-2326793119.
`clang-format` maintainers will of cour
huaatian 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 cri
101 - 144 of 144 matches
Mail list logo
