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
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
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
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
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
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 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
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 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/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 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
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
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:
@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:
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:
@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.
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
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 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
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:
@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.
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
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
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:
@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:
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
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
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
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/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
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
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 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
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] update pseudoprobe-decoding-inline.test
Created using spr 1.3.4
---
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] update pseudoprobe-decoding-inline.test
Created using spr 1.3.4
---
llvmbot wrote:
@llvm/pr-subscribers-bolt
Author: Amir Ayupov (aaupov)
Changes
Align BAT YAML (DataAggregator) to YAMLProfileWriter which drops blocks
without profile:
https://github.com/llvm/llvm-project/blob/main/bolt/lib/Profile/YAMLProfileWriter.cpp#L162-L176
Test Plan: NFCI
---
Full
https://github.com/aaupov created
https://github.com/llvm/llvm-project/pull/107970
Align BAT YAML (DataAggregator) to YAMLProfileWriter which drops blocks
without profile:
https://github.com/llvm/llvm-project/blob/main/bolt/lib/Profile/YAMLProfileWriter.cpp#L162-L176
Test Plan: NFCI
JDevlieghere wrote:
I'm supportive of merging this but only once we've decorated the test
accordingly (CC @Michael137). Currently this causes a test failure on Apple
Silicon:
https://ci.swift.org/view/all/job/llvm.org/view/LLDB/job/as-lldb-cmake/
https://github.com/llvm/llvm-project/pull/107
https://github.com/SixWeining approved this pull request.
https://github.com/llvm/llvm-project/pull/107948
___
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/llvmbot milestoned
https://github.com/llvm/llvm-project/pull/107948
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: None (llvmbot)
Changes
Backport 1ca411ca451e0e86caf9207779616f32ed9fd908
Requested by: @wangleiat
---
Full diff: https://github.com/llvm/llvm-project/pull/107948.diff
3 Files Affected:
- (modified) llvm/lib/Target/LoongArch
llvmbot wrote:
@SixWeining What do you think about merging this PR to the release branch?
https://github.com/llvm/llvm-project/pull/107948
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
https://github.com/llvmbot created
https://github.com/llvm/llvm-project/pull/107948
Backport 1ca411ca451e0e86caf9207779616f32ed9fd908
Requested by: @wangleiat
>From 9cd12fa1c545bea1c61bb1d85b451b5f391aac4e Mon Sep 17 00:00:00 2001
From: wanglei
Date: Tue, 10 Sep 2024 09:28:15 +0800
Subject: [
https://github.com/wangleiat approved this pull request.
https://github.com/llvm/llvm-project/pull/107945
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: None (llvmbot)
Changes
Backport a111f9119a5ec77c19a514ec09454218f739454f
Requested by: @dtcxzyw
---
Full diff: https://github.com/llvm/llvm-project/pull/107945.diff
2 Files Affected:
- (modified) llvm/lib/Target/LoongArch/L
https://github.com/llvmbot created
https://github.com/llvm/llvm-project/pull/107945
Backport a111f9119a5ec77c19a514ec09454218f739454f
Requested by: @dtcxzyw
>From 7b4ab2233655a30cf04d52ba98a707d1b6cb3036 Mon Sep 17 00:00:00 2001
From: Yingwei Zheng
Date: Tue, 10 Sep 2024 09:19:39 +0800
Subjec
llvmbot wrote:
@wangleiat What do you think about merging this PR to the release branch?
https://github.com/llvm/llvm-project/pull/107945
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/lis
https://github.com/llvmbot milestoned
https://github.com/llvm/llvm-project/pull/107945
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -94,6 +95,7 @@ class OpLowerer {
DiagnosticInfoUnsupported Diag(*CI->getFunction(), Message,
CI->getDebugLoc());
M.getContext().diagnose(Diag);
+HasErrors = true;
bogner wrote:
I pushed the `boo
https://github.com/bogner updated
https://github.com/llvm/llvm-project/pull/104253
>From d49a863313c30d3e75205dbffddc8f81980ed25b Mon Sep 17 00:00:00 2001
From: Justin Bogner
Date: Mon, 9 Sep 2024 17:55:15 -0700
Subject: [PATCH] Propagate HasErrors through return values
Created using spr 1.3.5
@@ -289,6 +289,43 @@ class OpLowerer {
});
}
+ void lowerTypedBufferStore(Function &F) {
+IRBuilder<> &IRB = OpBuilder.getIRB();
+Type *Int8Ty = IRB.getInt8Ty();
+Type *Int32Ty = IRB.getInt32Ty();
+
+replaceFunction(F, [&](CallInst *CI) -> Error {
--
@@ -94,6 +95,7 @@ class OpLowerer {
DiagnosticInfoUnsupported Diag(*CI->getFunction(), Message,
CI->getDebugLoc());
M.getContext().diagnose(Diag);
+HasErrors = true;
bogner wrote:
Even if we did pa
https://github.com/farzonl edited
https://github.com/llvm/llvm-project/pull/104253
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -289,6 +289,43 @@ class OpLowerer {
});
}
+ void lowerTypedBufferStore(Function &F) {
+IRBuilder<> &IRB = OpBuilder.getIRB();
+Type *Int8Ty = IRB.getInt8Ty();
+Type *Int32Ty = IRB.getInt32Ty();
+
+replaceFunction(F, [&](CallInst *CI) -> Error {
--
@@ -289,6 +289,43 @@ class OpLowerer {
});
}
+ void lowerTypedBufferStore(Function &F) {
+IRBuilder<> &IRB = OpBuilder.getIRB();
+Type *Int8Ty = IRB.getInt8Ty();
+Type *Int32Ty = IRB.getInt32Ty();
+
+replaceFunction(F, [&](CallInst *CI) -> Error {
--
https://github.com/hekota approved this pull request.
https://github.com/llvm/llvm-project/pull/104253
___
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/farzonl approved this pull request.
https://github.com/llvm/llvm-project/pull/104253
___
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/farzonl edited
https://github.com/llvm/llvm-project/pull/104253
___
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/vitalybuka updated
https://github.com/llvm/llvm-project/pull/107941
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -289,6 +289,43 @@ class OpLowerer {
});
}
+ void lowerTypedBufferStore(Function &F) {
+IRBuilder<> &IRB = OpBuilder.getIRB();
+Type *Int8Ty = IRB.getInt8Ty();
+Type *Int32Ty = IRB.getInt32Ty();
+
+replaceFunction(F, [&](CallInst *CI) -> Error {
--
https://github.com/vitalybuka updated
https://github.com/llvm/llvm-project/pull/107941
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-compiler-rt-sanitizer
Author: Vitaly Buka (vitalybuka)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/107941.diff
1 Files Affected:
- (modified) compiler-rt/lib/sanitizer_common/sanitizer_tls_get_addr.cpp (+4)
``diff
dif
https://github.com/vitalybuka created
https://github.com/llvm/llvm-project/pull/107941
None
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -94,6 +95,7 @@ class OpLowerer {
DiagnosticInfoUnsupported Diag(*CI->getFunction(), Message,
CI->getDebugLoc());
M.getContext().diagnose(Diag);
+HasErrors = true;
farzonl wrote:
`HasErrors ` upd
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (llvmbot)
Changes
Backport adf44d5c3ea03569f019740e1140c3205810b3fa
Requested by: @tstellar
---
Full diff: https://github.com/llvm/llvm-project/pull/107938.diff
3 Files Affected:
- (modified)
lldb/test/API/commands/expression/impo
llvmbot wrote:
@felipepiovezan What do you think about merging this PR to the release branch?
https://github.com/llvm/llvm-project/pull/107938
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailma
https://github.com/llvmbot created
https://github.com/llvm/llvm-project/pull/107938
Backport adf44d5c3ea03569f019740e1140c3205810b3fa
Requested by: @tstellar
>From ceccb786ea6247de6681ba5c37289305f06d2a08 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Fri, 6 Sep 2024 17:05:32 -0700
Subject
https://github.com/llvmbot milestoned
https://github.com/llvm/llvm-project/pull/107938
___
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/bogner updated
https://github.com/llvm/llvm-project/pull/104253
___
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/bogner updated
https://github.com/llvm/llvm-project/pull/104253
___
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/krzysz00 updated
https://github.com/llvm/llvm-project/pull/107659
>From c7d3804afe9a7e6325f6af230f060c19aceca09b Mon Sep 17 00:00:00 2001
From: Krzysztof Drewniak
Date: Fri, 6 Sep 2024 23:45:52 +
Subject: [PATCH 1/3] [mlir][GPU] Plumb range information through the NVVM
l
https://github.com/farzonl edited
https://github.com/llvm/llvm-project/pull/104253
___
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/farzonl edited
https://github.com/llvm/llvm-project/pull/104253
___
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/farzonl edited
https://github.com/llvm/llvm-project/pull/104253
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -361,11 +361,60 @@ Examples:
- ``i32``
- Index into the buffer
+Texture and Typed Buffer Stores
+---
+
+*relevant types: Textures and TypedBuffer*
+
+The `TextureStore`_ and `BufferStore`_ DXIL operations can only be used to
+write all
@@ -361,11 +361,60 @@ Examples:
- ``i32``
- Index into the buffer
+Texture and Typed Buffer Stores
+---
+
+*relevant types: Textures and TypedBuffer*
+
+The `TextureStore`_ and `BufferStore`_ DXIL operations can only be used to
+write all
@@ -361,11 +361,60 @@ Examples:
- ``i32``
- Index into the buffer
+Texture and Typed Buffer Stores
+---
+
+*relevant types: Textures and TypedBuffer*
+
+The `TextureStore`_ and `BufferStore`_ DXIL operations can only be used to
+write all
@@ -361,11 +361,60 @@ Examples:
- ``i32``
- Index into the buffer
+Texture and Typed Buffer Stores
+---
+
+*relevant types: Textures and TypedBuffer*
+
+The `TextureStore`_ and `BufferStore`_ DXIL operations can only be used to
---
@@ -699,9 +699,21 @@ gpu.module @test_module_32 {
}
gpu.module @test_module_33 {
-// CHECK-LABEL: func @kernel_with_block_size()
-// CHECK: attributes {gpu.kernel, gpu.known_block_size = array, nvvm.kernel, nvvm.maxntid = array}
- gpu.func @kernel_with_block_size() kernel att
@@ -209,7 +209,12 @@ struct GPULaneIdOpToNVVM :
ConvertOpToLLVMPattern {
ConversionPatternRewriter &rewriter) const override {
auto loc = op->getLoc();
MLIRContext *context = rewriter.getContext();
-Value newOp = rewriter.create(loc, rewriter.getI
@@ -1784,53 +1799,53 @@ def NVVM_CpAsyncBulkWaitGroupOp :
NVVM_Op<"cp.async.bulk.wait_group">,
}];
}
-def NVVM_CpAsyncBulkTensorGlobalToSharedClusterOp :
- NVVM_Op<"cp.async.bulk.tensor.shared.cluster.global",
- [DeclareOpInterfaceMethods,
+def NVVM_CpAsyncBulkTensorGl
@@ -388,10 +432,13 @@ class OpLowerer {
case Intrinsic::dx_typedBufferLoad:
lowerTypedBufferLoad(F);
break;
+ case Intrinsic::dx_typedBufferStore:
+lowerTypedBufferStore(F);
+break;
}
Updated = true;
}
-if (Updat
https://github.com/damyanp approved this pull request.
https://github.com/llvm/llvm-project/pull/104253
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
@@ -388,10 +432,13 @@ class OpLowerer {
case Intrinsic::dx_typedBufferLoad:
lowerTypedBufferLoad(F);
break;
+ case Intrinsic::dx_typedBufferStore:
+lowerTypedBufferStore(F);
+break;
}
Updated = true;
}
-if (Updat
bogner wrote:
Please take another look - specifically I'd like some review on the doc changes
to make sure they're clear.
https://github.com/llvm/llvm-project/pull/104253
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://
@@ -289,6 +289,43 @@ class OpLowerer {
});
}
+ void lowerTypedBufferStore(Function &F) {
+IRBuilder<> &IRB = OpBuilder.getIRB();
+Type *Int8Ty = IRB.getInt8Ty();
+Type *Int32Ty = IRB.getInt32Ty();
+
+replaceFunction(F, [&](CallInst *CI) -> Error {
+
@@ -259,6 +259,114 @@ class OpLowerer {
lowerToBindAndAnnotateHandle(F);
}
+ /// Replace uses of \c V with the values in the `dx.ResRet` of \c Op. Since
we
+ /// expect to be post-scalarization, make an effort to avoid vectors.
+ Error replaceResRetUses(CallInst *I
https://github.com/bogner updated
https://github.com/llvm/llvm-project/pull/104252
>From 2f317012985068f7130cdf4976d8821924d404c3 Mon Sep 17 00:00:00 2001
From: Justin Bogner
Date: Mon, 9 Sep 2024 12:16:36 -0700
Subject: [PATCH 1/2] Improve comments, move code for clarity
Created using spr 1.3
@@ -259,6 +259,114 @@ class OpLowerer {
lowerToBindAndAnnotateHandle(F);
}
+ /// Replace uses of \c V with the values in the `dx.ResRet` of \c Op. Since
we
bogner wrote:
Nice catch, should be "Intrin", the name of the first parameter. Updated.
http
1 - 100 of 144 matches
Mail list logo
