https://github.com/MaskRay approved this pull request.
https://github.com/llvm/llvm-project/pull/143124
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -325,13 +325,30 @@ bool ContinuationIndenter::canBreak(const LineState
&State) {
if (Current.isMemberAccess() && CurrentState.ContainsUnwrappedBuilder)
return false;
- // Don't create a 'hanging' indent if there are multiple blocks in a single
- // statement and we
https://github.com/mdavis36 updated
https://github.com/llvm/llvm-project/pull/143839
>From c1e9c253b863297e5e245ae9a484f4275bb1187d Mon Sep 17 00:00:00 2001
From: mdavis36
Date: Wed, 11 Jun 2025 22:32:30 -0700
Subject: [PATCH] Remove "explicitly" from ambiguous documentaion on
[[clang::no_spec
@@ -325,13 +325,30 @@ bool ContinuationIndenter::canBreak(const LineState
&State) {
if (Current.isMemberAccess() && CurrentState.ContainsUnwrappedBuilder)
return false;
- // Don't create a 'hanging' indent if there are multiple blocks in a single
- // statement and we
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Michael Davis (mdavis36)
Changes
# Summary
This PR resolves issue #143719.
- Removes "explcitly" from the documentation on `[[clang::no_specialization]]`
to better match behavior of specialization as defined by the C++ standard.
---
Full
@@ -325,13 +325,30 @@ bool ContinuationIndenter::canBreak(const LineState
&State) {
if (Current.isMemberAccess() && CurrentState.ContainsUnwrappedBuilder)
return false;
- // Don't create a 'hanging' indent if there are multiple blocks in a single
- // statement and we
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
https://github.com/mdavis36 created
https://github.com/llvm/llvm-project/pull/143839
# Summary
This PR resolves issue #143719.
- Removes "explcitly" from the documentation on `[[clang::no_specialization]]`
to better match behavior of specialization as defined by the C++ standard.
>From c1e9c2
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `ppc64le-flang-rhel-clang`
running on `ppc64le-flang-rhel-test` while building `clang-tools-extra,llvm` at
step 6 "test-build-unified-tree-check-flang".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/1
https://github.com/shafik commented:
I would also like to see some more background info on how we came up with the
original limit (if it exists).
https://github.com/llvm/llvm-project/pull/143785
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://github.com/anchuraj edited
https://github.com/llvm/llvm-project/pull/143769
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143769
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/4] [flang][flang-driver] atomic control support
---
clang/i
ziqingluo-90 wrote:
I do not have many suggestions for this change. It's great that we can get rid
of the meaningless `nullability.NullabilityBase` dummy checker. Thanks.
https://github.com/llvm/llvm-project/pull/143735
___
cfe-commits mailing list
https://github.com/cyndyishida updated
https://github.com/llvm/llvm-project/pull/143817
>From 11b78ef3b9464aba1e54dcf9c18fceea359d16eb Mon Sep 17 00:00:00 2001
From: Cyndy Ishida
Date: Wed, 11 Jun 2025 17:20:20 -0700
Subject: [PATCH] [clang][darwin] Fix assertion failure when reporting fatal
e
@@ -113,25 +114,21 @@ class NullabilityChecker
void printState(raw_ostream &Out, ProgramStateRef State, const char *NL,
const char *Sep) const override;
- enum CheckKind {
-CK_NullPassedToNonnull,
-CK_NullReturnedFromNonnull,
-CK_NullableDerefe
tbaederr wrote:
The linked standard says:
> Full-expressions evaluated within a core constant expression
> ([[expr.const]](https://eel.is/c++draft/expr.const)) [1 048
> 576][.](https://eel.is/c++draft/implimits#1.39.sentence-1)
Is that actually what the "steps" in clang refer to? We seem to ch
https://github.com/mdfazlay closed
https://github.com/llvm/llvm-project/pull/143442
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Fazlay Rabbi
Date: 2025-06-11T22:06:11-07:00
New Revision: 02550da932913bd7c3987c68abc9060c9e5bde2c
URL:
https://github.com/llvm/llvm-project/commit/02550da932913bd7c3987c68abc9060c9e5bde2c
DIFF:
https://github.com/llvm/llvm-project/commit/02550da932913bd7c3987c68abc9060c9e5bde2c.diff
https://github.com/jeremyd2019 closed
https://github.com/llvm/llvm-project/pull/138351
___
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
Author: Shafik Yaghmour (shafik)
Changes
Static analysis flagged Input as a large object that would benefit from being
moved over being copied.
---
Full diff: https://github.com/llvm/llvm-project/pull/143830.diff
1 Files Affected:
- (modified)
https://github.com/shafik created
https://github.com/llvm/llvm-project/pull/143830
Static analysis flagged Input as a large object that would benefit from being
moved over being copied.
>From ea85dd226ad4c8a6f9ef0a7f16c22fdc386c1334 Mon Sep 17 00:00:00 2001
From: Shafik Yaghmour
Date: Wed, 11
@@ -6726,17 +6726,67 @@ QualType ASTContext::getTagDeclType(const TagDecl
*Decl) const {
return getTypeDeclType(const_cast(Decl));
}
+// Inject __size_t, __signed_size_t, and __ptrdiff_t to provide portable hints
+// and diagnostics. In C and C++, expressions of type size_t
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Shafik Yaghmour (shafik)
Changes
Static analysis flagged FatbinFileName since we can move it instead of copying
it.
---
Full diff: https://github.com/llvm/llvm-project/pull/143827.diff
1 Files Affected:
- (modified) clang/lib/Interpret
https://github.com/shafik created
https://github.com/llvm/llvm-project/pull/143827
Static analysis flagged FatbinFileName since we can move it instead of copying
it.
>From 5fd6d2ff512a971b8e6ad8f900c31a1b74b49ed5 Mon Sep 17 00:00:00 2001
From: Shafik Yaghmour
Date: Wed, 11 Jun 2025 20:58:07 -
Author: Chuanqi Xu
Date: 2025-06-12T11:48:09+08:00
New Revision: f09050fdc85074869f0b34f0d9e061a74ef549ee
URL:
https://github.com/llvm/llvm-project/commit/f09050fdc85074869f0b34f0d9e061a74ef549ee
DIFF:
https://github.com/llvm/llvm-project/commit/f09050fdc85074869f0b34f0d9e061a74ef549ee.diff
LO
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143441
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/3] [flang][flang-driver] atomic control support
---
clang/i
@@ -18,6 +18,53 @@
using namespace llvm;
using namespace AMDGPU;
+/// Find KV in array using binary search.
+static const BasicSubtargetSubTypeKV *
+Find(StringRef S, ArrayRef A) {
MaskRay wrote:
`find` (functionName in new code)
https://github.com/llvm/llvm
@@ -18,6 +18,53 @@
using namespace llvm;
using namespace AMDGPU;
+/// Find KV in array using binary search.
+static const BasicSubtargetSubTypeKV *
+Find(StringRef S, ArrayRef A) {
+ // Binary search the array
+ auto F = llvm::lower_bound(A, S);
+ // If not found then retur
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143441
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/3] [flang][flang-driver] atomic control support
---
clang/i
Author: Chuanqi Xu
Date: 2025-06-12T10:48:34+08:00
New Revision: bb3b8306dc226c4dc4dfde36444b43476eea66ee
URL:
https://github.com/llvm/llvm-project/commit/bb3b8306dc226c4dc4dfde36444b43476eea66ee
DIFF:
https://github.com/llvm/llvm-project/commit/bb3b8306dc226c4dc4dfde36444b43476eea66ee.diff
LO
https://github.com/shafik commented:
I have the same questions as @efriedma-quic
https://github.com/llvm/llvm-project/pull/143667
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -1321,3 +1321,24 @@ constexpr bool check = different_in_loop();
// expected-error@-1 {{}} expected-note@-1 {{in call}}
}
+
+namespace GH48665 {
+constexpr bool foo(int *i) {
shafik wrote:
Other tests: https://godbolt.org/z/o66Gr3fc8
```cpp
struct A {
ChuanqiXu9 wrote:
I think we shouldn't remove the assertion. Your test passes with the removal of
the assertion since the initializers are not complex. So it ends quickly. But
if it is a complex initialization which triggers more deserialization, I feel
it will be problematic.
I think the poi
https://github.com/fanju110 deleted
https://github.com/llvm/llvm-project/pull/142892
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -35,6 +35,7 @@ enum AccessKinds {
AK_Construct,
AK_Destroy,
AK_IsWithinLifetime,
+ AK_CheckReferenceInitialization
shafik wrote:
```suggestion
AK_ReferenceInitialization
```
I could also go for `AK_ReadForReferenceInitialization`. The "Check" is w
https://github.com/shafik edited
https://github.com/llvm/llvm-project/pull/143667
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Shunsuke Watanabe
Date: 2025-06-12T10:19:26+09:00
New Revision: c4316180418ce8de4b4c9812c7fac791d55b6102
URL:
https://github.com/llvm/llvm-project/commit/c4316180418ce8de4b4c9812c7fac791d55b6102
DIFF:
https://github.com/llvm/llvm-project/commit/c4316180418ce8de4b4c9812c7fac791d55b6102.d
llvmbot wrote:
@llvm/pr-subscribers-backend-loongarch
Author: None (Ami-zhang)
Changes
When '-march' with LASX feature and '-mno-lsx' options are used together,
'-mno-lsx' fails to disable LASX, leaving 'HasFeatureLASX=true' and causing
incorrect '__loongarch_sx/asx=1' macro definition.
https://github.com/Ami-zhang created
https://github.com/llvm/llvm-project/pull/143821
When '-march' with LASX feature and '-mno-lsx' options are used together,
'-mno-lsx' fails to disable LASX, leaving 'HasFeatureLASX=true' and causing
incorrect '__loongarch_sx/asx=1' macro definition.
Fixes
https://github.com/CoTinker closed
https://github.com/llvm/llvm-project/pull/143542
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Longsheng Mou
Date: 2025-06-12T09:27:27+08:00
New Revision: 52360d195b85608c677d781272534dfa61e9a1c3
URL:
https://github.com/llvm/llvm-project/commit/52360d195b85608c677d781272534dfa61e9a1c3
DIFF:
https://github.com/llvm/llvm-project/commit/52360d195b85608c677d781272534dfa61e9a1c3.diff
https://github.com/s-watanabe314 closed
https://github.com/llvm/llvm-project/pull/132680
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,596 @@
+//===-- WindowsHotPatch.cpp - Support for Windows hotpatching
-===//
+//
+// 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: Ap
https://github.com/efriedma-quic edited
https://github.com/llvm/llvm-project/pull/138972
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,596 @@
+//===-- WindowsHotPatch.cpp - Support for Windows hotpatching
-===//
+//
+// 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: Ap
https://github.com/efriedma-quic commented:
I'd like to see regression tests for the cases I've mentioned. PHI nodes,
ConstantExpr, and I guess the combination of the two.
https://github.com/llvm/llvm-project/pull/138972
___
cfe-commits mailing list
tstellar wrote:
Was there a backport request created for this one?
https://github.com/llvm/llvm-project/pull/135957
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/sivadeilra updated
https://github.com/llvm/llvm-project/pull/138972
>From 0d7c21c83f608a11de9129844d62ff73820a4acb Mon Sep 17 00:00:00 2001
From: Arlie Davis
Date: Thu, 3 Apr 2025 16:10:50 -0700
Subject: [PATCH] Windows hotpatching support
---
clang/include/clang/Basic/Code
https://github.com/AlexVlx updated
https://github.com/llvm/llvm-project/pull/143814
>From a976da9d6033a252fab75de216fe6580d6e3e6ff Mon Sep 17 00:00:00 2001
From: Alex Voicu
Date: Thu, 12 Jun 2025 00:47:43 +0100
Subject: [PATCH 1/2] Override `SPIRVTargetCodeGenInfo::supportsLibCall()` in
order
https://github.com/AlexVlx commented:
#143431 is related to this, but it proposes a more pervasive change, which
would require further discussion and clarification around what the SPIR-V BE
wants to do / support in term of libcalls.
https://github.com/llvm/llvm-project/pull/143814
https://github.com/AlexVlx edited
https://github.com/llvm/llvm-project/pull/143814
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
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 HEAD~1 HEAD --extensions c,cpp --
clang/lib/CodeGen/Targets/SPIR.cpp clang/test/CodeG
llvmbot wrote:
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-clang-codegen
Author: Alex Voicu (AlexVlx)
Changes
The `supportsLibCall` predicate is used to select whether some math builtins
get expanded in the FE or they get lowered into libcalls. The default
implementation unconditiona
https://github.com/AlexVlx created
https://github.com/llvm/llvm-project/pull/143814
The `supportsLibCall` predicate is used to select whether some math builtins
get expanded in the FE or they get lowered into libcalls. The default
implementation unconditionally returns true, which is problemat
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `ppc64le-flang-rhel-clang`
running on `ppc64le-flang-rhel-test` while building `clang` at step 6
"test-build-unified-tree-check-flang".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/157/builds/30523
https://github.com/AmrDeveloper updated
https://github.com/llvm/llvm-project/pull/143355
>From 8f5c75c524b42fc405b107a847643e1fb18adab0 Mon Sep 17 00:00:00 2001
From: AmrDeveloper
Date: Sun, 8 Jun 2025 22:14:20 +0200
Subject: [PATCH 1/5] [CIR] Implement folder for VecCreateOp
---
clang/includ
https://github.com/dpaoliello updated
https://github.com/llvm/llvm-project/pull/143577
>From 07390317820324535fc75f7bd9dd53c2e65bda41 Mon Sep 17 00:00:00 2001
From: Daniel Paoliello
Date: Fri, 6 Jun 2025 16:39:07 -0700
Subject: [PATCH] Add support for requiring Win x64 Unwind V2
---
clang/inc
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 HEAD~1 HEAD --extensions h,cpp --
clang/test/SemaCXX/trivially-relocatable-ptrauth.cp
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Oliver Hunt (ojhunt)
Changes
This reworks the way we compute relocatability and replaceability of types. We
do this by having a single interface the provides a full `TypeRelocationInfo`
for a QualType. This simplifies the reasoning for al
https://github.com/ojhunt created
https://github.com/llvm/llvm-project/pull/143796
This reworks the way we compute relocatability and replaceability of types. We
do this by having a single interface the provides a full `TypeRelocationInfo`
for a QualType. This simplifies the reasoning for all
@@ -88,6 +88,46 @@ void fir::setTuneCPU(mlir::ModuleOp mod, llvm::StringRef
cpu) {
mod->setAttr(tuneCpuName, mlir::StringAttr::get(ctx, cpu));
}
+static constexpr const char *amdgpuIgnoreDenormalModeName =
+"fir.amdgpu.ignore.denormal.mode";
+void fir::setAmdgpuIgnoreDe
https://github.com/andykaylor updated
https://github.com/llvm/llvm-project/pull/143639
>From 7e08ebf8887cb4ef90a06b853ebacfff1e57f510 Mon Sep 17 00:00:00 2001
From: Andy Kaylor
Date: Mon, 9 Jun 2025 09:38:55 -0700
Subject: [PATCH 1/2] [CIR] Upstream support for emitting constructors
This chang
https://github.com/erichkeane commented:
Typically we set limits like this for at least somewhat of a reasoned-reason.
Can we do some archeology to figure out when/why we decided on this limit?
Many times these limits are a result of our own stack space limits, so it would
be interesting to
@@ -58,10 +58,24 @@ void setTargetCPU(mlir::ModuleOp mod, llvm::StringRef cpu);
/// Get the target CPU string from the Module or return a null reference.
llvm::StringRef getTargetCPU(mlir::ModuleOp mod);
+// Setters and Getters for atomic control options
anchu
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 HEAD~1 HEAD --extensions cpp --
clang/lib/Driver/ToolChains/Linux.cpp
``
@@ -53,6 +53,11 @@ class TargetOptions {
/// Print verbose assembly
bool asmVerbose = false;
+
+ /// Atomic Control Options for AMD GPU
anchuraj wrote:
Updated
https://github.com/llvm/llvm-project/pull/143441
@@ -58,10 +58,24 @@ void setTargetCPU(mlir::ModuleOp mod, llvm::StringRef cpu);
/// Get the target CPU string from the Module or return a null reference.
llvm::StringRef getTargetCPU(mlir::ModuleOp mod);
+// Setters and Getters for atomic control options
+void setAmdgpuIgnoreD
@@ -2911,8 +2911,13 @@ static void genAtomicUpdateStatement(
if (rightHandClauseList)
genOmpAtomicHintAndMemoryOrderClauses(converter, *rightHandClauseList,
hint,
memoryOrder);
+ auto module = firOpBuilder.getModule();
-
@@ -54,6 +54,20 @@ def FlagsAttr : OpenMP_Attr<"Flags", "flags"> {
let assemblyFormat = "`<` struct(params) `>`";
}
+//===--===//
+// AtomicControlAttr
+//===-
@@ -5243,7 +5245,19 @@ static bool EvaluateVarDecl(EvalInfo &Info, const
VarDecl *VD) {
if (InitE->isValueDependent())
return false;
- if (!EvaluateInPlace(Val, Info, Result, InitE)) {
+ if (VD->getType()->isReferenceType() && InitE->isGLValue()) {
ef
@@ -5243,7 +5245,19 @@ static bool EvaluateVarDecl(EvalInfo &Info, const
VarDecl *VD) {
if (InitE->isValueDependent())
return false;
- if (!EvaluateInPlace(Val, Info, Result, InitE)) {
+ if (VD->getType()->isReferenceType() && InitE->isGLValue()) {
+if (!EvaluateL
anchuraj wrote:
> Thanks for this.
>
> Since you have added both `FlangOption` and `FC1Option` in `Options.td`,
> could you add a test that checks that the option is handled by the main
> driver as well as `fc1`. One that simply checks that the option gets passed
> down to `fc1` from the main
@@ -174,10 +174,11 @@ def note_constexpr_heap_alloc_limit_exceeded : Note<
def note_constexpr_this : Note<
"%select{|implicit }0use of 'this' pointer is only allowed within the "
"evaluation of a call to a 'constexpr' member function">;
-def access_kind : TextSubstitution<
@@ -4503,7 +4505,7 @@ static CompleteObject findCompleteObject(EvalInfo &Info,
const Expr *E,
} else {
const Expr *Base = LVal.Base.dyn_cast();
-if (!Frame) {
+if (!Frame && AK != clang::AK_CheckReferenceInitialization) {
efriedma-quic wrote:
T
https://github.com/anchuraj edited
https://github.com/llvm/llvm-project/pull/143769
___
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
Author: Siu Chi Chan (scchan)
Changes
Remove the dots in the HIP path before passing to the rpath flag
---
Full diff: https://github.com/llvm/llvm-project/pull/143792.diff
1 Files Affected:
- (modified) clang/lib/Driver/ToolChains/Linux.cpp (+5
erichkeane wrote:
> Erich, is there a good point-of-contact at nvidia who can review CUDA
> intrinsic header changes in the future?
For the most part, we don't have ANYTHING to do with CUDA in clang as far as I
know. I also don't know much about CUDA, but I'll ping an internal slack
channel
https://github.com/scchan created
https://github.com/llvm/llvm-project/pull/143792
Remove the dots in the HIP path before passing to the rpath flag
>From 4519fbaec265c0b927e235516c72869cf128aa62 Mon Sep 17 00:00:00 2001
From: Siu Chi Chan
Date: Wed, 11 Jun 2025 17:18:42 -0400
Subject: [PATCH]
https://github.com/andykaylor approved this pull request.
https://github.com/llvm/llvm-project/pull/143771
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143769
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/4] [flang][flang-driver] atomic control support
---
clang/i
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143441
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/3] [flang][flang-driver] atomic control support
---
clang/i
https://github.com/andykaylor approved this pull request.
https://github.com/llvm/llvm-project/pull/143355
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/erichkeane approved this pull request.
https://github.com/llvm/llvm-project/pull/143639
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
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 HEAD~1 HEAD --extensions cpp,h --
flang/include/flang/Frontend/TargetOptions.h
flang
https://github.com/anchuraj updated
https://github.com/llvm/llvm-project/pull/143769
>From c9b65080c1301c46b05fddc1278eaf2817963cb9 Mon Sep 17 00:00:00 2001
From: Anchu Rajendran
Date: Wed, 4 Jun 2025 15:12:49 -0500
Subject: [PATCH 1/4] [flang][flang-driver] atomic control support
---
clang/i
https://github.com/choikwa closed
https://github.com/llvm/llvm-project/pull/143431
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
choikwa wrote:
Closed in favor of better fix
https://github.com/llvm/llvm-project/pull/143431
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -220,6 +220,14 @@ static ExprResult EvaluateAtomicConstraint(
if (Inst.isInvalid())
return ExprError();
+if (const TemplateTypeParmType *TTPT =
+
dyn_cast(AtomicExpr->getType().getDesugaredType(S.Context)))
{
+ TemplateTypeParmDecl *TTPD = TTPT->
https://github.com/Sirraide closed
https://github.com/llvm/llvm-project/pull/143517
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Sirraide
Date: 2025-06-11T23:24:33+02:00
New Revision: 7838fc0cd3fbe578d9554fdcd3198c2ba3616bcc
URL:
https://github.com/llvm/llvm-project/commit/7838fc0cd3fbe578d9554fdcd3198c2ba3616bcc
DIFF:
https://github.com/llvm/llvm-project/commit/7838fc0cd3fbe578d9554fdcd3198c2ba3616bcc.diff
LOG:
@@ -3992,7 +3992,7 @@ Controlling implementation limits
Sets the limit for the number of full-expressions evaluated in a single
constant expression evaluation. This also controls the maximum size
of array and dynamic array allocation that can be constant evaluated.
- The
@@ -3992,7 +3992,7 @@ Controlling implementation limits
Sets the limit for the number of full-expressions evaluated in a single
constant expression evaluation. This also controls the maximum size
of array and dynamic array allocation that can be constant evaluated.
- The
Sirraide wrote:
> on my machine 20 million steps take roughly 10 seconds.
Yeah, same.
Added some more reviewers in case anyone can think of a reason why we
*shouldn’t* do this.
https://github.com/llvm/llvm-project/pull/143785
___
cfe-commits mailing
https://github.com/efriedma-quic closed
https://github.com/llvm/llvm-project/pull/143460
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Oleksandr T.
Date: 2025-06-11T14:19:25-07:00
New Revision: d7e7f22626f214766f3592341dd1737fd232c6a5
URL:
https://github.com/llvm/llvm-project/commit/d7e7f22626f214766f3592341dd1737fd232c6a5
DIFF:
https://github.com/llvm/llvm-project/commit/d7e7f22626f214766f3592341dd1737fd232c6a5.diff
https://github.com/Sirraide commented:
This seems reasonable to me.
This should also come with a release note (in clang/docs/ReleaseNotes.rst); not
sure in what section though.
https://github.com/llvm/llvm-project/pull/143785
___
cfe-commits mailing
@@ -3992,7 +3992,7 @@ Controlling implementation limits
Sets the limit for the number of full-expressions evaluated in a single
constant expression evaluation. This also controls the maximum size
of array and dynamic array allocation that can be constant evaluated.
- The
https://github.com/Sirraide edited
https://github.com/llvm/llvm-project/pull/143785
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/efriedma-quic approved this pull request.
LGTM
(It might be worth trying to audit other uses of getLocForEndOfToken; it looks
like there are other dubious uses. But we don't need to do everything in one
patch.)
https://github.com/llvm/llvm-project/pull/143460
_
https://github.com/AmrDeveloper created
https://github.com/llvm/llvm-project/pull/143771
This change adds a folder for the VecSplatOp
Issue https://github.com/llvm/llvm-project/issues/136487
>From 02f674320c41416cd6afe574545a737312cd5a7d Mon Sep 17 00:00:00 2001
From: AmrDeveloper
Date: Wed,
1 - 100 of 440 matches
Mail list logo
