shiltian wrote:
> Don't see how that could be related; you can losslessly bitconvert between
> i16 and bfloat
Yes, `canLosslesslyBitCastTo` doesn't allow cast between `i16` and `bfloat`,
but it does between two vectors, as long as their sizes are the same.
> A cast between float and int
@@ -12696,6 +12696,56 @@ bool IntExprEvaluator::VisitBuiltinCallExpr(const
CallExpr *E,
return BuiltinOp == Builtin::BI__atomic_always_lock_free ?
Success(0, E) : Error(E);
}
+ case Builtin::BI__builtin_addcb:
+ case Builtin::BI__builtin_addcs:
+ case
@@ -416,11 +419,124 @@ bool BPFCheckAndAdjustIR::removeGEPBuiltins(Module ) {
return Changed;
}
+// Wrap ToWrap with cast to address space zero:
+// - if ToWrap is a getelementptr,
+// wrap it's base pointer instead and return a copy;
+// - if ToWrap is Instruction,
https://github.com/Pierre-vh closed
https://github.com/llvm/llvm-project/pull/81718
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Pierre van Houtryve
Date: 2024-02-14T15:19:04+01:00
New Revision: 43c7eb5d7b237bc18385f0a5529f1e4b8bf4d6a3
URL:
https://github.com/llvm/llvm-project/commit/43c7eb5d7b237bc18385f0a5529f1e4b8bf4d6a3
DIFF:
https://github.com/kzhuravl approved this pull request.
Thanks!
https://github.com/llvm/llvm-project/pull/81718
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/chapuni closed
https://github.com/llvm/llvm-project/pull/81221
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: NAKAMURA Takumi
Date: 2024-02-14T23:17:00+09:00
New Revision: 1a1fcacbce805e3c409d9d41de61413e3fd8aa36
URL:
https://github.com/llvm/llvm-project/commit/1a1fcacbce805e3c409d9d41de61413e3fd8aa36
DIFF:
https://github.com/AaronBallman closed
https://github.com/llvm/llvm-project/pull/81658
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Aaron Ballman
Date: 2024-02-14T09:08:28-05:00
New Revision: 8e24bc096dcd0013d802e59a45803c51796dec0a
URL:
https://github.com/llvm/llvm-project/commit/8e24bc096dcd0013d802e59a45803c51796dec0a
DIFF:
https://github.com/llvm/llvm-project/commit/8e24bc096dcd0013d802e59a45803c51796dec0a.diff
usx95 wrote:
> Is there a valid use for having "EHCleanup" that _doesn't_ handle branches
> across it? That is, do we _ever_ need a cleanup to be called only for an
> exception thrown, and not otherwise leaving the scope? I'm just wondering if
> we can simplify things conceptually here and
DavidSpickett wrote:
Fixed the warning.
https://github.com/llvm/llvm-project/pull/81726
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/81726
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
arsenm wrote:
We're gradually converging on something that looks like this, subject to bike
shedding the name
https://github.com/llvm/llvm-project/pull/69229
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/81726
>From 74fe9a47aecac7f7d16485d11781c9cc92229429 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Wed, 14 Feb 2024 11:20:51 +
Subject: [PATCH 1/2] [clang][flang][driver] Correct program names in
https://github.com/chapuni updated
https://github.com/llvm/llvm-project/pull/81221
>From 66bb6cc3fd339360c16c6a98ce08f34978f665e0 Mon Sep 17 00:00:00 2001
From: NAKAMURA Takumi
Date: Fri, 9 Feb 2024 07:56:51 +0900
Subject: [PATCH 1/4] [MC/DC] Refactor: Introduce `ConditionIDs` as
https://github.com/AaronBallman edited
https://github.com/llvm/llvm-project/pull/81658
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
AaronBallman wrote:
> We could consider keeping the warning group, not actually guarding any
> warning, so we don't warn on `-Wno-gnu-binary-literal`.
That's a good idea, I've done that and updated the release notes accordingly.
https://github.com/llvm/llvm-project/pull/81658
https://github.com/AaronBallman approved this pull request.
Aside from a minor nit with the documentation, LGTM!
https://github.com/llvm/llvm-project/pull/81207
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
@@ -297,6 +297,12 @@ DWARF Support in Clang
Floating Point Support in Clang
---
+Fixed Point Support in Clang
+---
AaronBallman wrote:
```suggestion
Fixed Point Support in Clang
https://github.com/AaronBallman edited
https://github.com/llvm/llvm-project/pull/81207
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,67 @@
+/// Assert the fixed point precision macros according to N1169 7.18a.3 are
+/// defined when -ffixed-point is provided.
+
+// RUN: %clang_cc1 -triple=x86_64 -E -dM -ffixed-point -x c < /dev/null |
FileCheck -match-full-lines %s
+// RUN: %clang_cc1
@@ -324,6 +326,19 @@ class ScalarExprEmitter
void EmitIntegerSignChangeCheck(Value *Src, QualType SrcType, Value *Dst,
QualType DstType, SourceLocation Loc);
+ /// Emit a check that an [implicit] truncation of a bitfield does not
+ ///
@@ -1035,7 +1050,7 @@ EmitIntegerTruncationCheckHelper(Value *Src, QualType
SrcType, Value *Dst,
}
llvm::Value *Check = nullptr;
- // 1. Extend the truncated value back to the same width as the Src.
+ // 1. Convert the Dst back to the same type as Src.
@@ -1097,6 +1112,27 @@ void ScalarExprEmitter::EmitIntegerTruncationCheck(Value
*Src, QualType SrcType,
{Src, Dst});
}
+static llvm::Value *EmitIsNegativeTestHelper(Value *V, QualType VType,
+ const char *Name,
+
@@ -1097,6 +1112,27 @@ void ScalarExprEmitter::EmitIntegerTruncationCheck(Value
*Src, QualType SrcType,
{Src, Dst});
}
+static llvm::Value *EmitIsNegativeTestHelper(Value *V, QualType VType,
+ const char *Name,
+
@@ -5570,11 +5570,44 @@ LValue CodeGenFunction::EmitBinaryOperatorLValue(const
BinaryOperator *E) {
break;
}
-RValue RV = EmitAnyExpr(E->getRHS());
+llvm::Value *Previous = nullptr;
+RValue RV;
+QualType SrcType = E->getRHS()->getType();
+// If
@@ -122,6 +122,26 @@ Non-comprehensive list of changes in this release
New Compiler Flags
--
+- ``-fsanitize=implicit-unsigned-bitfield-truncation`` catches implicit
+ unsigned conversions involving bitfields.
+-
https://github.com/hnakamura5 updated
https://github.com/llvm/llvm-project/pull/81611
>From 7ee4b35f0aed434053b6fd6329ef39de97bc22db Mon Sep 17 00:00:00 2001
From: hnakamura5
Date: Tue, 13 Feb 2024 23:50:15 +0900
Subject: [PATCH 1/5] [clang-format] Support of TableGen basic format
DavidSpickett wrote:
Yes I had to disable sphix -Werr for that, I will try to fix it.
https://github.com/llvm/llvm-project/pull/81726
___
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 ea8de6e4336cf82aa541c6ad951b62585c3ea55c
43ad7755bf78df4141baf53dad977379482d1e94 --
https://github.com/hnakamura5 updated
https://github.com/llvm/llvm-project/pull/81611
>From 7ee4b35f0aed434053b6fd6329ef39de97bc22db Mon Sep 17 00:00:00 2001
From: hnakamura5
Date: Tue, 13 Feb 2024 23:50:15 +0900
Subject: [PATCH 1/4] [clang-format] Support of TableGen basic format
https://github.com/hnakamura5 updated
https://github.com/llvm/llvm-project/pull/81611
>From 7ee4b35f0aed434053b6fd6329ef39de97bc22db Mon Sep 17 00:00:00 2001
From: hnakamura5
Date: Tue, 13 Feb 2024 23:50:15 +0900
Subject: [PATCH 1/4] [clang-format] Support of TableGen basic format
nikic wrote:
> I think the right fix is teaching that function about FP <-> INT casts.
The documentation for that function says:
```
/// Return true if this type could be converted with a lossless BitCast to
/// type 'Ty'. For example, i8* to i32*. BitCasts are valid for types of the
///
kiranchandramohan wrote:
Unrelated, but just wanted to bring this up since you are working in this area
and distinguishing between Flang and Clang. Flang does not generate the
Diagnostics Reference and hence ends up with the warning (see below) in the
docs CI
Author: David Spickett
Date: 2024-02-14T12:51:30Z
New Revision: c5e13840fdc20adce51673a63d5703bf1ed02aba
URL:
https://github.com/llvm/llvm-project/commit/c5e13840fdc20adce51673a63d5703bf1ed02aba
DIFF:
https://github.com/llvm/llvm-project/commit/c5e13840fdc20adce51673a63d5703bf1ed02aba.diff
DavidSpickett wrote:
@llvm/pr-subscribers-flang-driver
https://github.com/llvm/llvm-project/pull/81726
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Vlad Serebrennikov
Date: 2024-02-14T16:39:00+04:00
New Revision: 502756905c7de5f6217a071b73adda72c46ffd1c
URL:
https://github.com/llvm/llvm-project/commit/502756905c7de5f6217a071b73adda72c46ffd1c
DIFF:
https://github.com/Endilll closed
https://github.com/llvm/llvm-project/pull/81542
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/Endilll edited
https://github.com/llvm/llvm-project/pull/81542
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
tru wrote:
cc @sylvain-audi
https://github.com/llvm/llvm-project/pull/81677
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Pierre-vh wrote:
> > Sorry, I should have clearly mentioned that. Yes, it is for my followup
> > change #80908. In #80908, we changed the type of LLVM builtin but kept the
> > corresponding clang builtin unchanged to avoid breaking existing uses.
>
> Don't see how that could be related; you
https://github.com/dtcxzyw edited
https://github.com/llvm/llvm-project/pull/81727
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
quic-garvgupt wrote:
Hi
@jonathonpenix @apazos @kito-cheng @asb @MaskRay - Requesting for adding as
reviewers to review the PR. Thanks in advance!
https://github.com/llvm/llvm-project/pull/81727
___
cfe-commits mailing list
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Garvit Gupta (quic-garvgupt)
Changes
The below culprit patch enabled the generation of asynchronous unwind tables
(-funwind-tables=2) by default for RISCV for both linux and RISCVToolChain
baremetal object. However, since there
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,
https://github.com/quic-garvgupt created
https://github.com/llvm/llvm-project/pull/81727
The below culprit patch enabled the generation of asynchronous unwind tables
(-funwind-tables=2) by default for RISCV for both linux and RISCVToolChain
baremetal object. However, since there are 2
DavidSpickett wrote:
To add program specific option help, my idea is to store mutliple strings in
the driver and select based on who's asking for the help.
I think that warrants its own change so I'm not attempting that here. Also,
there's only 2 flang options that refer to clang so it's not
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: David Spickett (DavidSpickett)
Changes
Currently https://flang.llvm.org/docs/FlangCommandLineReference.html refers to
"Clang" in several of the group descriptions for example:
```
Compilation options
Flags controlling the behavior of
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/81726
Currently https://flang.llvm.org/docs/FlangCommandLineReference.html refers to
"Clang" in several of the group descriptions for example:
```
Compilation options
Flags controlling the behavior of Clang
RKSimon wrote:
Why have the x86 tests been placed in test\CodeGen\X86 instead of something
like test\Transforms\ExpandVariadics\X86 ?
https://github.com/llvm/llvm-project/pull/81058
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-llvm-binary-utilities
Author: Pierre van Houtryve (Pierre-vh)
Changes
The dot is too confusing for tools. Output temporaries would have
'10.3-generic' so tools could parse it as an extension,
llvmbot wrote:
@llvm/pr-subscribers-backend-amdgpu
Author: Pierre van Houtryve (Pierre-vh)
Changes
The dot is too confusing for tools. Output temporaries would have
'10.3-generic' so tools could parse it as an extension, device libs the
associated clang driver logic are also confused
https://github.com/Pierre-vh created
https://github.com/llvm/llvm-project/pull/81718
The dot is too confusing for tools. Output temporaries would have
'10.3-generic' so tools could parse it as an extension, device libs & the
associated clang driver logic are also confused by the dot.
After
https://github.com/owenca approved this pull request.
https://github.com/llvm/llvm-project/pull/81591
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -12696,6 +12696,56 @@ bool IntExprEvaluator::VisitBuiltinCallExpr(const
CallExpr *E,
return BuiltinOp == Builtin::BI__atomic_always_lock_free ?
Success(0, E) : Error(E);
}
+ case Builtin::BI__builtin_addcb:
+ case Builtin::BI__builtin_addcs:
+ case
tschuett wrote:
Sorry for the confusion, but the codegen test showed it makes sense what you
are doing.
https://github.com/llvm/llvm-project/pull/81656
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
Author: Haojian Wu
Date: 2024-02-14T09:54:44+01:00
New Revision: 5932f3f861f84305bd01050d0af8e0dcb232a8b3
URL:
https://github.com/llvm/llvm-project/commit/5932f3f861f84305bd01050d0af8e0dcb232a8b3
DIFF:
https://github.com/llvm/llvm-project/commit/5932f3f861f84305bd01050d0af8e0dcb232a8b3.diff
https://github.com/pwprzybyla updated
https://github.com/llvm/llvm-project/pull/75031
>From ea4d54f574bbceafcd45a108a8688b0a5cfeb0a4 Mon Sep 17 00:00:00 2001
From: Piotr Przybyla
Date: Wed, 29 Nov 2023 14:05:00 +
Subject: [PATCH] Multilib support for libraries with exceptions and rtti
---
@@ -7513,6 +7516,41 @@ void Sema::checkCall(NamedDecl *FDecl, const
FunctionProtoType *Proto,
}
}
+auto *CallerFD = dyn_cast(CurContext);
+bool IsCalleeStreaming = ((ExtInfo.AArch64SMEAttributes &
+
@@ -12239,7 +12239,8 @@ bool Sema::CheckFunctionDeclaration(Scope *S,
FunctionDecl *NewFD,
if (UsesSM) {
sdesmalen-arm wrote:
The comment on line 12232-12233 needs an update.
https://github.com/llvm/llvm-project/pull/79842
@@ -12236,6 +12236,23 @@ bool Sema::CheckFunctionDeclaration(Scope *S,
FunctionDecl *NewFD,
bool UsesSM = NewFD->hasAttr();
bool UsesZA = Attr && Attr->isNewZA();
bool UsesZT0 = Attr && Attr->isNewZT0();
+
+if (UsesSM) {
+ if
@@ -445,3 +448,54 @@ void conflicting_state_attrs_preserves_out_zt0(void)
__arm_preserves("zt0") __ar
// expected-cpp-error@+2 {{conflicting attributes for state 'zt0'}}
// expected-error@+1 {{conflicting attributes for state 'zt0'}}
void
@@ -12236,6 +12236,23 @@ bool Sema::CheckFunctionDeclaration(Scope *S,
FunctionDecl *NewFD,
bool UsesSM = NewFD->hasAttr();
bool UsesZA = Attr && Attr->isNewZA();
bool UsesZT0 = Attr && Attr->isNewZT0();
+
+if (UsesSM) {
+ if
@@ -7513,6 +7516,41 @@ void Sema::checkCall(NamedDecl *FDecl, const
FunctionProtoType *Proto,
}
}
+auto *CallerFD = dyn_cast(CurContext);
+bool IsCalleeStreaming = ((ExtInfo.AArch64SMEAttributes &
+
@@ -3717,6 +3717,14 @@ def err_sme_definition_using_za_in_non_sme_target :
Error<
"function using ZA state requires 'sme'">;
def err_sme_definition_using_zt0_in_non_sme2_target : Error<
"function using ZT0 state requires 'sme2'">;
+def
@@ -7517,34 +7517,37 @@ void Sema::checkCall(NamedDecl *FDecl, const
FunctionProtoType *Proto,
}
auto *CallerFD = dyn_cast(CurContext);
-if (FD && CallerFD && Context.getTargetInfo().hasFeature("sme") &&
-!FD->getBuiltinID()) {
+bool IsCalleeStreaming
https://github.com/chapuni closed
https://github.com/llvm/llvm-project/pull/81497
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: NAKAMURA Takumi
Date: 2024-02-14T17:27:53+09:00
New Revision: 5c8985e7703b013c5df0612c3cbc1d333f4c5fa1
URL:
https://github.com/llvm/llvm-project/commit/5c8985e7703b013c5df0612c3cbc1d333f4c5fa1
DIFF:
https://github.com/chapuni edited
https://github.com/llvm/llvm-project/pull/81497
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -1130,14 +1129,13 @@ template <> struct MappingTraits {
// AlwaysBreakAfterReturnType was not, initialize the latter from the
// former for backwards compatibility.
rmarker wrote:
Done.
https://github.com/llvm/llvm-project/pull/81591
https://github.com/rmarker updated
https://github.com/llvm/llvm-project/pull/81591
>From a40215e93b3d27f77d9e5f7ff38883ab1d4fde9a Mon Sep 17 00:00:00 2001
From: rmarker
Date: Tue, 13 Feb 2024 21:09:57 +1030
Subject: [PATCH 1/3] [clang-format][NFC] Drop "Always" in
@@ -1871,10 +1869,10 @@ FormatStyle getWebKitStyle() {
FormatStyle getGNUStyle() {
FormatStyle Style = getLLVMStyle();
Style.AlwaysBreakAfterDefinitionReturnType = FormatStyle::DRTBS_All;
- Style.AlwaysBreakAfterReturnType = FormatStyle::RTBS_AllDefinitions;
https://github.com/rmarker updated
https://github.com/llvm/llvm-project/pull/81591
>From a40215e93b3d27f77d9e5f7ff38883ab1d4fde9a Mon Sep 17 00:00:00 2001
From: rmarker
Date: Tue, 13 Feb 2024 21:09:57 +1030
Subject: [PATCH 1/2] [clang-format][NFC] Drop "Always" in
https://github.com/domin144 updated
https://github.com/llvm/llvm-project/pull/81474
From 9ffef2685c2766c6944e368a739b8c94e9b68092 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dominik=20W=C3=B3jt?=
Date: Mon, 12 Feb 2024 13:38:14 +0100
Subject: [PATCH 1/2] [clang][AArch64] multilib: fix deduction
301 - 375 of 375 matches
Mail list logo
