zyn0217 wrote:
Review ping
https://github.com/llvm/llvm-project/pull/134038
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/kito-cheng commented:
I am really happy to see this finally start to upstream as ex-Ande guy :P
---
Do you have plan send PR to
https://github.com/riscv-non-isa/riscv-toolchain-conventions?
https://github.com/llvm/llvm-project/pull/135110
___
@@ -690,6 +690,23 @@ SmallVector
TemplateParamsReferencedInTemplateArgumentList(
SemaRef.MarkUsedTemplateParameters(
DeducedArgs, TemplateParamsList->getDepth(), ReferencedTemplateParams);
+ auto MarkDefaultArgs = [&](auto *Param) {
+if (!Param || !Param->hasDefa
https://github.com/kito-cheng edited
https://github.com/llvm/llvm-project/pull/135110
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ShashwathiNavada wrote:
ping @cor3ntin
https://github.com/llvm/llvm-project/pull/125643
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/wzssyqa closed
https://github.com/llvm/llvm-project/pull/129207
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,34 @@
+# XAndesPerf - Andes Performance Extension
+# RUN: llvm-mc %s -triple=riscv64 -mattr=+xandesperf -show-encoding \
+# RUN: | FileCheck -check-prefixes=CHECK-ASM,CHECK-ASM-AND-OBJ %s
+# RUN: llvm-mc -filetype=obj -triple riscv64 -mattr=+xandesperf < %s \
+# RUN
@@ -0,0 +1,105 @@
+# XAndesPerf - Andes Performance Extension
+# RUN: llvm-mc %s -triple=riscv32 -mattr=+xandesperf -show-encoding \
+# RUN: | FileCheck -check-prefixes=CHECK-ASM,CHECK-ASM-AND-OBJ %s
+# RUN: llvm-mc -filetype=obj -triple riscv32 -mattr=+xandesperf < %s \
+# RU
@@ -0,0 +1,105 @@
+# XAndesPerf - Andes Performance Extension
+# RUN: llvm-mc %s -triple=riscv32 -mattr=+xandesperf -show-encoding \
+# RUN: | FileCheck -check-prefixes=CHECK-ASM,CHECK-ASM-AND-OBJ %s
+# RUN: llvm-mc -filetype=obj -triple riscv32 -mattr=+xandesperf < %s \
+# RU
@@ -0,0 +1,34 @@
+# XAndesPerf - Andes Performance Extension
+# RUN: llvm-mc %s -triple=riscv64 -mattr=+xandesperf -show-encoding \
+# RUN: | FileCheck -check-prefixes=CHECK-ASM,CHECK-ASM-AND-OBJ %s
+# RUN: llvm-mc -filetype=obj -triple riscv64 -mattr=+xandesperf < %s \
+# RUN
@@ -0,0 +1,105 @@
+# XAndesPerf - Andes Performance Extension
+# RUN: llvm-mc %s -triple=riscv32 -mattr=+xandesperf -show-encoding \
+# RUN: | FileCheck -check-prefixes=CHECK-ASM,CHECK-ASM-AND-OBJ %s
+# RUN: llvm-mc -filetype=obj -triple riscv32 -mattr=+xandesperf < %s \
+# RU
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-cmake-x86_64-avx512-win` running on `avx512-intel64-win` while building
`clang` at step 4 "cmake stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/81/builds/6292
Here is the relevant pi
Author: YunQiang Su
Date: 2025-04-14T13:49:32+08:00
New Revision: 58b5df09dc6f899016fc707bf937b36b36934b6d
URL:
https://github.com/llvm/llvm-project/commit/58b5df09dc6f899016fc707bf937b36b36934b6d
DIFF:
https://github.com/llvm/llvm-project/commit/58b5df09dc6f899016fc707bf937b36b36934b6d.diff
L
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `openmp-s390x-linux`
running on `systemz-1` while building `clang` at step 6 "test-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/88/builds/10403
Here is the relevant piece of the build log f
https://github.com/tclin914 updated
https://github.com/llvm/llvm-project/pull/135110
>From 1615cb987f60d8c6123f7c95bc7bd7f22d897ea1 Mon Sep 17 00:00:00 2001
From: Jim Lin
Date: Wed, 9 Apr 2025 09:44:47 +0800
Subject: [PATCH 1/7] [RISCV] Add Andes XAndesperf (Andes Performance)
extension.
The
Author: Pengcheng Wang
Date: 2025-04-14T13:00:57+08:00
New Revision: e57f4e8969db32f075d8f3e554506ec8b187a2f1
URL:
https://github.com/llvm/llvm-project/commit/e57f4e8969db32f075d8f3e554506ec8b187a2f1
DIFF:
https://github.com/llvm/llvm-project/commit/e57f4e8969db32f075d8f3e554506ec8b187a2f1.diff
@@ -2759,6 +2759,19 @@ StmtResult
Parser::ParseOpenMPDeclarativeOrExecutableDirective(
OpenMPClauseKind CKind = Tok.isAnnotation()
? OMPC_unknown
: getOpenMPClauseKind(PP.getSpelling(Tok));
+ // C
wangpc-pp wrote:
> @wangpc-pp you might want to revert this or fix it soon.
Reverted. Thanks!
https://github.com/llvm/llvm-project/pull/133710
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-
Author: Wang Pengcheng
Date: 2025-04-14T12:56:33+08:00
New Revision: 21ff45dea1601d6d12438b5201ff09b8726899be
URL:
https://github.com/llvm/llvm-project/commit/21ff45dea1601d6d12438b5201ff09b8726899be
DIFF:
https://github.com/llvm/llvm-project/commit/21ff45dea1601d6d12438b5201ff09b8726899be.diff
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `publish-sphinx-docs`
running on `as-worker-4` while building `clang` at step 5
"build-docs-llvm-html-docs-clang-html-docs-clang...".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/45/builds/9
He
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`amdgpu-offload-ubuntu-22-cmake-build-only` running on `rocm-docker-ubu-22`
while building `clang` at step 4 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/203/builds/7536
Here is the rel
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 5 "compile-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/10/builds/3389
Here is the relevant
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`polly-x86_64-linux-shared-plugin` running on `polly-x86_64-gce2` while
building `clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/118/builds/5768
Here is the relevant piece o
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `polly-x86_64-linux-shlib`
running on `polly-x86_64-gce2` while building `clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/99/builds/5910
Here is the relevant piece of the buil
svs-quic wrote:
@wangpc-pp you might want to revert this or fix it soon.
https://github.com/llvm/llvm-project/pull/133710
___
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-ppc64le-linux-multistage` running on `ppc64le-clang-multistage-test`
while building `clang` at step 4 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/76/builds/8722
Here is the
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `openmp-s390x-linux`
running on `systemz-1` while building `clang` at step 5 "compile-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/88/builds/10398
Here is the relevant piece of the build lo
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `polly-x86_64-linux-shared`
running on `polly-x86_64-gce2` while building `clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/97/builds/6061
Here is the relevant piece of the bui
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `polly-x86_64-linux-plugin`
running on `polly-x86_64-gce1` while building `clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/158/builds/7856
Here is the relevant piece of the bu
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`polly-x86_64-linux-noassert` running on `polly-x86_64-gce1` while building
`clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/28/builds/8361
Here is the relevant piece of the
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` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/95/builds/11961
Here is th
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`polly-x86_64-linux-shlib-plugin` running on `polly-x86_64-gce2` while building
`clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/75/builds/6187
Here is the relevant piece of
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `polly-x86_64-linux`
running on `polly-x86_64-gce1` while building `clang` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/105/builds/8316
Here is the relevant piece of the build log
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `flang-runtime-cuda-clang`
running on `as-builder-7` while building `clang` at step 7
"build-flang-default".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/7/builds/13381
Here is the relevant piece o
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`ppc64le-lld-multistage-test` running on `ppc64le-lld-multistage-test` while
building `clang` at step 6 "build-stage1-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/168/builds/10849
He
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-m68k-linux-cross`
running on `suse-gary-m68k-cross` while building `clang` at step 4 "build stage
1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/27/builds/8576
Here is the relevant piece o
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-ubuntu`
running on `as-builder-9` while building `clang` at step 7 "build-default".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/195/builds/7561
Here is the relevant piece of the
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 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/144/builds/22657
Here is the re
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `flang-runtime-cuda-gcc`
running on `as-builder-7` while building `clang` at step 6 "build-flang-rt".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/152/builds/1769
Here is the relevant piece of the b
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-hip-vega20` running
on `hip-vega20-0` while building `clang` at step 3 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/123/builds/17448
Here is the relevant piece of the build log fo
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `arc-builder` running on
`arc-worker` while building `clang` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/3/builds/14487
Here is the relevant piece of the build log f
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-x86_64-linux-abi-test` running on `sie-linux-worker2` while building
`clang` at step 6 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/8/builds/13936
Here is the relevant
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 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/174/builds/16139
Here is the releva
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`amdgpu-offload-rhel-8-cmake-build-only` running on `rocm-docker-rhel-8` while
building `clang` at step 4 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/204/builds/6349
Here is the releva
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`cross-project-tests-sie-ubuntu` running on `doug-worker-1a` while building
`clang` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/181/builds/17515
Here is the relevan
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 5 "compile-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/140/builds/21113
Here is the rel
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`cross-project-tests-sie-ubuntu-dwarf5` running on `doug-worker-1b` while
building `clang` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/163/builds/17069
Here is the
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 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/133/builds/14454
Here is the relevant pi
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`amdgpu-offload-rhel-9-cmake-build-only` running on `rocm-docker-rhel-9` while
building `clang` at step 4 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/205/builds/6327
Here is the releva
https://github.com/wangpc-pp updated
https://github.com/llvm/llvm-project/pull/133710
>From 031ef3fa34f0448dc9743135802e7c6be2025442 Mon Sep 17 00:00:00 2001
From: Wang Pengcheng
Date: Mon, 31 Mar 2025 20:12:40 +0800
Subject: [PATCH 1/3] [RISCV][NFC] Make generated intrinsic records more
human
https://github.com/wangpc-pp closed
https://github.com/llvm/llvm-project/pull/133710
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Pengcheng Wang
Date: 2025-04-14T12:17:26+08:00
New Revision: d0cf5cd5f9790dc21396936d076389c3be1a9599
URL:
https://github.com/llvm/llvm-project/commit/d0cf5cd5f9790dc21396936d076389c3be1a9599
DIFF:
https://github.com/llvm/llvm-project/commit/d0cf5cd5f9790dc21396936d076389c3be1a9599.diff
https://github.com/kazutakahirata created
https://github.com/llvm/llvm-project/pull/135574
None
>From 085ac380032ba50250a489327986bd7a0dce951e Mon Sep 17 00:00:00 2001
From: Kazu Hirata
Date: Sun, 13 Apr 2025 15:32:33 -0700
Subject: [PATCH] [Sema] Use llvm::erase_if (NFC)
---
clang/lib/Sema/
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-s390x-linux` running
on `systemz-1` while building `clang,llvm` at step 5 "ninja check 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/42/builds/4134
Here is the relevant piece of the build
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/AST/TextNodeDumper.cpp clang/test/AST/ast-d
https://github.com/YLChenZ updated
https://github.com/llvm/llvm-project/pull/135178
>From 1119ecf764ecd94c12966758964cb486709a441d Mon Sep 17 00:00:00 2001
From: YLChenZ
Date: Thu, 10 Apr 2025 21:20:58 +0800
Subject: [PATCH 1/3] [clang][ast]: Add DynamicAllocLValue and TypeInfoLValue
support t
https://github.com/kuhar approved this pull request.
https://github.com/llvm/llvm-project/pull/135574
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/YLChenZ updated
https://github.com/llvm/llvm-project/pull/135178
>From 1119ecf764ecd94c12966758964cb486709a441d Mon Sep 17 00:00:00 2001
From: YLChenZ
Date: Thu, 10 Apr 2025 21:20:58 +0800
Subject: [PATCH 1/2] [clang][ast]: Add DynamicAllocLValue and TypeInfoLValue
support t
https://github.com/ChuanqiXu9 approved this pull request.
Yeah, I have some concern about the interface. But I am in the camp that we'd
better to get best practice from practice instead of pure imagination. And
given Meta is doing the experiments in practice, I think it is fine to let it
go.
https://github.com/phoebewang milestoned
https://github.com/llvm/llvm-project/pull/135489
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `sanitizer-aarch64-linux`
running on `sanitizer-buildbot7` while building `clang,llvm` at step 2
"annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/51/builds/14338
Here is the relevant piece
llvmbot wrote:
/pull-request llvm/llvm-project#135577
https://github.com/llvm/llvm-project/pull/135489
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
phoebewang wrote:
/cherry-pick
https://github.com/llvm/llvm-project/commit/ebba554a3211b0b98d3ae33ba70f9d6ceaab6ad4
https://github.com/llvm/llvm-project/pull/135489
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
Author: Phoebe Wang
Date: 2025-04-14T08:54:10+08:00
New Revision: ebba554a3211b0b98d3ae33ba70f9d6ceaab6ad4
URL:
https://github.com/llvm/llvm-project/commit/ebba554a3211b0b98d3ae33ba70f9d6ceaab6ad4
DIFF:
https://github.com/llvm/llvm-project/commit/ebba554a3211b0b98d3ae33ba70f9d6ceaab6ad4.diff
L
@@ -3032,6 +2983,162 @@ int UnwindCursor::stepThroughSigReturn(Registers_s390x &) {
#endif // defined(_LIBUNWIND_CHECK_LINUX_SIGRETURN) &&
// defined(_LIBUNWIND_TARGET_S390X)
+#if defined(_LIBUNWIND_CHECK_HAIKU_SIGRETURN)
+
+#if defined(B_HAIKU_32_BIT)
+typedef Elf32_Sy
@@ -3032,6 +2983,162 @@ int UnwindCursor::stepThroughSigReturn(Registers_s390x &) {
#endif // defined(_LIBUNWIND_CHECK_LINUX_SIGRETURN) &&
// defined(_LIBUNWIND_TARGET_S390X)
+#if defined(_LIBUNWIND_CHECK_HAIKU_SIGRETURN)
+
+#if defined(B_HAIKU_32_BIT)
+typedef Elf32_Sy
https://github.com/wzssyqa updated
https://github.com/llvm/llvm-project/pull/129207
>From 679f92557d62acd87bf521050db7c2aee527293a Mon Sep 17 00:00:00 2001
From: YunQiang Su
Date: Fri, 28 Feb 2025 16:09:04 +0800
Subject: [PATCH 1/6] Clang: Add minnum/maxnum builtin functions support
With https
@@ -3032,6 +2983,162 @@ int UnwindCursor::stepThroughSigReturn(Registers_s390x &) {
#endif // defined(_LIBUNWIND_CHECK_LINUX_SIGRETURN) &&
// defined(_LIBUNWIND_TARGET_S390X)
+#if defined(_LIBUNWIND_CHECK_HAIKU_SIGRETURN)
+
+#if defined(B_HAIKU_32_BIT)
+typedef Elf32_Sy
https://github.com/kazutakahirata closed
https://github.com/llvm/llvm-project/pull/135574
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Kazu Hirata
Date: 2025-04-13T16:36:45-07:00
New Revision: 1f195afa57942db3f616e0595eb5816d1359dd2e
URL:
https://github.com/llvm/llvm-project/commit/1f195afa57942db3f616e0595eb5816d1359dd2e
DIFF:
https://github.com/llvm/llvm-project/commit/1f195afa57942db3f616e0595eb5816d1359dd2e.diff
L
https://github.com/a-tarasyuk created
https://github.com/llvm/llvm-project/pull/135573
Fixes #132038
---
This PR extends `-Wloop-analysis` to handle variable modifications inside
lambda expressions.
>From 05125bafc45755624973feba0f4e6c2050fad36f Mon Sep 17 00:00:00 2001
From: Oleksandr Ta
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Kazu Hirata (kazutakahirata)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/135574.diff
2 Files Affected:
- (modified) clang/lib/Sema/SemaTemplateInstantiateDecl.cpp (+4-6)
- (modified) clang/lib/Sema/TreeTransform.h
https://github.com/a-tarasyuk updated
https://github.com/llvm/llvm-project/pull/135573
>From 05125bafc45755624973feba0f4e6c2050fad36f Mon Sep 17 00:00:00 2001
From: Oleksandr Tarasiuk
Date: Mon, 14 Apr 2025 01:37:05 +0300
Subject: [PATCH] [Clang] enhance loop analysis to handle variable changes
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Oleksandr T. (a-tarasyuk)
Changes
Fixes #132038
---
This PR extends `-Wloop-analysis` to handle variable modifications inside
lambda expressions.
---
Full diff: https://github.com/llvm/llvm-project/pull/135573.diff
3 Files Affected
irymarchyk wrote:
> We should stick to the table in [#134337
> (comment)](https://github.com/llvm/llvm-project/pull/134337#discussion_r2028339995)
> and deprecate `SFS_InlineOnly`, `SFS_Empty`, and `SFS_Inline`.
Thanks, I marked options as 'deprecated'. Mapping is done in Format.cpp.
https://
https://github.com/irymarchyk updated
https://github.com/llvm/llvm-project/pull/134337
>From df25a8bbfd827085265c51a44bedbf38deebbab4 Mon Sep 17 00:00:00 2001
From: Ivan Rymarchyk <>
Date: Sat, 29 Mar 2025 13:54:32 -0700
Subject: [PATCH 1/6] [clang-format]: Add `Custom` to `ShortFunctionStyle`;
Author: Yoann Congal
Date: 2025-04-13T18:03:46-04:00
New Revision: 3de93015386f17d3430c6534b9fa3e2a9adfaa1a
URL:
https://github.com/llvm/llvm-project/commit/3de93015386f17d3430c6534b9fa3e2a9adfaa1a
DIFF:
https://github.com/llvm/llvm-project/commit/3de93015386f17d3430c6534b9fa3e2a9adfaa1a.diff
github-actions[bot] wrote:
@ycongal-smile 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
HighCommander4 wrote:
Ok, I went ahead and merged it.
https://github.com/llvm/llvm-project/pull/133124
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/HighCommander4 closed
https://github.com/llvm/llvm-project/pull/133124
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/aaronpuchert updated
https://github.com/llvm/llvm-project/pull/135561
>From 372bfceceec7ba618d7651559f1071baacaf2fcc Mon Sep 17 00:00:00 2001
From: Aaron Puchert
Date: Sun, 13 Apr 2025 22:28:23 +0200
Subject: [PATCH] Merge similar Clang Thread Safety attributes
Some of the o
ycongal-smile wrote:
ping
https://github.com/llvm/llvm-project/pull/133124
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
hvdijk wrote:
Not entirely sure who to ask for reviews, adding @rjmccall for the Itanium C++
ABI aspect as it interacts with the AAPCS ABIs, and @efriedma-quic who approved
https://reviews.llvm.org/D46013 originally.
https://github.com/llvm/llvm-project/pull/135564
@@ -3107,6 +3107,23 @@ let TargetPrefix = "aarch64" in {
}
}
+ class SME_OuterProduct_TMOP_Intrinsic
+ : DefaultAttrsIntrinsic<[],
+ [llvm_i32_ty,
+ llvm_anyvector_ty,
+ LLVMMatchType<0>,
+ LLVMMatchType<0>,
+ llvm_nxv16i8
@@ -3593,6 +3578,25 @@ class sme_tmopa_32b opc, RegisterOperand zn_ty,
RegisterOperand zm_ty, s
let Constraints = "$ZAda = $_ZAda";
}
+multiclass sme_tmopa_16b opc, RegisterOperand zn_ty, RegisterOperand
zm_ty, ValueType vt, string mnemonic, string intrinsic> {
+ def NAME
@@ -3593,6 +3578,25 @@ class sme_tmopa_32b opc, RegisterOperand zn_ty,
RegisterOperand zm_ty, s
let Constraints = "$ZAda = $_ZAda";
}
+multiclass sme_tmopa_16b opc, RegisterOperand zn_ty, RegisterOperand
zm_ty, ValueType vt, string mnemonic, string intrinsic> {
+ def NAME
ojhunt wrote:
@AaronBallman do you have any further requests or changes for this PR?
https://github.com/llvm/llvm-project/pull/100830
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/hvdijk created
https://github.com/llvm/llvm-project/pull/135564
RecordLayout::UnadjustedAlignment was documented as "Maximum of the alignments
of the record members in characters", but
RecordLayout::getUnadjustedAlignment(), which just returns UnadjustedAlignment,
was docum
perry-ca wrote:
> I just happened to look into the implementation of AutoConvert.h, and I see
> the entire interface is defined away when not targeting zOS. This means that
> all call sites need to be conditional on `ifdef __MVS__`, which means we have
> ugly ifdef droppings all over the codeb
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Harald van Dijk (hvdijk)
Changes
RecordLayout::UnadjustedAlignment was documented as "Maximum of the alignments
of the record members in characters", but
RecordLayout::getUnadjustedAlignment(), which just returns UnadjustedAlignment,
was
llvmbot wrote:
@llvm/pr-subscribers-clang-analysis
Author: Aaron Puchert (aaronpuchert)
Changes
Some of the old lock-based and new capability-based spellings behave basically
in the same way, so merging them simplifies the code significantly.
There are two minor functional changes: we on
https://github.com/ojhunt created
https://github.com/llvm/llvm-project/pull/135562
If clang is configured to apply pointer authentication to type_info's vtable
pointer we
ensure that the selected schema is applied to the RTTI objects generated for
objc++.
>From 5dc1e5fbb57f88e412e044605d8fe30
https://github.com/aaronpuchert created
https://github.com/llvm/llvm-project/pull/135561
Some of the old lock-based and new capability-based spellings behave basically
in the same way, so merging them simplifies the code significantly.
There are two minor functional changes: we only warn (inst
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Oliver Hunt (ojhunt)
Changes
If clang is configured to apply pointer authentication to type_info's vtable
pointer we
ensure that the selected schema is applied to the RTTI objects generated for
objc++.
---
Full diff: https://github.com/l
ojhunt wrote:
> > I just noticed there's no documentation for
> > `__builtin_virtual_member_address()` so I'm addressing that.
> > Due to code drift and time I realized that they disagree as to whether they
> > should take `C*` or `C&` so I'm going to make them both accept either
> > (existing
ojhunt wrote:
@AaronBallman are you ok with this now? I'm re-requesting the review as it's
been a while, and I want to confirm I addressed things as you wanted
https://github.com/llvm/llvm-project/pull/117428
___
cfe-commits mailing list
cfe-commits@l
https://github.com/MDevereau closed
https://github.com/llvm/llvm-project/pull/135016
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -80,13 +80,46 @@ void ExceptionEscapeCheck::check(const
MatchFinder::MatchResult &Result) {
if (!MatchedDecl)
return;
- if (Tracer.analyze(MatchedDecl).getBehaviour() ==
- utils::ExceptionAnalyzer::State::Throwing)
-// FIXME: We should provide more informat
ojhunt wrote:
> > I just noticed there's no documentation for
> > `__builtin_virtual_member_address()` so I'm addressing that.
> > Due to code drift and time I realized that they disagree as to whether they
> > should take `C*` or `C&` so I'm going to make them both accept either
> > (existing
YutongZhuu wrote:
> > > But still I feel generate a warning for this case went too far.
> >
> >
> > Yeah, that's probably right. Maybe for `-` on a signed operand, we should
> > just return the original range with the `NonNegative` flag cleared out, and
> > shouldn't add the extra bit for the
1 - 100 of 204 matches
Mail list logo