zahiraam wrote:
Not very clear to me what the issue is. Can you please explain this in the
description. I think here the `#pragma float_control(precise, on)` should be
taking precedence over the `-ffast-math` flag and it's not. Right?
https://github.com/llvm/llvm-project/pull/105912
_
jemarch wrote:
> Merged #107343 into main.
I am preparing the corresponding patch for GCC.
https://github.com/llvm/llvm-project/pull/107343
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-c
Author: Dmitry Polukhin
Date: 2024-09-25T08:31:49+01:00
New Revision: 2ccac07bf22d17029d4437b0a727dd55c8c86d56
URL:
https://github.com/llvm/llvm-project/commit/2ccac07bf22d17029d4437b0a727dd55c8c86d56
DIFF:
https://github.com/llvm/llvm-project/commit/2ccac07bf22d17029d4437b0a727dd55c8c86d56.dif
https://github.com/dmpolukhin closed
https://github.com/llvm/llvm-project/pull/109167
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: CarolineConcatto
Date: 2024-09-25T09:53:23+01:00
New Revision: 445d8b2d10b2bb9a5f50e3fe0671045acd309a04
URL:
https://github.com/llvm/llvm-project/commit/445d8b2d10b2bb9a5f50e3fe0671045acd309a04
DIFF:
https://github.com/llvm/llvm-project/commit/445d8b2d10b2bb9a5f50e3fe0671045acd309a04.di
https://github.com/CarolineConcatto closed
https://github.com/llvm/llvm-project/pull/97755
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Benjamin Maxwell
Date: 2024-09-25T09:50:55+01:00
New Revision: 53907ed5081b6cfde6cbe147ab06a074a4f3e0ed
URL:
https://github.com/llvm/llvm-project/commit/53907ed5081b6cfde6cbe147ab06a074a4f3e0ed
DIFF:
https://github.com/llvm/llvm-project/commit/53907ed5081b6cfde6cbe147ab06a074a4f3e0ed.di
https://github.com/MacDue closed
https://github.com/llvm/llvm-project/pull/108853
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
DavidSpickett wrote:
I think
https://github.com/llvm/llvm-project/blob/5a191e3cd904b5fee202569e54fe04f91f1a697f/llvm/utils/lit/lit/llvm/config.py#L411
works such that if the messages cannot be found (cross compiling and such) we
default to asking Python what it thinks they should be.
I wonder
DavidSpickett wrote:
CI failure is:
```
_bk;t=1727216861348Timed Out Tests (1):
_bk;t=1727216861348 lldb-api ::
functionalities/fork/concurrent_vfork/TestConcurrentVFork.py
```
Ignore that it's due to https://github.com/llvm/llvm-project/issues/104609.
https://github.com/llvm/llvm-project
https://github.com/DavidSpickett approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/109852
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
sheredom wrote:
> Sorry for being slow to look at this in more detail:
No bother!
> > When generating a PCH map the original directory to some fake directory.
> > You could imagine D:/Foo being mapped to Z:/Foo for instance.
>
> Can you clarify what this means? Is `Z:/Foo` a virtual-only pat
@@ -167,12 +181,14 @@ install( FILES ${CMAKE_CURRENT_BINARY_DIR}/libclc.pc
DESTINATION "${CMAKE_INSTAL
install( DIRECTORY generic/include/clc DESTINATION
"${CMAKE_INSTALL_INCLUDEDIR}" )
if( ENABLE_RUNTIME_SUBNORMAL )
- add_library( subnormal_use_default STATIC
-generic/
https://github.com/frasercrmck created
https://github.com/llvm/llvm-project/pull/109926
The ARCHIVE artifact kind is not valid for install(FILES ...).
Additionally, install wasn't resolving the target's TARGET_FILE properly and
was trying to find it in the top-level build directory, rather tha
https://github.com/frasercrmck edited
https://github.com/llvm/llvm-project/pull/109926
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
frasercrmck wrote:
Thanks to @aaronpuchert for pointing this out in #87622.
https://github.com/llvm/llvm-project/pull/109926
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
4ast wrote:
> Also, just a heads-up: I think this PR is blocked by [an issue that I
> mentioned earlier on
> LKML](https://lore.kernel.org/all/zujillqbegosx...@google.com/) (Cc: @4ast).
> After that is resolved, I think we should change this PR to use `0x5` for the
> new mode modifiers (`BPF_
@@ -167,12 +181,14 @@ install( FILES ${CMAKE_CURRENT_BINARY_DIR}/libclc.pc
DESTINATION "${CMAKE_INSTAL
install( DIRECTORY generic/include/clc DESTINATION
"${CMAKE_INSTALL_INCLUDEDIR}" )
if( ENABLE_RUNTIME_SUBNORMAL )
- add_library( subnormal_use_default STATIC
-generic/
https://github.com/paulwalker-arm closed
https://github.com/llvm/llvm-project/pull/109423
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
farzonl wrote:
In light of sarah’s comment we probably do want those extra test cases I
mentioned here:
https://github.com/llvm/llvm-project/pull/108849#issuecomment-2372671949
https://github.com/llvm/llvm-project/pull/108849
_
https://github.com/farzonl edited
https://github.com/llvm/llvm-project/pull/108849
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
teresajohnson wrote:
> @teresajohnson Do you have any concern or comment on this direction?
Just a quick reply to say that I am taking a look today (unfamiliar with this
approach so need to read through the RFC etc) and will get back later today
https://github.com/llvm/llvm-project/pull/90933
Author: Thomas Köppe
Date: 2024-09-25T09:25:46-07:00
New Revision: cebb7c010854e39a77065cfd681db91a79e7ce15
URL:
https://github.com/llvm/llvm-project/commit/cebb7c010854e39a77065cfd681db91a79e7ce15
DIFF:
https://github.com/llvm/llvm-project/commit/cebb7c010854e39a77065cfd681db91a79e7ce15.diff
https://github.com/fmayer closed
https://github.com/llvm/llvm-project/pull/109169
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -7326,11 +7326,13 @@ void
ItaniumMangleContextImpl::mangleCXXCtorVTable(const CXXRecordDecl *RD,
raw_ostream &Out) {
// ::= TC _
CXXNameMangler Mangler(*this, Out);
+ QualType RDType = getASTContext().getRecordType
https://github.com/agozillon updated
https://github.com/llvm/llvm-project/pull/109907
>From 6e29de9836f49e49558e7810ec0a8084017c22b4 Mon Sep 17 00:00:00 2001
From: agozillon
Date: Wed, 25 Sep 2024 00:18:26 -0500
Subject: [PATCH 1/2] [Flang][Driver][Offload] Support -Xoffload-linker
argument in
agozillon wrote:
Added the new suggested test and removed the "--" couldn't see anything else
that might lead to failure, but we'll see how the CI feels about it, if it
doesn't like it please ignore the spam (and my appologies for it) on the PR as
I try to work out what the CI wants from me fo
https://github.com/jansvoboda11 created
https://github.com/llvm/llvm-project/pull/110014
Some `FileManager` APIs still return `{File,Directory}Entry` instead of the
preferred `{File,Directory}EntryRef`. These are documented to be deprecated,
but don't have the attribute that warns on their usa
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
Author: Jan Svoboda (jansvoboda11)
Changes
Some `FileManager` APIs still return `{File,Directory}Entry` instead of the
preferred `{File,Directory}EntryRef`. These are documented to be deprecated,
but don't have the attribute that warn
llvmbot wrote:
@llvm/pr-subscribers-clang-modules
Author: Jan Svoboda (jansvoboda11)
Changes
Some `FileManager` APIs still return `{File,Directory}Entry` instead of the
preferred `{File,Directory}EntryRef`. These are documented to be deprecated,
but don't have the attribute that warns on
@@ -66,12 +66,12 @@ NVPTXTargetInfo::NVPTXTargetInfo(const llvm::Triple &Triple,
HasFloat16 = true;
if (TargetPointerWidth == 32)
-resetDataLayout("e-p:32:32-i64:64-i128:128-v16:16-v32:32-n16:32:64");
+resetDataLayout("e-p:32:32-i64:64-i128:128-v16:16-v32:32-n16:32
JanekvO wrote:
Rebase
https://github.com/llvm/llvm-project/pull/102913
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
arsenm wrote:
> There are targets that use a different integer to denote flat (e.g. see SPIR
> & SPIR-V). Whilst I know that there are objections to that, the fact remains
> that they had historical reason (wanted to make legacy OCL convention that
> the default is private work, and given that
arsenm wrote:
> Just to clarify, does this mean any two non-flat address space pointers
> _cannot_ alias?
This should change nothing about aliasing. The IR assumption is any address
space may alias any other
https://github.com/llvm/llvm-project/pull/108786
___
@@ -2302,6 +2302,10 @@ def err_init_list_bad_dest_type : Error<
def warn_cxx20_compat_aggregate_init_with_ctors : Warning<
"aggregate initialization of type %0 with user-declared constructors "
"is incompatible with C++20">, DefaultIgnore, InGroup;
+def warn_cxx20_compat_re
@@ -4561,6 +4569,15 @@ static void TryConstructorInitialization(Sema &S,
CXXConstructorDecl *CtorDecl = cast(Best->Function);
if (Result != OR_Deleted) {
+if (!IsListInit && Kind.getKind() == InitializationKind::IK_Default &&
+DestRecordDecl != nullptr && DestR
@@ -6457,6 +6474,19 @@ void InitializationSequence::InitializeFrom(Sema &S,
}
}
+ if (!S.getLangOpts().CPlusPlus &&
+ Kind.getKind() == InitializationKind::IK_Default) {
+RecordDecl *Rec = DestType->getAsRecordDecl();
+if (Rec && Rec->hasUninitializedExplic
@@ -1419,6 +1419,44 @@ is not specified.
}];
}
+def ExplicitInitDocs : Documentation {
+ let Category = DocCatField;
+ let Content = [{
+The ``clang::requires_explicit_initialization`` attribute indicates that the
+field of an aggregate must be initialized explicitly by us
@@ -1682,7 +1690,7 @@ class DeclContext {
/// True if a valid hash is stored in ODRHash. This should shave off some
/// extra storage and prevent CXXRecordDecl to store unused bits.
-uint64_t ODRHash : 26;
+uint64_t ODRHash : 25;
erichkeane wro
@@ -3141,6 +3148,10 @@ def warn_attribute_ignored_no_calls_in_stmt: Warning<
"statement">,
InGroup;
+def warn_attribute_needs_aggregate : Warning<
erichkeane wrote:
This seems like it should be an error here, mis-use of this should be an error
IMO.
http
@@ -4561,6 +4569,15 @@ static void TryConstructorInitialization(Sema &S,
CXXConstructorDecl *CtorDecl = cast(Best->Function);
if (Result != OR_Deleted) {
+if (!IsListInit && Kind.getKind() == InitializationKind::IK_Default &&
+DestRecordDecl != nullptr && DestR
@@ -1925,8 +1921,8 @@ ModuleLoadResult
CompilerInstance::findOrCompileModuleAndReadAST(
M = HS.lookupModule(ModuleName, ImportLoc, true, !IsInclusionDirective);
// Check whether M refers to the file in the prebuilt module path.
-if (M && M->getASTFile())
- if
llvmbot wrote:
@llvm/pr-subscribers-libunwind
Author: Louis Dionne (ldionne)
Changes
This removes the need for macOS nodes in Buildkite. It also moves to the proper
way of testing backdeployment, which is to actually run on the target OS
itself, instead of using packaged dylibs from prev
@@ -199,7 +199,7 @@ int main(int argc, const char **argv) {
for (auto I = Files.begin(), E = Files.end(); I != E; ++I) {
OS << " {\n";
OS << "\"FilePath\": \"" << *I << "\",\n";
-const auto Entry = FileMgr.getFile(*I);
+const auto Entr
@@ -427,12 +427,8 @@ static void InitializeFileRemapping(DiagnosticsEngine
&Diags,
}
// Create the file entry for the file that we're mapping from.
-const FileEntry *FromFile =
-FileMgr.getVirtualFile(RF.first, ToFile->getSize(), 0);
-if (!FromFile) {
llvmbot wrote:
@llvm/pr-subscribers-github-workflow
Author: Louis Dionne (ldionne)
Changes
This removes the need for macOS nodes in Buildkite. It also moves to the proper
way of testing backdeployment, which is to actually run on the target OS
itself, instead of using packaged dylibs fro
@@ -4561,6 +4569,15 @@ static void TryConstructorInitialization(Sema &S,
CXXConstructorDecl *CtorDecl = cast(Best->Function);
if (Result != OR_Deleted) {
+if (!IsListInit && Kind.getKind() == InitializationKind::IK_Default &&
+DestRecordDecl != nullptr && DestR
@@ -579,7 +579,7 @@ static StringRef computeDataLayout(const Triple &TT) {
"-p7:160:256:256:32-p8:128:128-p9:192:256:256:32-i64:64-v16:16-v24:32-"
"v32:32-v48:64-v96:"
"128-v192:256-v256:256-v512:512-v1024:1024-v2048:2048-n32:64-S32-A5-"
- "G
Author: Edd Dawson
Date: 2024-09-25T18:08:32+01:00
New Revision: 660ddb3a9357e766eb628abb8ea8c0776951d0db
URL:
https://github.com/llvm/llvm-project/commit/660ddb3a9357e766eb628abb8ea8c0776951d0db
DIFF:
https://github.com/llvm/llvm-project/commit/660ddb3a9357e766eb628abb8ea8c0776951d0db.diff
LO
https://github.com/benlangmuir approved this pull request.
Thanks for cleaning this up!
https://github.com/llvm/llvm-project/pull/110014
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jansvoboda11 closed
https://github.com/llvm/llvm-project/pull/110014
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Jan Svoboda
Date: 2024-09-25T10:36:44-07:00
New Revision: b1aea98cfa357e23f4bb52232da5f41781f23bff
URL:
https://github.com/llvm/llvm-project/commit/b1aea98cfa357e23f4bb52232da5f41781f23bff
DIFF:
https://github.com/llvm/llvm-project/commit/b1aea98cfa357e23f4bb52232da5f41781f23bff.diff
L
@@ -6014,6 +6014,10 @@ static void handleNoMergeAttr(Sema &S, Decl *D, const
ParsedAttr &AL) {
D->addAttr(NoMergeAttr::Create(S.Context, AL));
}
+static void handleExplicitInitAttr(Sema &S, Decl *D, const ParsedAttr &AL) {
+ D->addAttr(ExplicitInitAttr::Create(S.Context, A
@@ -2994,6 +2994,29 @@ A "convergencectrl" operand bundle is only valid on a
``convergent`` operation.
When present, the operand bundle must contain exactly one value of token type.
See the :doc:`ConvergentOperations` document for details.
+.. _ob_fpe:
+
+Floating-point Envir
Wilco1 wrote:
So looking at the TRMs, the cores support MTE2 or MTE3 (and MTE3 is again no
user visible change), but the hardware can be configured to only support MTE1.
[This is also explained
here](https://developer.arm.com/documentation/ka005919/1-0).
> I am not exposing any of +mte/+mte2
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-tools-extra,clang` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders
@@ -1279,6 +1279,9 @@ void Instruction::swapProfMetadata() {
void Instruction::copyMetadata(const Instruction &SrcInst,
ArrayRef WL) {
+ if (WL.empty() || is_contained(WL, LLVMContext::MD_dbg))
+setDebugLoc(SrcInst.getDebugLoc());
--
Author: Jan Svoboda
Date: 2024-09-25T10:54:40-07:00
New Revision: c71bfc59ee1cec32d56a82476461e242398f82ca
URL:
https://github.com/llvm/llvm-project/commit/c71bfc59ee1cec32d56a82476461e242398f82ca
DIFF:
https://github.com/llvm/llvm-project/commit/c71bfc59ee1cec32d56a82476461e242398f82ca.diff
L
Author: Lukacma
Date: 2024-09-25T17:00:40+01:00
New Revision: fff03b07c6048f2b9c45a9f71e6fb38e09d4856c
URL:
https://github.com/llvm/llvm-project/commit/fff03b07c6048f2b9c45a9f71e6fb38e09d4856c
DIFF:
https://github.com/llvm/llvm-project/commit/fff03b07c6048f2b9c45a9f71e6fb38e09d4856c.diff
LOG:
nico wrote:
The test is broken on trunk. It won't get more broken if you merge the fix. So
please merge, and if it helps, great.
https://github.com/llvm/llvm-project/pull/100128
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llv
https://github.com/Lukacma closed
https://github.com/llvm/llvm-project/pull/10
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
nico wrote:
Thanks for merging the fix! At least on one of my bots, it helped and it's
green again :)
https://github.com/llvm/llvm-project/pull/100128
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
farzonl wrote:
Good point. Yeah this needs to move to Semachecking, but we need `case
Builtin::BI__builtin_elementwise_fmod` in SemaHLSL for the half float check
https://github.com/llvm/llvm-project/pull/108849
___
c
spall wrote:
This code only runs if the language option is HLSL right?
https://github.com/llvm/llvm-project/pull/108849
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
spall wrote:
If this builtin is for clang and not just HLSL should the semantics checking be
in this file and not 'SemaChecking'?
https://github.com/llvm/llvm-project/pull/108849
___
cfe-commits mailing list
cfe-comm
@@ -0,0 +1,86 @@
+// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py
UTC_ARGS: --version 5
+
+// REQUIRES: aarch64-registered-target
+
+// RUN: %clang_cc1 -triple aarch64-none-linux-gnu -target-feature +bf16
-target-feature +sme -target-feature +sme2 -
@@ -1279,6 +1279,9 @@ void Instruction::swapProfMetadata() {
void Instruction::copyMetadata(const Instruction &SrcInst,
ArrayRef WL) {
+ if (WL.empty() || is_contained(WL, LLVMContext::MD_dbg))
+setDebugLoc(SrcInst.getDebugLoc());
--
agozillon wrote:
hm, weird it passed on my system and I made sure it was running by
intentionally failing it, I'll have a look into it and address it! And I'll add
the other format as well as an additional test thank you both.
https://github.com/llvm/llvm-project/pull/109907
__
spall wrote:
Glad to approve after this gets updated then!
https://github.com/llvm/llvm-project/pull/108849
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-c
https://github.com/rorth closed https://github.com/llvm/llvm-project/pull/107403
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Rainer Orth
Date: 2024-09-25T18:15:45+02:00
New Revision: d01e336336f2b7fb4137e3dcc7d5c0b06ca1f3d6
URL:
https://github.com/llvm/llvm-project/commit/d01e336336f2b7fb4137e3dcc7d5c0b06ca1f3d6
DIFF:
https://github.com/llvm/llvm-project/commit/d01e336336f2b7fb4137e3dcc7d5c0b06ca1f3d6.diff
L
https://github.com/ldionne updated
https://github.com/llvm/llvm-project/pull/109984
>From 6567a45fca93b81da2ccb0d596aa0be84666eab1 Mon Sep 17 00:00:00 2001
From: Louis Dionne
Date: Wed, 25 Sep 2024 09:55:53 -0400
Subject: [PATCH] [runtimes] Run backdeployment CI on Github hosted runners
This r
https://github.com/playstation-edd closed
https://github.com/llvm/llvm-project/pull/109796
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ldionne edited
https://github.com/llvm/llvm-project/pull/109984
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,23 @@
+! Check -B driver option.
+!
+! Target triple prefix is not detected for -B.
+! RUN: %flang %s -### -o %t.o -target i386-unknown-linux \
MaskRay wrote:
Use `--target=`
`-target ` has been deprecated since around clang 3.4
https://github.com/ll
@@ -1925,8 +1921,8 @@ ModuleLoadResult
CompilerInstance::findOrCompileModuleAndReadAST(
M = HS.lookupModule(ModuleName, ImportLoc, true, !IsInclusionDirective);
// Check whether M refers to the file in the prebuilt module path.
-if (M && M->getASTFile())
- if
https://github.com/jansvoboda11 updated
https://github.com/llvm/llvm-project/pull/110014
>From 6b413a95887bb12cf7bae647173dd7b3c6a47684 Mon Sep 17 00:00:00 2001
From: Jan Svoboda
Date: Mon, 23 Sep 2024 17:00:48 -0700
Subject: [PATCH 1/5] [clang] Formally deprecate `FileManager::getFile()`
---
https://github.com/higher-performance updated
https://github.com/llvm/llvm-project/pull/102040
>From 7ea9d3dbb6ff74ca3f7f9b9a0c589e4a0a3366f2 Mon Sep 17 00:00:00 2001
From: higher-performance
Date: Mon, 5 Aug 2024 15:04:19 -0400
Subject: [PATCH 1/2] Add Clang attribute to ensure that fields are
https://github.com/ldionne ready_for_review
https://github.com/llvm/llvm-project/pull/109984
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -1419,6 +1419,35 @@ is not specified.
}];
}
+def ExplicitInitDocs : Documentation {
higher-performance wrote:
Sure, please see update.
https://github.com/llvm/llvm-project/pull/102040
___
cfe-commits mailing l
@@ -81,6 +82,7 @@ CXXRecordDecl::DefinitionData::DefinitionData(CXXRecordDecl
*D)
HasPrivateFields(false), HasProtectedFields(false),
HasPublicFields(false), HasMutableFields(false),
HasVariantMembers(false),
HasOnlyCMembers(true), HasInitMethod(false),
Has
@@ -134,6 +134,25 @@ class RISCVTargetInfo : public TargetInfo {
bool validateGlobalRegisterVariable(StringRef RegName, unsigned RegSize,
bool &HasSizeMismatch) const override;
+
+ bool checkCFProtectionBranchSupported() const override
arsenm wrote:
> Both in InferAddressSpaces, and in Attributor, you don't really care about
> whether a flat address-space exists.
Right, this is more of an undesirable address space. Optimizations don't need
to know anything about its behavior beyond that.
> In reply to your question above
awson wrote:
@shafik ?
https://github.com/llvm/llvm-project/pull/96464
___
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: Oliver Stannard (ostannard)
Changes
This is a continuation of #102896 by @kiran-isaac, which gets
the `[[clang::musttail]]` attribute working for as many cases as possible in
the ARM backend.
This includes one target-independent LangRef
https://github.com/ostannard updated
https://github.com/llvm/llvm-project/pull/109943
>From f96d3a1a44ade11f5a9879b49bb3d5296c4b225e Mon Sep 17 00:00:00 2001
From: Oliver Stannard
Date: Thu, 9 May 2024 12:58:41 +0100
Subject: [PATCH 1/9] [ARM] Re-generate a test
---
llvm/test/CodeGen/ARM/fp-a
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 b75174d05aa033a382d4c088e96e068a774f46da
5ec1238756677fc68d3a4081b3d58e930d24b9ac --e
https://github.com/ostannard closed
https://github.com/llvm/llvm-project/pull/102896
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ostannard wrote:
Superseded by #109943.
https://github.com/llvm/llvm-project/pull/102896
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -357,6 +357,9 @@ class IRBuilderBase {
void setConstrainedFPCallAttr(CallBase *I) {
I->addFnAttr(Attribute::StrictFP);
+MemoryEffects ME = MemoryEffects::inaccessibleMemOnly();
arsenm wrote:
It shouldn't be necessary to touch the attributes. The
arsenm wrote:
Also it's silly that we need to do bitcode autoupgrade of "experimental"
intrinsics, but x86 started shipping with strictfp enabled in production before
they graduated. We might as well drop the experimental bit then
https://github.com/llvm/llvm-project/pull/109798
_
https://github.com/Lukacma updated
https://github.com/llvm/llvm-project/pull/100347
>From 4cbec87032166083624251f868ab1c60a7a266b4 Mon Sep 17 00:00:00 2001
From: Marian Lukac
Date: Wed, 24 Jul 2024 11:16:20 +
Subject: [PATCH 1/3] [AArch64] Implement NEON vscale intrinsics
---
clang/includ
https://github.com/SLTozer created
https://github.com/llvm/llvm-project/pull/11
Following the commit that added the fake use intrinsic to LLVM, this patch adds
a pair of flags for the clang frontend that emit fake use intrinsics, for the
purpose of extending the lifetime of variables (eith
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Stephen Tozer (SLTozer)
Changes
Following the commit that added the fake use intrinsic to LLVM, this patch adds
a pair of flags for the clang frontend that emit fake use intrinsics, for the
purpose of extending the lifetime of vari
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Stephen Tozer (SLTozer)
Changes
Following the commit that added the fake use intrinsic to LLVM, this patch adds
a pair of flags for the clang frontend that emit fake use intrinsics, for the
purpose of extending the lifetime of variables (
https://github.com/NagyDonat edited
https://github.com/llvm/llvm-project/pull/109804
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
dyung wrote:
@Lukacma the test you added,
CodeGen/aarch64-fp8-intrinsics/acle_sme2_fp8_scale.c, is failing on at least 2
bots, can you take a look and revert if you need time to investigate?
- https://lab.llvm.org/buildbot/#/builders/190/builds/6495
- https://lab.llvm.org/buildbot/#/builders/1
@@ -0,0 +1,503 @@
+
+Function Effect Analysis
+
+
+Introduction
+
+
+Clang Function Effect Analysis is a C++ language extension which can warn
about "unsafe"
+constructs. The feature is currently tailored for the Perform
@@ -0,0 +1,503 @@
+
+Function Effect Analysis
+
+
+Introduction
+
+
+Clang Function Effect Analysis is a C++ language extension which can warn
about "unsafe"
cjappl wrote:
May be worth documenting how t
@@ -0,0 +1,503 @@
+
+Function Effect Analysis
+
+
+Introduction
+
+
+Clang Function Effect Analysis is a C++ language extension which can warn
about "unsafe"
+constructs. The feature is currently tailored for the Perform
201 - 300 of 431 matches
Mail list logo
