github-actions[bot] wrote:
@yichi170 Congratulations on having your first Pull Request (PR) merged into
the LLVM Project!
Your changes will be combined with recent changes from other authors, then
tested
by our [build bots](https://lab.llvm.org/buildbot/). If there is a problem with
a build
https://github.com/cor3ntin closed
https://github.com/llvm/llvm-project/pull/99075
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Yi-Chi Lee
Date: 2024-07-24T08:56:37+02:00
New Revision: fad17b43dbc09ac7e0a95535459845f72c2b739a
URL:
https://github.com/llvm/llvm-project/commit/fad17b43dbc09ac7e0a95535459845f72c2b739a
DIFF:
https://github.com/llvm/llvm-project/commit/fad17b43dbc09ac7e0a95535459845f72c2b739a.diff
LO
cor3ntin wrote:
LGTM too!
Thanks for the fix :)
https://github.com/llvm/llvm-project/pull/99075
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
+ using namespace ast_matchers;
+
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
+ using namespace ast_matchers;
+
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
martinboehme wrote
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
+ using namespace ast_matchers;
+
https://github.com/martinboehme requested changes to this pull request.
https://github.com/llvm/llvm-project/pull/99616
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
+ using namespace ast_matchers;
+
@@ -442,6 +442,46 @@ TEST_F(EnvironmentTest,
CXXDefaultInitExprResultObjIsWrappedExprResultObj) {
&Env.getResultObjectLocation(*DefaultInit->getExpr()));
}
+TEST_F(EnvironmentTest, ResultObjectLocationForInheritedCtorInitExpr) {
+ using namespace ast_matchers;
+
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
https://github.com/tbaederr closed
https://github.com/llvm/llvm-project/pull/100062
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Timm Baeder
Date: 2024-07-24T08:09:06+02:00
New Revision: dbe308c000f3401cbf6bb55f2b8d606fe091dcfe
URL:
https://github.com/llvm/llvm-project/commit/dbe308c000f3401cbf6bb55f2b8d606fe091dcfe
DIFF:
https://github.com/llvm/llvm-project/commit/dbe308c000f3401cbf6bb55f2b8d606fe091dcfe.diff
L
https://github.com/owenca approved this pull request.
https://github.com/llvm/llvm-project/pull/93140
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca edited https://github.com/llvm/llvm-project/pull/93140
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/yetingk edited
https://github.com/llvm/llvm-project/pull/99849
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
goldsteinn wrote:
ping
https://github.com/llvm/llvm-project/pull/91101
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvmbot wrote:
@llvm/pr-subscribers-clang-codegen
@llvm/pr-subscribers-clang
Author: Allen (vfdff)
Changes
Follow PR96025, except expf, more FP math libcalls in libm should also be
supported.
Fix https://github.com/llvm/llvm-project/issues/86635
---
Full diff: https://github.com/llvm/ll
https://github.com/vfdff created
https://github.com/llvm/llvm-project/pull/100302
Follow PR96025, except expf, more FP math libcalls in libm should also be
supported.
Fix https://github.com/llvm/llvm-project/issues/86635
>From c750234674531788ee26958954a5f9a6b59ea866 Mon Sep 17 00:00:00 2001
https://github.com/owenca updated
https://github.com/llvm/llvm-project/pull/93140
>From 09bd1f04730f0accad7ce041b0121f716cc7a18d Mon Sep 17 00:00:00 2001
From: Gedare Bloom
Date: Tue, 21 May 2024 22:21:59 -0600
Subject: [PATCH 01/13] [clang-format] Improve BlockIndent at ColumnLimit
Fixes #557
owenca wrote:
> Fixes #73584
Seems it's not fixed yet:
```
$ cat test.cpp
{
PyObjectPtr const readinto_method_obj{
PyObject_GetAttrString(input_stream, "readinto")};
}
$ clang-format test.cpp
{
PyObjectPtr const
readinto_method_obj{PyObject_GetAttrString(input_stream, "readi
MaskRay wrote:
> Aren't hashes supposed to be deterministic ?
>
> Can we add a override for builds with asserts turned ON to favor determinism ?
>
> Could have an API to set the determinism flag ?
>
> This also has an effect on Build ID computation ?
Some hashes are supposed to be determinist
Author: Fangrui Song
Date: 2024-07-23T21:57:21-07:00
New Revision: 6461e537815f7fa68cef06842505353cf5600e9c
URL:
https://github.com/llvm/llvm-project/commit/6461e537815f7fa68cef06842505353cf5600e9c
DIFF:
https://github.com/llvm/llvm-project/commit/6461e537815f7fa68cef06842505353cf5600e9c.diff
@@ -5813,6 +5813,27 @@ static TypoCorrection TryTypoCorrectionForCall(Sema &S,
Expr *Fn,
return TypoCorrection();
}
+// [C++26][[expr.unary.op]/p4
+// A pointer to member is only formed when an explicit &
+// is used and its operand is a qualified-id not enclosed in parenth
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `premerge-monolithic-linux`
running on `premerge-linux-1` while building `clang-tools-extra` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/153/builds/402
https://github.com/yichi170 updated
https://github.com/llvm/llvm-project/pull/99075
>From 60a8a36851bcb0e73228ec4941f1906d0e5b7ba9 Mon Sep 17 00:00:00 2001
From: yichi170
Date: Wed, 17 Jul 2024 02:15:43 +0800
Subject: [PATCH] [clang] replaced the usage of `asctime` with `std::put_time`
---
cl
hekota wrote:
Thanks @pow2clk !
https://github.com/llvm/llvm-project/pull/100017
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,65 @@
+// REQUIRES: system-windows
+
+// RUN: rm -rf %t
+// RUN: mkdir -p %t
+// RUN: split-file %s %t
+
+// RUN: %clang_cl /std:c++20 --precompile "%/t/Hello.cppm" "/Fo%/t/Hello.pcm"
ChuanqiXu9 wrote:
Oh, sorry. It turns to be my bad. We should check
jhuber6 wrote:
> I think LLVM generally doesn't follow the convention that `-a x` and
> `--abc=x`?
`cl::opt` options are arbitrary, but this isn't about convention really, it's
for things like `-Xoffload-linker -Wl,-plugin-opt=blah` not being passed
correctly.
https://github.com/llvm/llvm-pr
https://github.com/shiltian commented:
I think LLVM generally doesn't follow the convention that `-a x` and `--abc=x`?
https://github.com/llvm/llvm-project/pull/100270
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
yichi170 wrote:
I don't have write access, so if the PR is ready, please help me land it!
If there is anything that I need to do, please let me know!
https://github.com/llvm/llvm-project/pull/99075
___
cfe-commits mailing list
cfe-commits@lists.llvm.or
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-x86_64-debian-fast`
running on `gribozavr4` while building `clang-tools-extra` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/56/builds/3219
Here
https://github.com/yichi170 edited
https://github.com/llvm/llvm-project/pull/99075
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/yichi170 edited
https://github.com/llvm/llvm-project/pull/99075
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -26,24 +27,38 @@ static cl::opt
NoF16Math("nvptx-no-f16-math", cl::Hidden,
cl::desc("NVPTX Specific: Disable generation of f16 math ops."),
cl::init(false));
+static cl::opt
+NextSM("nvptx-next-sm", cl::Hidden,
+ cl::desc("NVPTX
https://github.com/MitalAshok updated
https://github.com/llvm/llvm-project/pull/95112
>From e53dfbc9b2c6b7f30c1378731d7de284fa99d568 Mon Sep 17 00:00:00 2001
From: Mital Ashok
Date: Tue, 11 Jun 2024 14:26:38 +0100
Subject: [PATCH 1/7] [Clang] Implement CWG2813
---
clang/docs/ReleaseNotes.rst
https://github.com/MitalAshok updated
https://github.com/llvm/llvm-project/pull/97200
>From 0dea95701ca4dfca9b7d0bd889003fc35aa3017e Mon Sep 17 00:00:00 2001
From: Mital Ashok
Date: Sun, 30 Jun 2024 10:39:15 +0100
Subject: [PATCH 01/12] [NFC] [Clang] Some core issues have changed status from
t
https://github.com/MitalAshok updated
https://github.com/llvm/llvm-project/pull/97200
>From 0dea95701ca4dfca9b7d0bd889003fc35aa3017e Mon Sep 17 00:00:00 2001
From: Mital Ashok
Date: Sun, 30 Jun 2024 10:39:15 +0100
Subject: [PATCH 01/11] [NFC] [Clang] Some core issues have changed status from
t
@@ -139,7 +139,7 @@ struct D3 : B {
#endif
#if __cplusplus >= 202302L
-namespace cwg2561 { // cwg2561: no tentatively ready 2024-03-18
+namespace cwg2561 { // cwg2561: no ready 2024-06-25
MitalAshok wrote:
It doesn't really make sense to put a date for someth
@@ -1,5 +1,6 @@
// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%itanium_abi_triple -verify %s -DN=1
// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%itanium_abi_triple -verify %s -DN=2
+// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%i
@@ -1,5 +1,6 @@
// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%itanium_abi_triple -verify %s -DN=1
// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%itanium_abi_triple -verify %s -DN=2
+// RUN: %clang_cc1 -emit-llvm-only -x c++ -std=c++11 -triple
%i
https://github.com/ahatanak updated
https://github.com/llvm/llvm-project/pull/100204
>From 4cbbf9ee2c5afaa3818c10ab6f2645353da94a8c Mon Sep 17 00:00:00 2001
From: Akira Hatanaka
Date: Tue, 23 Jul 2024 11:55:57 -0700
Subject: [PATCH 1/2] [PAC] Define __builtin_ptrauth_type_discriminator
The bui
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-aarch64-sve-vls-2stage` running on `linaro-g3-01` while building
`clang-tools-extra` at step 12 "ninja check 2".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/4/builds/898
Here is the relevant
chrisnc wrote:
@AaronBallman yes, that would be great! I'm just a contributor, not a
collaborator.
https://github.com/llvm/llvm-project/pull/97534
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r
ef8de68faebee0226b4836e66574f225f724e768...cbcf4b3fb0ccad7eea5c1672b90a564e707028f6
cross
https://github.com/andykaylor updated
https://github.com/llvm/llvm-project/pull/99723
>From 869385fd8d7738b041149d88d5f427b5039c5921 Mon Sep 17 00:00:00 2001
From: Andy Kaylor
Date: Mon, 6 May 2024 10:07:52 -0700
Subject: [PATCH 1/3] [Driver] Clean up fp-contract handling in clang driver
This
https://github.com/sayhaan updated
https://github.com/llvm/llvm-project/pull/100282
>From 8824746a8fe2390a6cb35075f2595f0a6c9586f0 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Tue, 1 Jun 2021 11:37:41 -0700
Subject: [PATCH 1/3] Rebase: [Facebook] Add clang driver options to test debug
info
https://github.com/sayhaan created
https://github.com/llvm/llvm-project/pull/100282
Enables parallelization for the processing of DWO CUs.
>From 11fff0b2d1868f1e8fce988b2b41a38de42dff61 Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Tue, 1 Jun 2021 11:37:41 -0700
Subject: [PATCH 1/5] Rebase:
JustinStitt wrote:
> > Right, unsigned overflow is well-defined. This isn't about the semantics of
> > "undefined-ness". We want the unsigned sanitizer ON but some of the things
> > it reports are noisy -- that's what this PR is about
>
> "Idiom" seems to vague to me. kernel has own opinion on
https://github.com/Artem-B edited
https://github.com/llvm/llvm-project/pull/100247
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -648,6 +658,13 @@ void NVPTX::getNVPTXTargetFeatures(const Driver &D, const
llvm::Triple &Triple,
Features.push_back(Args.MakeArgString(PtxFeature));
return;
}
+ // Add --cuda-next-ptx to the list of features, but carry on to add the
+ // default PTX feature for
vitalybuka wrote:
> Right, unsigned overflow is well-defined. This isn't about the semantics of
> "undefined-ness". We want the unsigned sanitizer ON but some of the things it
> reports are noisy -- that's what this PR is about
"Idiom" seems to vague to me. kernel has own opinion on what is i
JustinStitt wrote:
> I assume you are going to change fronted to avoid compiler abusing these UBs?
Well, like you said, none of this is really undefined behavior and isn't
getting optimized away. The exception being `if ( a + b < a )` which can
definitely have some unexpected results with high
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/3201
Here is the relev
JustinStitt wrote:
> Actually stuff like unsigned overflows are not UB.
>
> Maybe instead of `-fno-sanitize-overflow-idioms` we convert into
> `unsigned-integer-overflow` into ` check group` so user can
> -fno-sanitize=-unsigned-integer-overflow
Right, unsigned overflow is well-defined. This
https://github.com/jhuber6 closed
https://github.com/llvm/llvm-project/pull/98170
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Joseph Huber
Date: 2024-07-23T18:30:30-05:00
New Revision: 4f516aa04be616f3ad2929b275e7dc7da9b90d0a
URL:
https://github.com/llvm/llvm-project/commit/4f516aa04be616f3ad2929b275e7dc7da9b90d0a
DIFF:
https://github.com/llvm/llvm-project/commit/4f516aa04be616f3ad2929b275e7dc7da9b90d0a.diff
@@ -312,6 +312,38 @@ This attribute may not be
supported by other compilers, so consider using it together with
``#if defined(__clang__)``.
+Disabling instrumentation of common overflow idioms
+=
+
+There are certain overflow
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-ppc64le-linux-multistage` running on `ppc64le-clang-multistage-test`
while building `clang-tools-extra` at step 5 "ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/76/builds/1281
@@ -648,6 +658,13 @@ void NVPTX::getNVPTXTargetFeatures(const Driver &D, const
llvm::Triple &Triple,
Features.push_back(Args.MakeArgString(PtxFeature));
return;
}
+ // Add --cuda-next-ptx to the list of features, but carry on to add the
+ // default PTX feature for
vitalybuka wrote:
> I assume you are going to change fronted to avoid compiler abusing these UBs?
Actually stuff like unsigned overflows are not UB.
Maybe instead of `-fno-sanitize-overflow-idioms` we convert into
`unsigned-integer-overflow` into ` check group` so user can
-fno-sanitize=-uns
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 ce811fb6d94e1d4af1fd1f52fbf109bc34834970
1d9084e9c246d2fcb395c329c6cf1ca19ef032aa --e
@@ -96,6 +96,7 @@ static const OffloadArchToStringMap arch_names[] = {
SM(89), // Ada Lovelace
SM(90), // Hopper
SM(90a), // Hopper
+SM(next),// Placeholder for a n
llvmbot wrote:
@llvm/pr-subscribers-backend-arm
@llvm/pr-subscribers-clang
Author: None (SpencerAbson)
Changes
This patch moves NEON immediate argument specification and checking to the
system currently shared by both SVE and SME. As a result, NEON instructions
that take immediate argum
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-clang-x86_64-darwin`
running on `doug-worker-3` while building `clang-tools-extra` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/23/builds/1319
He
https://github.com/vitalybuka edited
https://github.com/llvm/llvm-project/pull/100272
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -312,6 +312,38 @@ This attribute may not be
supported by other compilers, so consider using it together with
``#if defined(__clang__)``.
+Disabling instrumentation of common overflow idioms
+=
+
+There are certain overflow
@@ -96,6 +96,7 @@ static const OffloadArchToStringMap arch_names[] = {
SM(89), // Ada Lovelace
SM(90), // Hopper
SM(90a), // Hopper
+SM(next),// Placeholder for a n
https://github.com/jhuber6 updated
https://github.com/llvm/llvm-project/pull/98170
>From 69811ec62c70a55b398f6cd71dd4f73162bb64d1 Mon Sep 17 00:00:00 2001
From: Joseph Huber
Date: Tue, 9 Jul 2024 10:15:35 -0500
Subject: [PATCH 1/2] [Clang] Make the GPU toolchains implicitly link `-lm` and
`-lc
kparzysz wrote:
Linux failure went away, but a Windows issue was introduced upstream in the
meantime. None of that has to do with this PR.
https://github.com/llvm/llvm-project/pull/100162
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https:
vitalybuka wrote:
I assume you are going to change fronted to avoid compiler abusing these UBs?
https://github.com/llvm/llvm-project/pull/100272
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe
https://github.com/kparzysz closed
https://github.com/llvm/llvm-project/pull/100162
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Krzysztof Parzyszek
Date: 2024-07-23T18:11:27-05:00
New Revision: 51507046c0e35eb04bbd90c79f6f3e5f31fe3dad
URL:
https://github.com/llvm/llvm-project/commit/51507046c0e35eb04bbd90c79f6f3e5f31fe3dad
DIFF:
https://github.com/llvm/llvm-project/commit/51507046c0e35eb04bbd90c79f6f3e5f31fe3dad
https://github.com/rnk approved this pull request.
Thanks, looks good, I'll wait for premerge checks to come back green before I
merge it.
https://github.com/llvm/llvm-project/pull/97792
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://
https://github.com/JustinStitt updated
https://github.com/llvm/llvm-project/pull/100272
>From 06b702cd38943314b2e6f873e64d70baed6f57f7 Mon Sep 17 00:00:00 2001
From: Justin Stitt
Date: Tue, 23 Jul 2024 20:21:49 +
Subject: [PATCH 1/3] implement idiom exclusions
Add flag `-fno-sanitize-overf
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 8bdc3d9ebb19e8c455c77241ef52ea74be6acfed
1dd1cbb1b13d0b038fa511620af993238a5bb260 --e
https://github.com/JustinStitt edited
https://github.com/llvm/llvm-project/pull/100272
___
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 `clang-debian-cpp20`
running on `clang-debian-cpp20` while building `clang-tools-extra` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/108/builds/1641
He
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-ppc64le-linux-test-suite` running on `ppc64le-clang-test-suite` while
building `clang-tools-extra` at step 6 "test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/9
https://github.com/JustinStitt edited
https://github.com/llvm/llvm-project/pull/100272
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Justin Stitt (JustinStitt)
Changes
## Summary
Introduce `-fno-sanitize-overflow-idioms` which disables sanitizer
instrumentation for common overflow-dependent code idioms.
## Background
For a wide selection of projects, proper over
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Justin Stitt (JustinStitt)
Changes
## Summary
Introduce `-fno-sanitize-overflow-idioms` which disables sanitizer
instrumentation for common overflow-dependent code idioms.
## Background
For a wide selection of projects, proper overflow sa
https://github.com/JustinStitt created
https://github.com/llvm/llvm-project/pull/100272
## Summary
Introduce `-fno-sanitize-overflow-idioms` which disables sanitizer
instrumentation for common overflow-dependent code idioms.
## Background
For a wide selection of projects, proper overflow sanit
llvmbot wrote:
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-clang-driver
Author: Joseph Huber (jhuber6)
Changes
Summary:
We have the `-Xoffload-linker=triple=arg` syntax that split the argument
meant only for a single toolchain. However this borke if it was an `a=b`
type argument. Make
https://github.com/jhuber6 created
https://github.com/llvm/llvm-project/pull/100270
Summary:
We have the `-Xoffload-linker=triple=arg` syntax that split the argument
meant only for a single toolchain. However this borke if it was an `a=b`
type argument. Make it only treat it like a triple if it'
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-solaris11-sparcv9`
running on `solaris11-sparcv9` while building `clang-tools-extra` at step 5
"ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/13/builds/1007
Here is the relevan
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-sve-vla`
running on `linaro-g3-02` while building `clang-tools-extra` at step 7 "ninja
check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/17/builds/1253
Here is the relevant piece
@@ -96,6 +96,7 @@ static const OffloadArchToStringMap arch_names[] = {
SM(89), // Ada Lovelace
SM(90), // Hopper
SM(90a), // Hopper
+SM(next),// Placeholder for a n
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-ppc64be-linux-test-suite` running on `ppc64be-clang-test-suite` while
building `clang-tools-extra` at step 6 "test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/1
https://github.com/PeterChou1 closed
https://github.com/llvm/llvm-project/pull/100260
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: PeterChou1
Date: 2024-07-23T18:55:25-04:00
New Revision: fb55db5482dd5bee1c8d78cc1b0ddd9517e97e17
URL:
https://github.com/llvm/llvm-project/commit/fb55db5482dd5bee1c8d78cc1b0ddd9517e97e17
DIFF:
https://github.com/llvm/llvm-project/commit/fb55db5482dd5bee1c8d78cc1b0ddd9517e97e17.diff
LO
https://github.com/Artem-B updated
https://github.com/llvm/llvm-project/pull/100247
>From 44a1045eee71777fa916e2a8043b2f99afc96a96 Mon Sep 17 00:00:00 2001
From: Artem Belevich
Date: Thu, 18 Jul 2024 15:05:01 -0700
Subject: [PATCH 1/2] [CUDA] Add a pseudo GPU sm_next which allows overrides
for
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
Author: None (PeterChou1)
Changes
This patch fixes the broken test caused by clang-doc which was caused by
https://github.com/llvm/llvm-project/pull/100251
https://lab.llvm.org/buildbot/#/builders/144/builds/3080
---
Full diff: https
rnk wrote:
I'm not seeing how your example constitutes an ODR violation, or how merging
these lambda types by mangled name is incorrect. They are equivalent in your
example. It seems like the issue has more to do with the details of how exactly
we do the merge, and where the metadata reference
https://github.com/PeterChou1 created
https://github.com/llvm/llvm-project/pull/100260
This patch fixes the broken test caused by clang-doc which was caused by
https://github.com/llvm/llvm-project/pull/100251
https://lab.llvm.org/buildbot/#/builders/144/builds/3080
>From 72911ee0060d300a39359
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-quick`
running on `linaro-clang-aarch64-quick` while building `clang-tools-extra` at
step 5 "ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/65/builds/1855
Here is the re
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-armv8-quick` running
on `linaro-clang-armv8-quick` while building `clang-tools-extra` at step 5
"ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/154/builds/1844
Here is the relev
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-clang-aarch64-darwin`
running on `doug-worker-4` while building `clang-tools-extra` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/190/builds/2508
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-tools-extra` at step 6 "test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/174/builds
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-clang-x86_64-sie-win`
running on `sie-win-worker` while building `clang-tools-extra` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/46/builds/2175
1 - 100 of 547 matches
Mail list logo
