Author: Benson Chu
Date: 2025-03-10T10:05:15-05:00
New Revision: 1f05703176d43a339b41a474f51c0e8b1a83c9bb
URL:
https://github.com/llvm/llvm-project/commit/1f05703176d43a339b41a474f51c0e8b1a83c9bb
DIFF:
https://github.com/llvm/llvm-project/commit/1f05703176d43a339b41a474f51c0e8b1a83c9bb.diff
LO
RiverDave wrote:
> Change looks correct, but looks like this check got one more limitation in
> case of code like this:
>
> ```
> class CastInit {
> CastInit() : m(static_cast(9)) {}
> int m = 9;
> };
> ```
>
> And this:
>
> ```
> class CastInit {
> CastInit() : m(static_cast(0)) {}
>
https://github.com/AZero13 edited
https://github.com/llvm/llvm-project/pull/130528
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ssahasra commented:
I don't have recent exposure to the OpenCL implementation, but generally
eyeballed the code to make sure that the changes do what is described. Is there
some confidence that the new scheme actually works? For example, maybe an
existing CodeGen test where
@@ -374,6 +379,8 @@ def main():
common_clang_tidy_args.append("-extra-arg-before=%s" % arg)
for plugin in args.plugins:
common_clang_tidy_args.append("-load=%s" % plugin)
+if args.warnings_as_errors != "":
PiotrZSL wrote:
probably this
https://github.com/PiotrZSL edited
https://github.com/llvm/llvm-project/pull/128221
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -3835,7 +3866,7 @@ let TargetPrefix = "aarch64" in {
def int_aarch64_sme_luti4_lane_zt_x2
: DefaultAttrsIntrinsic<[llvm_anyvector_ty, LLVMMatchType<0>],
[llvm_i32_ty, llvm_nxv16i8_ty, llvm_i32_ty],
[ImmArg>, ImmArg>,
IntrReadMem]>;
-
https://github.com/Ritanya-B-Bharadwaj closed
https://github.com/llvm/llvm-project/pull/129888
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/zyn0217 created
https://github.com/llvm/llvm-project/pull/130228
Todo:
- [ ] Adapt the bytecode interpreter to the new evaluation model
- [ ] Tests for CG & Constant evaluation
- [ ] Release notes
With this patch, the example shown in https://godbolt.org/z/b64x65716 (the R
https://github.com/PiotrZSL commented:
Release notes entry is missing.
Look into clang-tidy 20 release notes and just copy entry and adjust it.
https://github.com/llvm/llvm-project/pull/128221
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
htt
@@ -62,16 +62,13 @@ class PassTimingInfo {
private:
StringMap PassIDCountMap; ///< Map that counts instances of passes
- DenseMap> TimingData; ///< timers for
pass instances
- TimerGroup TG;
+ DenseMap TimingData; ///< timers for pass instances
aeubanks
https://github.com/tblah updated
https://github.com/llvm/llvm-project/pull/130788
>From 5d3c1cc1d40b308b93cc47c78c6c3ca677f55155 Mon Sep 17 00:00:00 2001
From: Tom Eccles
Date: Tue, 11 Mar 2025 15:54:35 +
Subject: [PATCH 1/2] [flang] Add support for -f[no-]verbose-asm
This flag provides ex
@@ -0,0 +1,50 @@
+// RUN: %check_clang_tidy %s misc-const-correctness %t \
vbvictor wrote:
I suppose this behavior comes from overlapping diag-messages, so guess we need
to change diag-message inside `CheckPointee` lambda.
https://github.com/llvm/llvm-project/p
https://github.com/t-rasmud approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/130729
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
t-rasmud wrote:
Thank you for addressing all the feedback. Didn't really mean to make you
create a new PR just for that one comment, I should've mentioned it was purely
for clarification.
https://github.com/llvm/llvm-project/pull/130729
___
cfe-commi
@@ -145,64 +165,90 @@ void ConstCorrectnessCheck::check(const
MatchFinder::MatchResult &Result) {
if (ArrayT->getElementType()->isPointerType())
VC = VariableCategory::Pointer;
- // Each variable can only be in one category: Value, Pointer, Reference.
- // Analysi
dwblaikie wrote:
> I am not sure that I understand your concern completely. Consider the
> following DWARF output based on my implementation. How would you say "v1"
> should be represented ideally?
> ```
> 0x0042: DW_TAG_structure_type
> DW_AT_calling_convention (DW_CC_pass_by_value)
> DW_A
@@ -0,0 +1,21 @@
+// RUN: %clang_cc1 -triple arm64-apple-ios -fsyntax-only -verify
-fptrauth-intrinsics -std=c++11 %s
+// RUN: %clang_cc1 -triple aarch64-linux-gnu -fsyntax-only -verify
-fptrauth-intrinsics -std=c++11 %s
+
+template struct G {
+ T __ptrauth(0,0,1234) test;
+
https://github.com/yxsamliu created
https://github.com/llvm/llvm-project/pull/130624
Reload aba3005a after fixing build failure.
Recently HIP runtime changed dll name to amdhip64_n.dll on Windows, where n is
ROCm major version number.
Fix amdgpu-arch to search for amdhip64_n.dll on Windows.
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Ricardo Jesus (rj-jesus)
Changes
This restores commit f01e760c08365426de95f02dc2c2dc670eb47352.
The original patch from #129732 exposed what seems to be a bug in
`SelectAddrModeIndexedSVE`.
Currently, the offset returned by `SelectAddrMo
https://github.com/mpark edited https://github.com/llvm/llvm-project/pull/129982
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ziqingluo-90 closed
https://github.com/llvm/llvm-project/pull/130683
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Ziqing Luo
Date: 2025-03-11T10:23:03-07:00
New Revision: 65016475084f6435dbf252997d53853c2bfdf9be
URL:
https://github.com/llvm/llvm-project/commit/65016475084f6435dbf252997d53853c2bfdf9be
DIFF:
https://github.com/llvm/llvm-project/commit/65016475084f6435dbf252997d53853c2bfdf9be.diff
LO
@@ -10033,15 +10040,24 @@ class Sema final : public SemaBase {
bool InOverloadResolution,
QualType &ConvertedType);
+ enum class CheckMemberPointerConversionResult {
erichkeane wrote:
Right, i
@@ -208,10 +208,17 @@ bool arm::useAAPCSForMachO(const llvm::Triple &T) {
bool arm::isHardTPSupported(const llvm::Triple &Triple) {
int Ver = getARMSubArchVersionNumber(Triple);
llvm::ARM::ArchKind AK = llvm::ARM::parseArch(Triple.getArchName());
- return Triple.isARM() ||
@@ -136,6 +136,10 @@ Changes in existing checks
` check by updating suppress
warnings logic for ``nullptr`` in ``std::find``.
+- Improved :doc:`modernize-use-std-numbers
+ ` check to support math
functions
dl8sd11 wrote:
Done.
https://github.com/llvm/
@@ -2203,8 +2203,18 @@ Parser::ParseCXXCondition(StmtResult *InitStmt,
SourceLocation Loc,
return ParseCXXCondition(nullptr, Loc, CK, MissingOK);
}
-// Parse the expression.
-ExprResult Expr = ParseExpression(); // expression
+ExprResult Expr;
+{
+
@@ -70,16 +94,38 @@ class ParentMapContext::ParentMap {
push_back(Value);
}
bool contains(const DynTypedNode &Value) {
- return Seen.contains(Value);
+ assert(Value.getMemoizationData());
+ bool found = FragileLazySeenCache.contains(&Value);
+
https://github.com/mizvekov edited
https://github.com/llvm/llvm-project/pull/130529
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -3520,21 +3520,24 @@ DecompositionDecl *DecompositionDecl::Create(ASTContext
&C, DeclContext *DC,
SourceLocation LSquareLoc,
QualType T, TypeSourceInfo *TInfo,
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/128150
>From e27ec113b6d20a34816fcf8daf5206cb7c4605d4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Thu, 20 Feb 2025 12:37:15 +
Subject: [PATCH] [clang-tidy] Avoid processing declarati
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Aaron Ballman (AaronBallman)
Changes
We have a list of criteria for proposing an extension in Clang, but we do not
have any documentation about how to propose an extension. This adds some basic
documentation about how we run RFCs in Clang
AaronBallman wrote:
Eventually, I expect we'll add documentation about the Clang Area Team to
`clang/docs` as .rst files. Once that happens, I think we should switch the
`AreaTeamMembers.txt` file to a .rst file and then link to the rendered content
from `get_involved.html`. But I figured that
ziqingluo-90 wrote:
Thanks for reviewing! I will create another PR for my questions.
https://github.com/llvm/llvm-project/pull/130683
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
PiotrZSL wrote:
@RiverDave If you rebase this change we can merge it, and then if you want you
could work on next version in independent PR.
https://github.com/llvm/llvm-project/pull/129408
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https
@@ -19,6 +19,5 @@
// NPM: InstCombinePass{{$}}
// NPM-NOT: InstCombinePass #
// TIME: Total{{$}}
-// NPM: Pass execution timing report
aeubanks wrote:
why does this line disappear?
https://github.com/llvm/llvm-project/pull/130375
_
Author: Jan Svoboda
Date: 2025-03-11T10:29:39-07:00
New Revision: eaca60d1a9a54ae0aa8626719decef4b11eb939d
URL:
https://github.com/llvm/llvm-project/commit/eaca60d1a9a54ae0aa8626719decef4b11eb939d
DIFF:
https://github.com/llvm/llvm-project/commit/eaca60d1a9a54ae0aa8626719decef4b11eb939d.diff
L
https://github.com/jansvoboda11 closed
https://github.com/llvm/llvm-project/pull/106274
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -194,15 +199,21 @@ void UseDefaultMemberInitCheck::storeOptions(
}
void UseDefaultMemberInitCheck::registerMatchers(MatchFinder *Finder) {
- auto InitBase =
- anyOf(stringLiteral(), characterLiteral(), integerLiteral(),
-unaryOperator(hasAnyOperatorName("+
@@ -0,0 +1,50 @@
+// RUN: %check_clang_tidy %s misc-const-correctness %t \
vbvictor wrote:
I tried running test on small code with both of the options enabled.
```cpp
int a[] = {1, 2};
int *p_local0 = &a[0];
```
transformed to
```cpp
int a[] = {1, 2};
int
https://github.com/efriedma-quic commented:
I somehow thought we had already done something about this, but I can't find
any reference to it.
Anyway, if we're going to support this as an extension, I don't want to bury it
in CGBuilder.h. We should decide exactly when we want it to trigger, an
https://github.com/RiverDave edited
https://github.com/llvm/llvm-project/pull/129408
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/RiverDave edited
https://github.com/llvm/llvm-project/pull/129408
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
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/erichkeane commented:
This patch ended up being pretty massive... ANYTHING we can do to reduce the
size of this would be very appreciated.
I DID NOT do more than a cursory look over the tests, so if someone else could
do some work to make sure there isn't anything awkward/we
andykaylor wrote:
Apparently the code formatting checker won't even let me mention "undef" in a
comment.
https://github.com/llvm/llvm-project/pull/130164
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
@@ -13461,13 +13486,112 @@ static ElaboratedTypeKeyword
getCommonTypeKeyword(const T *X, const T *Y) {
: ElaboratedTypeKeyword::None;
}
+static NestedNameSpecifier *getCommonNNS(ASTContext &Ctx,
+
https://github.com/mydeveloperday approved this pull request.
https://github.com/llvm/llvm-project/pull/130471
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/sarnex closed
https://github.com/llvm/llvm-project/pull/129545
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
sunfishcode wrote:
Is there a use case that needs to disable the red zone globally on Wasm? My
understanding is that -mno-red-zone exists for compatibility reasons that don't
apply to Wasm. I'm hesitant to add flags adding implicit ABI variants in the
absence of use cases. At least with the fu
Author: Aaron Ballman
Date: 2025-03-11T14:49:51-04:00
New Revision: 14176d10842dcb8697bc7bbce3a4e252d6f11986
URL:
https://github.com/llvm/llvm-project/commit/14176d10842dcb8697bc7bbce3a4e252d6f11986
DIFF:
https://github.com/llvm/llvm-project/commit/14176d10842dcb8697bc7bbce3a4e252d6f11986.diff
https://github.com/mpark edited https://github.com/llvm/llvm-project/pull/129982
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -89,23 +89,31 @@ void asuint(double4, out uint4, out uint4);
/// \param X The X input value.
/// \param Y The Y input value.
+template
_HLSL_16BIT_AVAILABILITY(shadermodel, 6.2)
-const inline half distance(half X, half Y) {
+const inline __detail::enable_if_t<__detail::is
https://github.com/tcottin updated
https://github.com/llvm/llvm-project/pull/128591
>From 18fa9e58b04b4e41e2b810fcc4a0c6be48258a1f Mon Sep 17 00:00:00 2001
From: Tim Cottin
Date: Tue, 11 Mar 2025 19:00:49 +
Subject: [PATCH] [clangd] Add doxygen parsing for hover information
---
clang-tool
Author: Aaron Ballman
Date: 2025-03-11T15:04:11-04:00
New Revision: 456fa47bab479f0ef1136d07687bd1b2635b1a26
URL:
https://github.com/llvm/llvm-project/commit/456fa47bab479f0ef1136d07687bd1b2635b1a26
DIFF:
https://github.com/llvm/llvm-project/commit/456fa47bab479f0ef1136d07687bd1b2635b1a26.diff
@@ -13461,13 +13486,112 @@ static ElaboratedTypeKeyword
getCommonTypeKeyword(const T *X, const T *Y) {
: ElaboratedTypeKeyword::None;
}
+static NestedNameSpecifier *getCommonNNS(ASTContext &Ctx,
+
https://github.com/jansvoboda11 updated
https://github.com/llvm/llvm-project/pull/130395
>From a9969c43be752ccaa70959fd4527a57dc2981881 Mon Sep 17 00:00:00 2001
From: Jan Svoboda
Date: Thu, 6 Mar 2025 17:29:34 -0800
Subject: [PATCH 1/3] [Support] Remove output file checks from
`LockFileManager
https://github.com/zhouronghua updated
https://github.com/llvm/llvm-project/pull/119513
>From bdb0d6d9996344c847ef145d4e55963534f78ceb Mon Sep 17 00:00:00 2001
From: "ronghua.zhou"
Date: Fri, 14 Feb 2025 01:04:51 +
Subject: [PATCH] [Feature]: support for the BC library file into the compile
cachemeifyoucan wrote:
Do you have a bot or build to point to for test failures?
There is no way to disable Darwin target from clang driver. I think the test
might be related to the host platform is not Darwin so the driver didn't infer
the target correctly without a default target triple?
I
@@ -45,6 +45,10 @@ template struct is_arithmetic {
static const bool Value = __is_arithmetic(T);
};
+template
+using HLSL_FIXED_VECTOR =
bogner wrote:
`HLSL_FIXED_VECTOR` looks like a macro to me rather than a type. Why use all
caps convention here?
htt
https://github.com/bogner approved this pull request.
Looks good to me. One suggestion for an alternative approach (using `= delete`
on some overloads) but you can use your judgement on whether that's worth
trying.
https://github.com/llvm/llvm-project/pull/130724
__
@@ -89,23 +89,31 @@ void asuint(double4, out uint4, out uint4);
/// \param X The X input value.
/// \param Y The Y input value.
+template
_HLSL_16BIT_AVAILABILITY(shadermodel, 6.2)
-const inline half distance(half X, half Y) {
+const inline __detail::enable_if_t<__detail::is
https://github.com/bogner edited
https://github.com/llvm/llvm-project/pull/130724
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -45,6 +45,10 @@ template struct is_arithmetic {
static const bool Value = __is_arithmetic(T);
};
+template
+using HLSL_FIXED_VECTOR =
farzonl wrote:
I was using it like a Macro for creating the vector type.
https://github.com/llvm/llvm-project/pull/
@@ -89,23 +89,31 @@ void asuint(double4, out uint4, out uint4);
/// \param X The X input value.
/// \param Y The Y input value.
+template
_HLSL_16BIT_AVAILABILITY(shadermodel, 6.2)
-const inline half distance(half X, half Y) {
+const inline __detail::enable_if_t<__detail::is
Author: Farzon Lotfi
Date: 2025-03-11T15:13:00-04:00
New Revision: 1cb14078658f9ac573ec4102354106e29d62c46d
URL:
https://github.com/llvm/llvm-project/commit/1cb14078658f9ac573ec4102354106e29d62c46d
DIFF:
https://github.com/llvm/llvm-project/commit/1cb14078658f9ac573ec4102354106e29d62c46d.diff
https://github.com/farzonl closed
https://github.com/llvm/llvm-project/pull/130724
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/farzonl edited
https://github.com/llvm/llvm-project/pull/130724
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shafik commented:
Should this have updated: https://clang.llvm.org/c_status.html
Also it would have been nice to mention the paper number in the release notes,
I am assuming there was a paper?
CC @AaronBallman
https://github.com/llvm/llvm-project/pull/129737
_
@@ -0,0 +1,21 @@
+// RUN: %clang_cc1 -triple arm64-apple-ios -fsyntax-only -verify
-fptrauth-intrinsics -std=c++11 %s
+// RUN: %clang_cc1 -triple aarch64-linux-gnu -fsyntax-only -verify
-fptrauth-intrinsics -std=c++11 %s
+
+template struct G {
+ T __ptrauth(0,0,1234) test;
+
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`openmp-offload-sles-build-only` running on `rocm-worker-hw-04-sles` while
building `clang` at step 6 "Add check check-clang".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/140/builds/18759
Here is
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/20047
MacDue wrote:
Thanks for the report :+1: It looks like all we have to do is set the
legalization rule for f32 to "Promote". Looks like there's actually already
logic to do this for a bunch of other nodes:
>From X86ISelLowering.cpp:
```c++
// On 32 bit MSVC, `fmodf(f32)` is not defined - only
https://github.com/rniwa closed https://github.com/llvm/llvm-project/pull/128586
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ykhatav wrote:
> > I am not sure that I understand your concern completely. Consider the
> > following DWARF output based on my implementation. How would you say "v1"
> > should be represented ideally?
> > ```
> > 0x0042: DW_TAG_structure_type
> > DW_AT_calling_convention (DW_CC_pass_by
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-cmake-x86_64-avx512-linux` running on `avx512-intel64` while building
`clang` at step 7 "ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/133/builds/12649
Here is the relevant pi
mstorsjo wrote:
> > So I believe this should be generalized to all of Windows (and/or
> > generalized to check for a COFF object file format?) instead of singling
> > out specifically MSVC only.
>
> Thanks for checking. I can fix the condition but can you please let me know
> which of the two
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`openmp-offload-amdgpu-runtime-2` running on `rocm-worker-hw-02` while building
`clang` at step 7 "Add check check-clang".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/10/builds/1097
Here is the re
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/14353
Her
@@ -36,6 +36,18 @@ class ScalarExprEmitter : public
StmtVisitor {
bool ira = false)
: cgf(cgf), builder(builder), ignoreResultAssign(ira) {}
+
//======//
+ //
@@ -84,26 +96,266 @@ class ScalarExprEmitter : public
StmtVisitor {
}
mlir::Value VisitCXXBoolLiteralExpr(const CXXBoolLiteralExpr *e) {
-mlir::Type type = cgf.convertType(e->getType());
+mlir::Type type = convertType(e->getType());
return builder.create(
@@ -0,0 +1,58 @@
+// RUN: %clang_cc1 -std=c++17 -triple x86_64-unknown-linux-gnu -fclangir
-emit-cir %s -o %t.cir
+// RUN: FileCheck --input-file=%t.cir %s
+
+unsigned char cxxstaticcast_0(unsigned int x) {
+ return static_cast(x);
+}
+
+// CHECK: cir.func @cxxstaticcast_0
+// C
@@ -36,6 +36,18 @@ class ScalarExprEmitter : public
StmtVisitor {
bool ira = false)
: cgf(cgf), builder(builder), ignoreResultAssign(ira) {}
+
//======//
+ //
@@ -84,26 +96,266 @@ class ScalarExprEmitter : public
StmtVisitor {
}
mlir::Value VisitCXXBoolLiteralExpr(const CXXBoolLiteralExpr *e) {
-mlir::Type type = cgf.convertType(e->getType());
+mlir::Type type = convertType(e->getType());
return builder.create(
@@ -0,0 +1,58 @@
+// RUN: %clang_cc1 -std=c++17 -triple x86_64-unknown-linux-gnu -fclangir
-emit-cir %s -o %t.cir
andykaylor wrote:
Can you expand this test to cover all the cast types you're adding (or remove
any that can't be supported yet)?
https://github.c
@@ -78,6 +79,67 @@ class CIRBaseBuilderTy : public mlir::OpBuilder {
return create(loc, val, dst);
}
+
//======//
+ // Cast/Conversion Operators
+
//===--
https://github.com/alexey-bataev approved this pull request.
https://github.com/llvm/llvm-project/pull/129888
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -22,56 +22,128 @@
//
// RUN: %clang_cc1 -finclude-default-header -x hlsl -triple \
// RUN: spirv-unknown-vulkan-compute %s -fnative-half-type \
-// RUN: -emit-llvm -disable-llvm-passes -o - | FileCheck %s \
+// RUN: -emit-llvm -o - | FileCheck %s \
// RUN: -DFNATTRS
@@ -22,56 +22,136 @@
//
// RUN: %clang_cc1 -finclude-default-header -x hlsl -triple \
// RUN: spirv-unknown-vulkan-compute %s -fnative-half-type \
-// RUN: -emit-llvm -disable-llvm-passes -o - | FileCheck %s \
+// RUN: -emit-llvm -o - | FileCheck %s \
// RUN: -DFNATTRS
@@ -22,56 +22,128 @@
//
// RUN: %clang_cc1 -finclude-default-header -x hlsl -triple \
// RUN: spirv-unknown-vulkan-compute %s -fnative-half-type \
-// RUN: -emit-llvm -disable-llvm-passes -o - | FileCheck %s \
+// RUN: -emit-llvm -o - | FileCheck %s \
// RUN: -DFNATTRS
@@ -40,11 +40,14 @@ class ConstCorrectnessCheck : public ClangTidyCheck {
const bool AnalyzeValues;
const bool AnalyzeReferences;
+ const bool AnalyzePointers;
EugeneZelenko wrote:
How about alphabetical order? Same below.
https://github.com/llvm/llvm-p
@@ -4668,6 +4668,34 @@ bool Parser::ParseOpenMPVarList(OpenMPDirectiveKind
DKind,
assert(Tok.is(tok::comma) && "Expected comma.");
(void)ConsumeToken();
}
+// Handle original(private / shared) Modifier
+if (Kind == OMPC_reduction && getLangOpts().OpenMP
https://github.com/Icohedron approved this pull request.
https://github.com/llvm/llvm-project/pull/130320
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,114 @@
+//===--- CapturingThisByFieldCheck.cpp - clang-tidy
---===//
+//
+// 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/HerrCai0907 edited
https://github.com/llvm/llvm-project/pull/130297
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
mizvekov wrote:
Sorry about that, but the patch which added the automatic
`NoteTemplateParameterLocation` was reverted and I had missed the notification.
https://github.com/llvm/llvm-project/pull/122754
___
cfe-commits mailing list
cfe-commits@lists.l
tarunprabhu wrote:
For compiler options, we have various "categories" in `Options.td`,
`ClangOptions`, `FlangOptions` etc. which only apply to specific frontends. I
haven't looked very closely at this, but I believe that there is only one
"category" for warnings. Is this correct? If that the c
Author: Mariusz Sikora
Date: 2025-03-06T14:24:49+01:00
New Revision: 0aa92d23b206e20fb1e19f4fc0d05d2d293f404f
URL:
https://github.com/llvm/llvm-project/commit/0aa92d23b206e20fb1e19f4fc0d05d2d293f404f
DIFF:
https://github.com/llvm/llvm-project/commit/0aa92d23b206e20fb1e19f4fc0d05d2d293f404f.diff
@@ -8361,6 +8361,17 @@ class ExprEvaluatorBase
return false;
}
+// If an assertion fails during constant evaluation, give a specific note
explaining that
+if (FD->getName() == "__assert_fail") {
cor3ntin wrote:
Maybe we can instead check
@@ -0,0 +1,44 @@
+//===--- CapturingThisByFieldCheck.h - clang-tidy ---*- C++
-*-===//
+//
+// 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: Apa
401 - 500 of 680 matches
Mail list logo
