@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,104 @@
+//===- llvm-mustachespec.cpp - The LLVM Modular Optimizer
+//===--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.tx
@@ -0,0 +1,12 @@
+llvm-mustachespec - LLVM tool to test Mustache Compliance Library
+=
+
+llvm-mustachespec test the mustache spec conformance of the LLVM
nikic wrote:
```suggestion
llvm-mustachespec
@@ -0,0 +1,12 @@
+llvm-mustachespec - LLVM tool to test Mustache Compliance Library
+=
+
+llvm-mustachespec test the mustache spec conformance of the LLVM
+mustache library. The spec can be found here https://github.c
nikic wrote:
> Overall the patch is much better. Once it's moved to `utils` I think it will
> be good. @nikic I seem to recall that we now prefer markdown over `.rst`
> files. Is that correct? I tried to find documentation for the policy, but I
> seem to be missing it in my grep/googling.
I b
https://github.com/Wolfram70 created
https://github.com/llvm/llvm-project/pull/134345
This change adds NVVM intrinsics and clang builtins for the cvt instruction
variants of types `.e2m3x2`, `.e3m2x2`, and `.ue8m0x2` introduced in PTX 8.6
for `sm_100a`, `sm_101a`, and `sm_120a`.
Tests are add
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
llvmbot wrote:
@llvm/pr-subscribers-llvm-ir
Author: Srinivasa Ravi (Wolfram70)
Changes
This change adds NVVM intrinsics and clang builtins for the cvt instruction
variants of types `.e2m3x2`, `.e3m2x2`, and `.ue8m0x2` introduced in PTX 8.6
for `sm_100a`, `sm_101a`, and `sm_120a`.
Tests
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Srinivasa Ravi (Wolfram70)
Changes
This change adds NVVM intrinsics and clang builtins for the cvt instruction
variants of types `.e2m3x2`, `.e3m2x2`, and `.ue8m0x2` introduced in PTX 8.6
for `sm_100a`, `sm_101a`, and `sm_120a`.
Tests ar
https://github.com/andykaylor updated
https://github.com/llvm/llvm-project/pull/134181
>From 54454e4d52570f29c493c41fc9bf95cbaf9e0886 Mon Sep 17 00:00:00 2001
From: Andy Kaylor
Date: Fri, 21 Mar 2025 09:46:27 -0700
Subject: [PATCH 1/2] [CIR] Upstream support for break and continue statements
T
madhur13490 wrote:
> The other tests should be strengthened to always use -NEXT. The exact set of
> macros should be tested; don't want others hiding in the gaps
Thanks, @arsenm. However, the strict checks are creating problems in our
downstream compiler and rebasing. Our downstream compiler e
efriedma-quic wrote:
I'm mostly concerned about the case where the lowered node has the wrong type.
For example, AArch64TargetLowering::LowerINTRINSIC_WO_CHAIN always creates a
value with the pointer width of addrspace 0, but address spaces exist which
don't have the native pointer width (arm
andykaylor wrote:
I'm starting to be uncomfortable with the amount of alignment and
LValueBaseInfo support we've skipped over. I tried to add markers in this PR
where I wasn't adding support for those. I intend to fill in that support in a
separate PR soon.
https://github.com/llvm/llvm-projec
https://github.com/cyndyishida approved this pull request.
LGTM. I was a bit worried about the fallout that other target triples using the
same sdks would now opt into this behavior but if that were the case they'd
already be running into modularization errors (e.g.
`found_incompatible_headers
https://github.com/Icohedron edited
https://github.com/llvm/llvm-project/pull/134171
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/DanielCChen closed
https://github.com/llvm/llvm-project/pull/134297
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
kraj wrote:
> @kraj, you approved this and you are a project member, are you comfortable
> merging this? If so, please go ahead.
>
> From my point of view as a clangd maintainer, I'm supportive of having such
> an option, but I have ~zero CMake knowledge, so if you think this needs more
> rev
https://github.com/fmayer edited
https://github.com/llvm/llvm-project/pull/134310
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/phoebewang closed
https://github.com/llvm/llvm-project/pull/134240
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Phoebe Wang
Date: 2025-04-04T11:27:39+08:00
New Revision: 897f9a51b981c773a63dd94709d9de2442feb008
URL:
https://github.com/llvm/llvm-project/commit/897f9a51b981c773a63dd94709d9de2442feb008
DIFF:
https://github.com/llvm/llvm-project/commit/897f9a51b981c773a63dd94709d9de2442feb008.diff
L
https://github.com/irymarchyk converted_to_draft
https://github.com/llvm/llvm-project/pull/133598
___
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: Madhur Amilkanthwar (madhur13490)
Changes
The checks in init-aarch64.c expect macros to be back-to-back which seems very
strict. This change aims to relax this and use just AARCH64 instead of
AARCH64-NEXT. This way, we maintain the order
https://github.com/DanielCChen created
https://github.com/llvm/llvm-project/pull/134297
As suggested in PR #131041, this PR moves the code of `addFortranRuntimeLibs`
from `PPCLinux.cpp` to `Gnu.cpp` to generalize it for all Linux platform.
>From a7c791a7fe3a0606fc6b79368b32d599bdfbe2fb Mon Sep
thurstond wrote:
> Trap checks fail at most once (when the program crashes).
It's technically possible to have a signal handler that consumes SIGILL and
then jumps over the offending instruction. The UBSan docs allude to this:
"-fsanitize-trap=...: execute a trap instruction (doesn’t require U
https://github.com/arsenm requested changes to this pull request.
The other tests should be strengthened to always use -NEXT. The exact set of
macros should be tested, don't want others hiding in the gaps
https://github.com/llvm/llvm-project/pull/134338
llvmbot wrote:
@llvm/pr-subscribers-clang-format
Author: Ivan (irymarchyk)
Changes
The current clang-format configuration option AllowShortFunctionsOnASingleLine
uses a single enum (ShortFunctionStyle) to control when short function
definitions can be merged onto a single line. This enum
https://github.com/madhur13490 created
https://github.com/llvm/llvm-project/pull/134338
The checks in init-aarch64.c expect macros to be back-to-back which seems very
strict. This change aims to relax this and use just AARCH64 instead of
AARCH64-NEXT. This way, we maintain the order of the mac
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/irymarchyk created
https://github.com/llvm/llvm-project/pull/134337
The current clang-format configuration option AllowShortFunctionsOnASingleLine
uses a single enum (ShortFunctionStyle) to control when short function
definitions can be merged onto a single line. This enum p
https://github.com/AaronBallman edited
https://github.com/llvm/llvm-project/pull/133472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -87,6 +90,15 @@ define <2 x double> @f7(<2 x double> %dummy, <2 x double>
%val1,
ret <2 x double> %ret
}
+; Test the fminh library function.
+define half @f11_half(half %dummy, half %val1, half %val2) {
+; CHECK-LABEL: f11_half:
+; CHECK: %r14, fminh@PLT
@@ -0,0 +1,115 @@
+//===--- RunOnNewStack.cpp - Crash Recovery
---===//
+//
+// 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
@@ -280,6 +280,22 @@ constexpr bool4 isinf(double4 V) { return
isinf((float4)V); }
_DXC_COMPAT_TERNARY_DOUBLE_OVERLOADS(lerp)
_DXC_COMPAT_TERNARY_INTEGER_OVERLOADS(lerp)
+//===--===//
+// lit builtins overloa
@@ -25,6 +25,147 @@ using namespace clang;
using namespace clang::CIRGen;
using namespace cir;
+/// Given an expression of pointer type, try to
+/// derive a more accurate bound on the alignment of the pointer.
+Address CIRGenFunction::emitPointerWithAlignment(const Expr *expr
llvmbot wrote:
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-clang-codegen
Author: Florian Mayer (fmayer)
Changes
Trap checks fail at most once (when the program crashes).
---
Patch is 22.09 KiB, truncated to 20.00 KiB below, full version:
https://github.com/llvm/llvm-project/pull/13
https://github.com/Icohedron edited
https://github.com/llvm/llvm-project/pull/134171
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
HighCommander4 wrote:
@kraj, you approved this and you are a project member, are you comfortable
merging this? If so, please go ahead.
>From my point of view as a clangd maintainer, I'm supportive of having such an
>option, but I have ~zero CMake knowledge, so if you think this needs more
>re
@@ -280,6 +280,22 @@ constexpr bool4 isinf(double4 V) { return
isinf((float4)V); }
_DXC_COMPAT_TERNARY_DOUBLE_OVERLOADS(lerp)
_DXC_COMPAT_TERNARY_INTEGER_OVERLOADS(lerp)
+//===--===//
+// lit builtins overloa
Lai-YT wrote:
> Why is this a module flag, instead of a function attribute?
The other value handled by the _NVVMReflect_ pass is `"__CUDA_FTZ"`, which
Clang currently sets via a module flag. I followed the same approach here for
consistency.
Also, since the decision to use precise square root
https://github.com/fmayer ready_for_review
https://github.com/llvm/llvm-project/pull/134310
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/andykaylor updated
https://github.com/llvm/llvm-project/pull/134181
>From 54454e4d52570f29c493c41fc9bf95cbaf9e0886 Mon Sep 17 00:00:00 2001
From: Andy Kaylor
Date: Fri, 21 Mar 2025 09:46:27 -0700
Subject: [PATCH 1/3] [CIR] Upstream support for break and continue statements
T
https://github.com/kmpeng edited
https://github.com/llvm/llvm-project/pull/134171
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: NAKAMURA Takumi
Date: 2025-04-04T11:05:46+09:00
New Revision: 4088c70f4e7eae0bfc2916cc88c7301ec5e19daf
URL:
https://github.com/llvm/llvm-project/commit/4088c70f4e7eae0bfc2916cc88c7301ec5e19daf
DIFF:
https://github.com/llvm/llvm-project/commit/4088c70f4e7eae0bfc2916cc88c7301ec5e19daf.dif
Andres-Salamanca wrote:
@andykaylor
https://github.com/llvm/llvm-project/pull/134333
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -193,8 +334,23 @@ LValue CIRGenFunction::emitUnaryOpLValue(const
UnaryOperator *e) {
switch (op) {
case UO_Deref: {
-cgm.errorNYI(e->getSourceRange(), "UnaryOp dereference");
-return LValue();
+QualType t = e->getSubExpr()->getType()->getPointeeType();
+
llvmbot wrote:
@llvm/pr-subscribers-clangir
Author: None (Andres-Salamanca)
Changes
This patch adds support for if statements in the CIR dialect
Additionally, multiple RUN lines were introduced to improve codegen test
coverage
---
Patch is 43.50 KiB, truncated to 20.00 KiB below, full v
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (Andres-Salamanca)
Changes
This patch adds support for if statements in the CIR dialect
Additionally, multiple RUN lines were introduced to improve codegen test
coverage
---
Patch is 43.50 KiB, truncated to 20.00 KiB below, full ver
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 edited
https://github.com/llvm/llvm-project/pull/134181
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Andres-Salamanca created
https://github.com/llvm/llvm-project/pull/134333
This patch adds support for if statements in the CIR dialect
Additionally, multiple RUN lines were introduced to improve codegen test
coverage
>From 89f0f528f981223273b2c1548c9a71f2ceeca329 Mon Sep 17
YLChenZ wrote:
Hi @AaronBallman, bothering you again. I have a doubt about the merge of the
following case:
There is a lot of content that is `No documentation`, and to merge these
entri
https://github.com/erichkeane approved this pull request.
1 concern, else lgtm.
https://github.com/llvm/llvm-project/pull/134317
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/erichkeane edited
https://github.com/llvm/llvm-project/pull/134317
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -569,6 +569,36 @@ def YieldOp : CIR_Op<"yield", [ReturnLike, Terminator,
];
}
+//===--===//
+// BreakOp
+//===--===//
+
+def BreakOp : C
https://github.com/erichkeane approved this pull request.
1 Possible nit, else LGTM.
https://github.com/llvm/llvm-project/pull/134181
___
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.
Thanks for looking into that! That makes sense. LGTM.
https://github.com/llvm/llvm-project/pull/133966
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mai
@@ -1358,6 +1360,33 @@ mlir::Value
CIRGenFunction::emitScalarConversion(mlir::Value src,
.emitScalarConversion(src, srcTy, dstTy, loc);
}
+mlir::Value ScalarExprEmitter::VisitUnaryLNot(const UnaryOperator *e) {
+ // Perform vector logical not on comparison with zero ve
@@ -280,6 +280,22 @@ constexpr bool4 isinf(double4 V) { return
isinf((float4)V); }
_DXC_COMPAT_TERNARY_DOUBLE_OVERLOADS(lerp)
_DXC_COMPAT_TERNARY_INTEGER_OVERLOADS(lerp)
+//===--===//
+// lit builtins overloa
@@ -679,20 +679,18 @@ llvm::ARM::FPUKind arm::getARMTargetFeatures(const Driver
&D,
CPUArgFPUKind != llvm::ARM::FK_INVALID ? CPUArgFPUKind :
ArchArgFPUKind;
(void)llvm::ARM::getFPUFeatures(FPUKind, Features);
} else {
-bool Generic = true;
-if (!ForAS) {
llvmbot wrote:
@llvm/pr-subscribers-backend-directx
Author: Steven Perron (s-perron)
Changes
HLSL has three levels of visibility for functions. See section 3.6 of
the [HLSL spec](https://microsoft.github.io/hlsl-specs/specs/hlsl.pdf)
for details.
1. Functions marked `static` have internal
https://github.com/mizvekov closed
https://github.com/llvm/llvm-project/pull/134142
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Bigcheese updated
https://github.com/llvm/llvm-project/pull/133173
>From cc251995b3d55b3cd76b0b65753be88c9fb9d627 Mon Sep 17 00:00:00 2001
From: Michael Spencer
Date: Wed, 26 Mar 2025 14:48:19 -0700
Subject: [PATCH] [llvm][clang] Allocate a new stack instead of spawning a new
https://github.com/Bigcheese updated
https://github.com/llvm/llvm-project/pull/132853
>From d19d7c6314dbb68abfe7cdceebd8e8f65aedddc5 Mon Sep 17 00:00:00 2001
From: Michael Spencer
Date: Wed, 29 Jan 2025 12:49:29 -0800
Subject: [PATCH] [clang][modules] Lazily load by name lookups in module maps
https://github.com/Bigcheese updated
https://github.com/llvm/llvm-project/pull/132853
>From d19d7c6314dbb68abfe7cdceebd8e8f65aedddc5 Mon Sep 17 00:00:00 2001
From: Michael Spencer
Date: Wed, 29 Jan 2025 12:49:29 -0800
Subject: [PATCH 1/2] [clang][modules] Lazily load by name lookups in module
@@ -280,6 +280,22 @@ constexpr bool4 isinf(double4 V) { return
isinf((float4)V); }
_DXC_COMPAT_TERNARY_DOUBLE_OVERLOADS(lerp)
_DXC_COMPAT_TERNARY_INTEGER_OVERLOADS(lerp)
+//===--===//
+// lit builtins overloa
@@ -2314,6 +2317,12 @@ static Value *upgradeNVVMIntrinsicCall(StringRef Name,
CallBase *CI,
Value *Val = CI->getArgOperand(1);
Rep = Builder.CreateAtomicRMW(AtomicRMWInst::FAdd, Ptr, Val, MaybeAlign(),
AtomicOrdering::SequentiallyConsi
https://github.com/e-kud approved this pull request.
LGTM. Looks like the last nep.
https://github.com/llvm/llvm-project/pull/134240
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,3329 @@
+// RUN: %clang_cc1 -triple nvptx-unknown-unknown -fcuda-is-device -O3 -o - %s
-emit-llvm | FileCheck %s
+// RUN: %clang_cc1 -triple nvptx64-unknown-unknown -fcuda-is-device -O3 -o -
%s -emit-llvm | FileCheck %s
+#include "../Headers/Inputs/include/cuda.h"
---
@@ -0,0 +1,3329 @@
+// RUN: %clang_cc1 -triple nvptx-unknown-unknown -fcuda-is-device -O3 -o - %s
-emit-llvm | FileCheck %s
+// RUN: %clang_cc1 -triple nvptx64-unknown-unknown -fcuda-is-device -O3 -o -
%s -emit-llvm | FileCheck %s
+#include "../Headers/Inputs/include/cuda.h"
---
ian-twilightcoder wrote:
> LGTM. I was a bit worried about the fallout that other target triples using
> the same sdks would now opt into this behavior but if that were the case
> they'd already be running into modularization errors (e.g.
> `found_incompatible_headers__check_search_paths`)
Ot
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 --
clang/include/clang/CIR/Dialect/Builder/CIRBaseBuil
@@ -280,6 +280,22 @@ constexpr bool4 isinf(double4 V) { return
isinf((float4)V); }
_DXC_COMPAT_TERNARY_DOUBLE_OVERLOADS(lerp)
_DXC_COMPAT_TERNARY_INTEGER_OVERLOADS(lerp)
+//===--===//
+// lit builtins overloa
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib`
running on `gribozavr4` while building `clang` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/60/builds/23834
Here is the relevant piece of t
https://github.com/ilovepi edited
https://github.com/llvm/llvm-project/pull/134298
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,25 @@
+//===-- File.h --- File Helpers ---*- 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: Apache-2.0 WITH LLV
https://github.com/ilovepi approved this pull request.
Since this just moves common code I think this is fine for now. We should
revisit some of the interfaces though, especially the ones that return
SmallString<128>. I think there is also a Path API that handles relative
paths, so we can per
https://github.com/fmayer updated
https://github.com/llvm/llvm-project/pull/134310
>From 44f9ccd6b4104fb07ad9cf9581c41c6d473525ec Mon Sep 17 00:00:00 2001
From: Florian Mayer
Date: Thu, 3 Apr 2025 14:53:29 -0700
Subject: [PATCH 1/6] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20in?=
=?UTF
@@ -0,0 +1,25 @@
+//===-- File.h --- File Helpers ---*- 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: Apache-2.0 WITH LLV
https://github.com/fmayer updated
https://github.com/llvm/llvm-project/pull/134310
>From 44f9ccd6b4104fb07ad9cf9581c41c6d473525ec Mon Sep 17 00:00:00 2001
From: Florian Mayer
Date: Thu, 3 Apr 2025 14:53:29 -0700
Subject: [PATCH 1/5] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20in?=
=?UTF
DanielCChen wrote:
Seems PR #134320 is fixing this.
https://github.com/llvm/llvm-project/pull/131041
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/fmayer updated
https://github.com/llvm/llvm-project/pull/134310
>From 44f9ccd6b4104fb07ad9cf9581c41c6d473525ec Mon Sep 17 00:00:00 2001
From: Florian Mayer
Date: Thu, 3 Apr 2025 14:53:29 -0700
Subject: [PATCH 1/4] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20in?=
=?UTF
https://github.com/yxsamliu closed
https://github.com/llvm/llvm-project/pull/133456
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -49,6 +51,135 @@ LLVM_INSTANTIATE_REGISTRY(FrontendPluginRegistry)
namespace {
+/// Dumps deserialized declarations.
VitaNuo wrote:
> If you want, you might use a comment to explain other non-trivial details,
> though, e.g. how the class must be used or
@@ -253,6 +253,37 @@ const inline float
length(__detail::HLSL_FIXED_VECTOR X) {
return __detail::length_vec_impl(X);
}
+//===--===//
+// lit builtins
+//===--
@@ -265,3 +265,125 @@ void test_empty_while_true() {
// OGCG: br label %[[WHILE_BODY:.*]]
// OGCG: [[WHILE_BODY]]:
// OGCG: ret void
+
+void unreachable_after_continue() {
+ for (;;) {
+continue;
+int x = 1;
+ }
+}
+
+// CIR: cir.func @unreachable_after_continue
+
https://github.com/kmpeng updated
https://github.com/llvm/llvm-project/pull/134171
>From 719bb94279f64f134c826faa22898e4e549bb23c Mon Sep 17 00:00:00 2001
From: kmpeng
Date: Thu, 27 Mar 2025 14:39:27 -0700
Subject: [PATCH 1/9] finished lit implementation, added codegen and sema tests
---
.../
ilovepi wrote:
ah, right. I forgot we build things under `utils` that's a much better place
for this.
Overall the patch is much better. Once it's moved to `utils` I think it will be
good. @nikic I seem to recall that we now prefer markdown over `.rst` files.
Is that correct? I tried to find
@@ -253,6 +253,37 @@ const inline float
length(__detail::HLSL_FIXED_VECTOR X) {
return __detail::length_vec_impl(X);
}
+//===--===//
+// lit builtins
+//===--
@@ -126,3 +138,23 @@ define void @f9(ptr %cptr, ptr %aptr, ptr %bptr) {
store fp128 %c, ptr %cptr
ret void
}
+
+; Test f16 copies in which the sign comes from an f16.
+define half @f10(half %a, half %b) {
+; CHECK-LABEL: f10:
+; CHECK: brasl %r14, copysignh@PLT
aaronpuchert wrote:
Maybe the test needs to be relaxed a bit because of stack layout differences in
other OS targets? Although I'm not sure why they're different. See
https://lab.llvm.org/buildbot/#/builders/186/builds/7896:
```
TEST 'AddressSanitizer-arm-android ::
TestCa
klausler wrote:
```
FAIL: Flang :: Driver/linker-flags.f90 (1 of 3430)
TEST 'Flang :: Driver/linker-flags.f90' FAILED
Exit Code: 1
Command Output (stderr):
--
/home/pklausler/llvm-project/build/x86/gcc/9.3.0/Release/shared/bin/flang -###
--target=ppc64
jrtc27 wrote:
> I think you also need to fix the backends so if they see thread_pointer
> intrinsic with the wrong address-space, they don't crash.
I don't believe they do crash? At least, I can't construct IR using any
addrspace (even some of the special X86 ones) that makes amd64/aarch64/ris
https://github.com/metkarpoonam updated
https://github.com/llvm/llvm-project/pull/133828
>From 3a45246453d120da108e597d23da0fb8d9df0b1b Mon Sep 17 00:00:00 2001
From: Poonam Vilas Metkar
Date: Mon, 31 Mar 2025 16:49:18 -0700
Subject: [PATCH 1/8] Implement a dst function with test cases for HLSL
https://github.com/ian-twilightcoder closed
https://github.com/llvm/llvm-project/pull/134005
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Ian Anderson
Date: 2025-04-03T16:09:57-07:00
New Revision: bd197ca00365cd35002792324bd149f71e864e1a
URL:
https://github.com/llvm/llvm-project/commit/bd197ca00365cd35002792324bd149f71e864e1a
DIFF:
https://github.com/llvm/llvm-project/commit/bd197ca00365cd35002792324bd149f71e864e1a.diff
@@ -424,8 +432,19 @@ std::string Linux::computeSysRoot() const {
const StringRef InstallDir = GCCInstallation.getInstallPath();
const StringRef TripleStr = GCCInstallation.getTriple().str();
const Multilib &Multilib = GCCInstallation.getMultilib();
+ std::string Path;
+
1 - 100 of 447 matches
Mail list logo
