@@ -537,7 +537,11 @@ AMDGPUTargetCodeGenInfo::getLLVMSyncScopeID(const
LangOptions &LangOpts,
break;
}
- if (Ordering != llvm::AtomicOrdering::SequentiallyConsistent) {
+ // OpenCL assumes by default that atomic scopes are per-address space for
+ // non-sequentially
@@ -537,7 +537,11 @@ AMDGPUTargetCodeGenInfo::getLLVMSyncScopeID(const
LangOptions &LangOpts,
break;
}
- if (Ordering != llvm::AtomicOrdering::SequentiallyConsistent) {
+ // OpenCL assumes by default that atomic scopes are per-address space for
+ // non-sequentially
https://github.com/dhruvachak edited
https://github.com/llvm/llvm-project/pull/120095
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -537,7 +537,11 @@ AMDGPUTargetCodeGenInfo::getLLVMSyncScopeID(const
LangOptions &LangOpts,
break;
}
- if (Ordering != llvm::AtomicOrdering::SequentiallyConsistent) {
+ // OpenCL assumes by default that atomic scopes are per-address space for
+ // non-sequentially
@@ -537,7 +537,11 @@ AMDGPUTargetCodeGenInfo::getLLVMSyncScopeID(const
LangOptions &LangOpts,
break;
}
- if (Ordering != llvm::AtomicOrdering::SequentiallyConsistent) {
+ // OpenCL assumes by default that atomic scopes are per-address space for
+ // non-sequentially
https://github.com/jhuber6 edited
https://github.com/llvm/llvm-project/pull/120095
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
b-sumner wrote:
OpenCL should only be using the amdgcn fence builtin. See, e.g.
https://github.com/ROCm/llvm-project/blob/amd-staging/amd/device-libs/opencl/src/misc/awif.cl#L73
https://github.com/llvm/llvm-project/pull/120095
___
cfe-commits maili
https://github.com/MaxEW707 updated
https://github.com/llvm/llvm-project/pull/99833
>From 0a705b1a8e9673cd5e803ffe392dacfa0f06c40f Mon Sep 17 00:00:00 2001
From: MaxEW707
Date: Fri, 21 Jun 2024 20:37:40 -0700
Subject: [PATCH 01/24] Support MSVC lvalue to temporary reference binding
---
clang/
Author: Ashley Coleman
Date: 2024-12-16T16:13:35-08:00
New Revision: 41a6e9cfd693c8570d48e73c5649d83ee6376b6d
URL:
https://github.com/llvm/llvm-project/commit/41a6e9cfd693c8570d48e73c5649d83ee6376b6d
DIFF:
https://github.com/llvm/llvm-project/commit/41a6e9cfd693c8570d48e73c5649d83ee6376b6d.diff
https://github.com/spall closed https://github.com/llvm/llvm-project/pull/117245
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/sarnex updated
https://github.com/llvm/llvm-project/pull/120145
>From e1b9b503b1e9b8ebf5a9c94dcefd0c47ab009019 Mon Sep 17 00:00:00 2001
From: "Sarnie, Nick"
Date: Mon, 16 Dec 2024 09:25:44 -0800
Subject: [PATCH 1/3] [Driver][clang-linker-wrapper] Add initial support for
Open
@@ -537,7 +537,8 @@ AMDGPUTargetCodeGenInfo::getLLVMSyncScopeID(const
LangOptions &LangOpts,
break;
}
- if (Ordering != llvm::AtomicOrdering::SequentiallyConsistent) {
+ if (LangOpts.OpenCL &&
jhuber6 wrote:
I'm sure it's using it somewhere since it'
https://github.com/shiltian updated
https://github.com/llvm/llvm-project/pull/104661
>From 9e23538a7cac72fe456fb039b5e0f321a0f3e142 Mon Sep 17 00:00:00 2001
From: Shilei Tian
Date: Mon, 16 Dec 2024 21:51:53 -0500
Subject: [PATCH] [Clang] Remove 3-element vector load and store special
handling
@@ -1846,6 +1846,16 @@ class TargetInfo : public TransferrableTargetInfo,
return std::make_pair(64, 64);
}
+ /// Returns the optimal vector type elements based on the provided vector
+ /// type. For example, on some targets, a vector with 3 elements may be
+ /// treat
@@ -1846,6 +1846,16 @@ class TargetInfo : public TransferrableTargetInfo,
return std::make_pair(64, 64);
}
+ /// Returns the optimal vector type elements based on the provided vector
+ /// type. For example, on some targets, a vector with 3 elements may be
+ /// treat
vsapsai wrote:
How does it work in Objective-C++? I don't know even if we have a test but hope
we do.
https://github.com/llvm/llvm-project/pull/119908
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-x86_64-debian-fast`
running on `gribozavr4` while building `clang` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/56/builds/14671
Here is the rel
jplehr wrote:
Is there the possibility to set up a buildbot for this architecture?
https://github.com/llvm/llvm-project/pull/120173
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib`
running on `gribozavr4` while building `clang` at step 6
"test-build-unified-tree-check-clang".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/60/builds/15369
Here is the r
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-sie-ubuntu-fast` running on `sie-linux-worker` while
building `clang` at step 6 "test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/144/builds/14100
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `premerge-monolithic-linux`
running on `premerge-linux-1` while building `clang` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/153/builds/17770
Here is
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Ryosuke Niwa (rniwa)
Changes
Reverts llvm/llvm-project#120123
Broke some tests.
---
Full diff: https://github.com/llvm/llvm-project/pull/120195.diff
1 Files Affected:
- (modified) clang/tools/scan-build/bin/scan-build (+1-3)
Author: Ryosuke Niwa
Date: 2024-12-16T23:36:26-08:00
New Revision: 6db1b2035bbef5ec477a1e645e249ebf7b29688c
URL:
https://github.com/llvm/llvm-project/commit/6db1b2035bbef5ec477a1e645e249ebf7b29688c
DIFF:
https://github.com/llvm/llvm-project/commit/6db1b2035bbef5ec477a1e645e249ebf7b29688c.diff
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-debian-cpp20`
running on `clang-debian-cpp20` while building `clang` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/108/builds/7214
Here is the r
https://github.com/rniwa closed https://github.com/llvm/llvm-project/pull/120195
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/chestnykh updated
https://github.com/llvm/llvm-project/pull/120013
>From 9422b097ff80f5501dcf4fa3d41176b9439ab3f6 Mon Sep 17 00:00:00 2001
From: Dmitry Chestnykh
Date: Sun, 15 Dec 2024 21:18:23 +0300
Subject: [PATCH 1/3] [Libunwind] Don't XFAIL tests with msan
---
libunwind
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-gcc-ubuntu` running on `sie-linux-worker3` while building
`clang` at step 6 "test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/174/builds/10204
Her
https://github.com/rniwa created
https://github.com/llvm/llvm-project/pull/120195
Reverts llvm/llvm-project#120123
Broke some tests.
>From b2b261c406108390117e1b6c3fdbe5e9d53a7111 Mon Sep 17 00:00:00 2001
From: Ryosuke Niwa
Date: Mon, 16 Dec 2024 23:35:54 -0800
Subject: [PATCH] =?UTF-8?q?Rever
@@ -53,3 +53,16 @@
// RUN: %clang -target aarch64 -march=armv9.6a+sve-f16f32mm -### -c %s 2>&1 |
FileCheck -check-prefix=V96A-SVE-F16F32MM %s
// RUN: %clang -target aarch64 -march=armv9.6-a+sve-f16f32mm -### -c %s 2>&1 |
FileCheck -check-prefix=V96A-SVE-F16F32MM %s
// V96A-SV
https://github.com/bevin-hansson updated
https://github.com/llvm/llvm-project/pull/120099
>From 16bd4a00feec97ae65a14600caf6921045d54833 Mon Sep 17 00:00:00 2001
From: Bevin Hansson
Date: Mon, 16 Dec 2024 16:40:06 +0100
Subject: [PATCH 1/2] [clangd] Augment code completion results with
documen
bevin-hansson wrote:
> > I'm not entirely sure how to add to the tests for clangd. Any advice?
>
> We have GTest unit tests for code completion in `CodeCompleteTests.cpp`.
> [This
> test](https://searchfox.org/llvm/rev/2df48fa78b496a2d276aa848598634bb2aad6857/clang-tools-extra/clangd/unittests
@@ -0,0 +1,324 @@
+# NOTE: Assertions have been autogenerated by utils/update_mca_test_checks.py
MaskRay wrote:
update_mca_test_checks.py is only for llvm-mca. Seems wrong usage?
There is now update_mc_test_checks.py . You can also do `%extract-encodings`
like
HighCommander4 wrote:
> I'm not entirely sure how to add to the tests for clangd. Any advice?
We have GTest unit tests for code completion in `CodeCompleteTests.cpp`. [This
test](https://searchfox.org/llvm/rev/2df48fa78b496a2d276aa848598634bb2aad6857/clang-tools-extra/clangd/unittests/CodeCompl
https://github.com/HerrCai0907 approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/119974
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-aarch64-linux-bootstrap-hwasan` running on `sanitizer-buildbot11`
while building `clang` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/55/builds/4421
Here is the rel
301 - 335 of 335 matches
Mail list logo