Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-bootstrap-asan` running on `sanitizer-buildbot2` while
building `clang,llvm` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/
Author: Baranov Victor
Date: 2025-10-29T09:53:28+03:00
New Revision: 1bd0fdf1e6e211a7f26592d6c9877fba42118a08
URL:
https://github.com/llvm/llvm-project/commit/1bd0fdf1e6e211a7f26592d6c9877fba42118a08
DIFF:
https://github.com/llvm/llvm-project/commit/1bd0fdf1e6e211a7f26592d6c9877fba42118a08.diff
https://github.com/vbvictor closed
https://github.com/llvm/llvm-project/pull/164165
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/vbvictor closed
https://github.com/llvm/llvm-project/pull/164130
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Baranov Victor
Date: 2025-10-29T09:52:08+03:00
New Revision: 2f977613f226ef7866375a7aefa4c7c7730bfe22
URL:
https://github.com/llvm/llvm-project/commit/2f977613f226ef7866375a7aefa4c7c7730bfe22
DIFF:
https://github.com/llvm/llvm-project/commit/2f977613f226ef7866375a7aefa4c7c7730bfe22.diff
https://github.com/tbaederr closed
https://github.com/llvm/llvm-project/pull/165512
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Timm Baeder
Date: 2025-10-29T07:30:11+01:00
New Revision: a21521a4efacba405964767a8c2280b40aa68536
URL:
https://github.com/llvm/llvm-project/commit/a21521a4efacba405964767a8c2280b40aa68536
DIFF:
https://github.com/llvm/llvm-project/commit/a21521a4efacba405964767a8c2280b40aa68536.diff
L
https://github.com/tbaederr updated
https://github.com/llvm/llvm-project/pull/164941
>From cde792d4d439aeaf1bda84a929b348ba073bb017 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timm=20B=C3=A4der?=
Date: Fri, 24 Oct 2025 09:59:45 +0200
Subject: [PATCH] [clang] Adjust TextDiagnostic style ranges for
https://github.com/capitan-davide updated
https://github.com/llvm/llvm-project/pull/158706
>From 518ae97641b488ca8c07a703c88f2a585b55594b Mon Sep 17 00:00:00 2001
From: Davide Cunial
Date: Tue, 16 Sep 2025 07:19:34 +0200
Subject: [PATCH 1/3] [clang-tidy][NFC] Enable
'readability-simplify-boole
https://github.com/carlosgalvezp approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/164165
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
capitan-davide wrote:
I tried with option `SimplifyDemorganRelaxed`, here's the
[diffs](https://github.com/llvm/llvm-project/compare/518ae97641b488ca8c07a703c88f2a585b55594b...a5d4399d28040de1821fce030f9b97d7112a7997).
For older commit is set to false `false`, the newer commit is `true`
https:
https://github.com/capitan-davide updated
https://github.com/llvm/llvm-project/pull/158706
>From 518ae97641b488ca8c07a703c88f2a585b55594b Mon Sep 17 00:00:00 2001
From: Davide Cunial
Date: Tue, 16 Sep 2025 07:19:34 +0200
Subject: [PATCH 1/3] [clang-tidy][NFC] Enable
'readability-simplify-boole
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 origin/main HEAD --extensions cpp,c --
clang/lib/AST/ByteCode/InterpBuiltin.cpp clang
https://github.com/ahmednoursphinx updated
https://github.com/llvm/llvm-project/pull/165513
>From eca52c0e1d9e79911f79d7339926e295fcbcf84f Mon Sep 17 00:00:00 2001
From: ahmed
Date: Tue, 28 Oct 2025 23:49:56 +0300
Subject: [PATCH] feat: VectorExprEvaluator::VisitCallExpr / InterpretBuiltin -
A
llvmbot wrote:
@llvm/pr-subscribers-backend-x86
Author: Ahmed Nour (ahmednoursphinx)
Changes
This PR Resolves https://github.com/llvm/llvm-project/issues/165161
---
Full diff: https://github.com/llvm/llvm-project/pull/165513.diff
4 Files Affected:
- (modified) clang/include/clang/Basic
https://github.com/ahmednoursphinx created
https://github.com/llvm/llvm-project/pull/165513
This PR Resolves https://github.com/llvm/llvm-project/issues/165161
>From eca52c0e1d9e79911f79d7339926e295fcbcf84f Mon Sep 17 00:00:00 2001
From: ahmed
Date: Tue, 28 Oct 2025 23:49:56 +0300
Subject: [PA
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Timm Baeder (tbaederr)
Changes
Fixes https://github.com/llvm/llvm-project/issues/165372
---
Full diff: https://github.com/llvm/llvm-project/pull/165512.diff
2 Files Affected:
- (modified) clang/lib/AST/ByteCode/InterpBuiltin.cpp (+1-1)
https://github.com/tbaederr created
https://github.com/llvm/llvm-project/pull/165512
Fixes https://github.com/llvm/llvm-project/issues/165372
>From 1d9f5cc3eb936e92c766f3b2885097ee1dbab9a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timm=20B=C3=A4der?=
Date: Wed, 29 Oct 2025 06:46:21 +0100
Subjec
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
jinge90 wrote:
> > we have used them in intel/llvm
>
> Do they do anything useful for SYCL in https://github.com/llvm/llvm-project/?
Hi, @bader
The driver code handling -Xarch_device/host doesn't do specific things to SYCL
or CUDA, HIP :
https://github.com/llvm/llvm-project/blob/main/clang/l
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-armv8-quick` running
on `linaro-clang-armv8-quick` while building `clang,llvm` at step 5 "ninja
check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
ChuanqiXu9 wrote:
LGTM generally, so what's the problem for now?
https://github.com/llvm/llvm-project/pull/165341
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-quick`
running on `linaro-clang-aarch64-quick` while building `clang,llvm` at step 5
"ninja check 1".
Full details are available at:
https://lab.llvm.org/buildb
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `mlir-nvidia` running on
`mlir-nvidia` while building `clang,llvm` at step 7
"test-build-check-mlir-build-only-check-mlir".
Full details are available at:
https://lab.llvm.org
bader wrote:
> we have used them in intel/llvm
Do they do anything useful for SYCL in https://github.com/llvm/llvm-project/?
https://github.com/llvm/llvm-project/pull/165503
___
cfe-commits mailing list
[email protected]
https://lists.llvm.or
Timm =?utf-8?q?Bäder?=
Message-ID:
In-Reply-To:
https://github.com/tbaederr closed
https://github.com/llvm/llvm-project/pull/164935
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Timm Baeder
Date: 2025-10-29T06:16:59+01:00
New Revision: 09262656f32ab3f2e1d82e5342ba37eecac52522
URL:
https://github.com/llvm/llvm-project/commit/09262656f32ab3f2e1d82e5342ba37eecac52522
DIFF:
https://github.com/llvm/llvm-project/commit/09262656f32ab3f2e1d82e5342ba37eecac52522.diff
L
@@ -3622,6 +3622,15 @@ RValue CodeGenFunction::EmitBuiltinExpr(const GlobalDecl
GD, unsigned BuiltinID,
Builder.CreateArithmeticFence(ArgValue, ConvertType(ArgType)));
return RValue::get(ArgValue);
}
+ case Builtin::BI__builtin_bswapg: {
+Value *ArgValue =
https://github.com/clingfei updated
https://github.com/llvm/llvm-project/pull/162433
>From 92466f3789ce1849ebee8a405efd42e191c591f5 Mon Sep 17 00:00:00 2001
From: clingfei <[email protected]>
Date: Wed, 8 Oct 2025 15:05:44 +0800
Subject: [PATCH 01/13] [Clang] Add __builtin_bswapg
---
clang/inc
=?utf-8?q?Björn_Schäpers?= ,
=?utf-8?q?Björn_Schäpers?= ,
=?utf-8?q?Björn_Schäpers?=
Message-ID:
In-Reply-To:
https://github.com/owenca approved this pull request.
There are probably 30+ two (or three if you count `Style`) parameter version of
`verifyFormat` that can be replaced with the one-
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/163607
>From b2f00eb013f5174b1ab5199bb7cc4cab6d5ed059 Mon Sep 17 00:00:00 2001
From: Tom Stellard
Date: Sat, 11 Oct 2025 17:39:12 -0700
Subject: [PATCH 01/33] [Darwin][Driver] Prefer linking with toolchain's libc++
i
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-armv8-quick` running
on `linaro-clang-armv8-quick` while building `clang` at step 5 "ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/154/builds/23298
Here is the relevant piece o
ChuanqiXu9 wrote:
> Ok, bootstrap - assertions passes all tests for me, what is your bootstrap
> config?
LDFLAGS="-fuse-ld=lld -Wl,-q -Wl,-znow -Wl,-build-id=sha1" cmake -G Ninja
-DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=... -DCMAKE_CXX_COMPILER=...
-DCMAKE_C_FLAG="-fstack-clash-protection
https://github.com/owenca closed
https://github.com/llvm/llvm-project/pull/165351
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ChuanqiXu9 wrote:
After I add the following, the bootstrap build and test succeeded for me:
```
if (CGM.getCodeGenOpts().StrictVTablePointers && CXXThisValue) {
const CXXRecordDecl *ThisRecordDecl = MD->getParent();
bool IsPolymorphicObject = ThisRecordDecl->isPolymorphic();
Author: owenca
Date: 2025-10-28T20:16:24-07:00
New Revision: 3fc24a282a1092efca8a437719491dd4cb127426
URL:
https://github.com/llvm/llvm-project/commit/3fc24a282a1092efca8a437719491dd4cb127426
DIFF:
https://github.com/llvm/llvm-project/commit/3fc24a282a1092efca8a437719491dd4cb127426.diff
LOG: [
@@ -2249,6 +2283,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
else if (getLangOpts().C2y && OpTok.is(tok::kw__Countof))
Diag(OpTok, diag::warn_c2y_compat_keyword) << OpTok.getName();
+ if (OpTok.is(tok::caretcaret))
+return ParseCXXReflectExpressi
https://github.com/owenca edited
https://github.com/llvm/llvm-project/pull/165351
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca edited
https://github.com/llvm/llvm-project/pull/165351
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -2249,6 +2283,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
else if (getLangOpts().C2y && OpTok.is(tok::kw__Countof))
Diag(OpTok, diag::warn_c2y_compat_keyword) << OpTok.getName();
+ if (OpTok.is(tok::caretcaret))
+return ParseCXXReflectExpressi
@@ -2249,6 +2283,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
else if (getLangOpts().C2y && OpTok.is(tok::kw__Countof))
Diag(OpTok, diag::warn_c2y_compat_keyword) << OpTok.getName();
+ if (OpTok.is(tok::caretcaret))
+return ParseCXXReflectExpressi
jinge90 wrote:
Hi, @bader
-Xarch_device/host can work for SYCL and we have used them in intel/llvm, this
PR shows SYCL is supported in -Xarch_device/host help text.
Thanks very much.
https://github.com/llvm/llvm-project/pull/165503
___
cfe-commits ma
https://github.com/jinge90 edited
https://github.com/llvm/llvm-project/pull/165503
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (jinge90)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/165503.diff
1 Files Affected:
- (modified) clang/include/clang/Driver/Options.td (+2-2)
``diff
diff --git a/clang/include/clang/Driver/Options.t
https://github.com/jinge90 created
https://github.com/llvm/llvm-project/pull/165503
None
>From 3efc034ffdc00a86a52d0636d72fc1b30d98ac70 Mon Sep 17 00:00:00 2001
From: jinge90
Date: Wed, 29 Oct 2025 11:31:13 +0800
Subject: [PATCH] [Driver][NFC] Show SYCL support in -Xarch_device/host help
text
ojhunt wrote:
Ok, bootstrap - assertions passes all tests for me, what is your bootstrap
config?
https://github.com/llvm/llvm-project/pull/165341
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/c
4vtomat wrote:
Suspended for now since spec is not accepted by RVI yet
https://github.com/llvm/llvm-project/pull/164820
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/4vtomat updated
https://github.com/llvm/llvm-project/pull/164820
>From 0284d120e4d54693e8ef63e53bc8a42de3a08993 Mon Sep 17 00:00:00 2001
From: Brandon Wu
Date: Tue, 29 Apr 2025 13:54:26 +0800
Subject: [PATCH 1/4] [RISCV] Support Zvfofp4min assembler version 0.1
OFP4 conversi
https://github.com/HerrCai0907 approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/164130
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
HerrCai0907 wrote:
It is hard to understand double negation in `not-nothrow` part. At least we
should avoid it.
maybe `bugprone-exception-copy-constructor-throwable` WDYT?
https://github.com/llvm/llvm-project/pull/164061
___
cfe-commits mailing list
c
ojhunt wrote:
> And also, when bootstrapping, have you met errors like: `undefined symbol:
> clang::ImplicitConceptSpecializationDecl::~ImplicitConceptSpecializationDecl()`?
> There are other similar cases.
>
> The common point of these decl is, they have a virtual destructor but they
> don't
@@ -269,6 +269,12 @@ void AvoidCStyleCastsCheck::check(const
MatchFinder::MatchResult &Result) {
return;
}
break;
+ case CK_BaseToDerived:
+if (!needsConstCast(SourceType, DestType)) {
+ ReplaceWithNamedCast("static_cast");
+ return;
+}
+br
ChuanqiXu9 wrote:
And also, when bootstrapping, have you met errors like: `undefined symbol:
clang::ImplicitConceptSpecializationDecl::~ImplicitConceptSpecializationDecl()`?
There are other similar cases.
The common point of these decl is, they have a virtual destructor but they
don't have a
HerrCai0907 wrote:
> If the added option to to discourage writing such code, then there should not
> be not option at all and no warning for such cases but a separate check that
> warns about the pattern.
In theory true, but since c++ STL and Microsoft system header have conflict in
`min` / `
https://github.com/HerrCai0907 approved this pull request.
https://github.com/llvm/llvm-project/pull/165448
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/HerrCai0907 edited
https://github.com/llvm/llvm-project/pull/164827
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-l
@@ -0,0 +1,13 @@
+// RUN: %clang_cc1 %s -std=c++26 -freflection -fblocks -fsyntax-only
+
+struct A {
+ int operator^(int (^block)(int x)) const {
+return block(0);
+ }
+};
+
+
+int main()
+{
+(void)(A{}^^(int y){ return y + 1; });
Sirraide wrote:
(That
https://github.com/Sirraide edited
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,13 @@
+// RUN: %clang_cc1 %s -std=c++26 -freflection -fblocks -fsyntax-only
+
+struct A {
+ int operator^(int (^block)(int x)) const {
+return block(0);
+ }
+};
+
+
+int main()
+{
+(void)(A{}^^(int y){ return y + 1; });
Sirraide wrote:
Anothe
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-fast` running on `sanitizer-buildbot3` while building
`clang` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/169/builds/16472
Here is the relevant piece
https://github.com/Sirraide edited
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca updated
https://github.com/llvm/llvm-project/pull/165351
>From 85036b258697d6c279d9b8150530ef8d2f6e29b6 Mon Sep 17 00:00:00 2001
From: Owen Pan
Date: Mon, 27 Oct 2025 21:42:03 -0700
Subject: [PATCH 1/3] [clang-format] Fix a bug in annotating operator functions
Fixes #
@@ -3689,6 +3689,11 @@ defm application_extension :
BoolFOption<"application-extension",
PosFlag,
NegFlag>;
+defm reflection : BoolFOption<"reflection",
+ LangOpts<"Reflection">, DefaultFalse,
+ PosFlag,
+ NegFlag>;
Sirraide wrote:
```suggestion
NegFl
@@ -0,0 +1,78 @@
+//===--- ParseReflect.cpp - C++26 Reflection Parsing -===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apach
@@ -0,0 +1,13 @@
+// RUN: %clang_cc1 %s -std=c++26 -freflection -fblocks -fsyntax-only
+
+struct A {
+ int operator^(int (^block)(int x)) const {
+return block(0);
+ }
+};
+
+
+int main()
+{
+(void)(A{}^^(int y){ return y + 1; });
Sirraide wrote:
Also a
@@ -2249,6 +2283,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
else if (getLangOpts().C2y && OpTok.is(tok::kw__Countof))
Diag(OpTok, diag::warn_c2y_compat_keyword) << OpTok.getName();
+ if (OpTok.is(tok::caretcaret))
+return ParseCXXReflectExpressi
@@ -4946,6 +4946,12 @@ void CXXNameMangler::mangleExpression(const Expr *E,
unsigned Arity,
E = cast(E)->getSubExpr();
goto recurse;
+ case Expr::CXXReflectExprClass: {
+// TODO(Reflection): implement this after introducing std::meta::info
+// and add info in
@@ -0,0 +1,78 @@
+//===--- ParseReflect.cpp - C++26 Reflection Parsing -===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apach
https://github.com/Sirraide edited
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -5501,6 +5501,60 @@ class BuiltinBitCastExpr final
}
};
+/// Represents a C++26 reflect expression [expr.reflect]. The operand of the
+/// expression is either:
+/// - :: (global namespace),
+/// - a reflection-name,
+/// - a type-id, or
+/// - an id-expression.
+clas
@@ -7677,7 +7690,7 @@ class Parser : public CodeCompletionHandler {
/// [GNU] asm-clobbers:
/// asm-string-literal
/// asm-clobbers ',' asm-string-literal
- /// \endverbatim
+ /// \endverbatim
Sirraide wrote:
This change is back, so ca
@@ -2249,6 +2283,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
else if (getLangOpts().C2y && OpTok.is(tok::kw__Countof))
Diag(OpTok, diag::warn_c2y_compat_keyword) << OpTok.getName();
+ if (OpTok.is(tok::caretcaret))
+return ParseCXXReflectExpressi
https://github.com/Sirraide commented:
Yeah, I think we should be able to merge this soon.
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-comm
@@ -2189,8 +,9 @@ ExprResult Parser::ParseUnaryExprOrTypeTraitExpression() {
assert(Tok.isOneOf(tok::kw_sizeof, tok::kw___datasizeof, tok::kw___alignof,
tok::kw_alignof, tok::kw__Alignof, tok::kw_vec_step,
tok::kw___builtin_omp_re
https://github.com/fhahn closed https://github.com/llvm/llvm-project/pull/164821
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/fhahn edited https://github.com/llvm/llvm-project/pull/164821
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Florian Hahn
Date: 2025-10-28T19:03:17-07:00
New Revision: 53785846aa11bdecbbb683e1ebec9461539f1e97
URL:
https://github.com/llvm/llvm-project/commit/53785846aa11bdecbbb683e1ebec9461539f1e97
DIFF:
https://github.com/llvm/llvm-project/commit/53785846aa11bdecbbb683e1ebec9461539f1e97.diff
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (Sirraide)
Changes
Many editors and IDEs automatically delete trailing whitespace on save, and
this particular one has shown up as an unrelated change in several of my
patches that I then had to remove later (and I’ve seen it in othe
https://github.com/Men-cotton updated
https://github.com/llvm/llvm-project/pull/162105
>From 7a29a63fe2bfca5e7bf6af5ab2fd3f0ff1ea52cf Mon Sep 17 00:00:00 2001
From: mencotton
Date: Tue, 7 Oct 2025 23:14:20 +0900
Subject: [PATCH 1/5] [clang-format] Add SpaceInComments controls for block
comment
@@ -18,11 +18,66 @@
#include "clang/Basic/SourceLocation.h"
#include "clang/Basic/SourceManager.h"
#include "clang/Format/Format.h"
+#include "llvm/ADT/StringExtras.h"
#include "llvm/Support/Regex.h"
namespace clang {
namespace format {
+namespace {
+
+CommentKind classi
Author: Sirraide
Date: 2025-10-29T02:50:55+01:00
New Revision: eb40a0150251c724d5c51bef85ef8d9d59d5c462
URL:
https://github.com/llvm/llvm-project/commit/eb40a0150251c724d5c51bef85ef8d9d59d5c462
DIFF:
https://github.com/llvm/llvm-project/commit/eb40a0150251c724d5c51bef85ef8d9d59d5c462.diff
LOG:
https://github.com/Sirraide closed
https://github.com/llvm/llvm-project/pull/165498
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Sirraide created
https://github.com/llvm/llvm-project/pull/165498
Many editors and IDEs automatically delete trailing whitespace on save, and
this particular one has shown up as an unrelated change in several of my
patches that I then had to remove later (and I’ve seen it in
https://github.com/changkhothuychung updated
https://github.com/llvm/llvm-project/pull/164692
error: too big or took too long to generate
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commit
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-aarch64-windows`
running on `linaro-armv8-windows-msvc-05` while building `clang` at step 6
"test".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/141/builds/12594
Here is the relevant piece of
https://github.com/changkhothuychung edited
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Timm =?utf-8?q?B=C3=A4der?=
Message-ID:
In-Reply-To:
Sirraide wrote:
> aarch64 CI failure is unrelated.
Yeah, I ran into that too in one of my prs
https://github.com/llvm/llvm-project/pull/164935
___
cfe-commits mailing list
[email protected].
Timm =?utf-8?q?B=C3=A4der?=
Message-ID:
In-Reply-To:
https://github.com/Sirraide approved this pull request.
https://github.com/llvm/llvm-project/pull/164935
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mail
katzdm wrote:
I left a few more comments, but now I'm out of feedback. Looking forward to
seeing this land once maintainers are happy with it!! 🚀
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://github.com/boomanaiden154 approved this pull request.
https://github.com/llvm/llvm-project/pull/165448
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/changkhothuychung updated
https://github.com/llvm/llvm-project/pull/164692
error: too big or took too long to generate
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commit
@@ -0,0 +1,60 @@
+// RUN: %clang_cc1 %s -std=c++26 -freflection -fsyntax-only -verify
+
+namespace a {
+struct X {
+int y;
+bool operator==(const X& other)
+{
+return y == other.y;
+}
+};
+
+namespace b {
+struct Y {};
+int x;
+}
+
+template
+struct
https://github.com/katzdm edited
https://github.com/llvm/llvm-project/pull/164692
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
1 - 100 of 415 matches
Mail list logo
