llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-win-fast` running on `as-builder-3` while building `clang`
at step 6 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/2/builds/20755
Here is the relevant piece
MaskRay wrote:
> Thanks for working on this! This will be the first time I'm not going to
> oppose an effort to remove Native Client support 🎉 Although I am going to ask
> you to wait a couple of months to land it, until we finally turn it off for
> good and start deleting the support code fro
thurstond wrote:
If it is not quick and easy to fix forward, please consider reverting in the
meantime, so that the buildbots can be green and provide useful feedback to
contributors. Thanks!
https://github.com/llvm/llvm-project/pull/132748
___
cfe-c
https://github.com/DanielCChen edited
https://github.com/llvm/llvm-project/pull/134520
___
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: Daniel Chen (DanielCChen)
Changes
`addArchSpecificRPath` shoudl immediately return for AIX as AIX doesn't support
`rpath` option.
`getArchSpecificLibPaths` also needs to get the triple without the OS version
on AIX.
---
Full diff: https:
https://github.com/DanielCChen created
https://github.com/llvm/llvm-project/pull/134520
`addArchSpecificRPath` shoudl immediately return for AIX as AIX doesn't support
`rpath` option.
`getArchSpecificLibPaths` also needs to get the triple without the OS version
on AIX.
>From a3583c59f7797a40a
brad0 wrote:
@MaskRay Another thing I wanted to ask about was there were some tests I
removed with nacl in the name that used nacl triples as well as
rodata-section.s. I am not sure if any of them are still relevant outside of a
nacl environment. Should they be renamed and use a different trip
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?=
Message-ID:
In-Reply-To:
https://github.com/jeremyd2019 edited
https://github.com/llvm/llvm-project/pull/134494
___
cfe-commits mailing list
cfe-commits@lists.llvm.o
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?=
Message-ID:
In-Reply-To:
@@ -847,7 +847,11 @@ void llvm::sys::PrintStackTrace(raw_ostream &OS, int
Depth) {
const char *name = strrchr(dlinfo.dli_fname, '/');
if (!name)
+#ifdef __
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?=
Message-ID:
In-Reply-To:
@@ -847,7 +847,11 @@ void llvm::sys::PrintStackTrace(raw_ostream &OS, int
Depth) {
const char *name = strrchr(dlinfo.dli_fname, '/');
if (!name)
+#ifdef __
https://github.com/YutongZhuu ready_for_review
https://github.com/llvm/llvm-project/pull/133653
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/YutongZhuu edited
https://github.com/llvm/llvm-project/pull/133653
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca closed
https://github.com/llvm/llvm-project/pull/134473
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Owen Pan
Date: 2025-04-05T17:03:55-07:00
New Revision: aaaeb86acea77c5bcdb60011ce6aaaf4ebca4081
URL:
https://github.com/llvm/llvm-project/commit/aaaeb86acea77c5bcdb60011ce6aaaf4ebca4081
DIFF:
https://github.com/llvm/llvm-project/commit/aaaeb86acea77c5bcdb60011ce6aaaf4ebca4081.diff
LOG:
owenca wrote:
See #134514
https://github.com/llvm/llvm-project/pull/134472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca demilestoned
https://github.com/llvm/llvm-project/pull/134472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
roadswitcher wrote:
Closing on assumption there's a More Preferred way to build this with
gcc-toolset.
https://github.com/llvm/llvm-project/pull/128438
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/list
https://github.com/roadswitcher closed
https://github.com/llvm/llvm-project/pull/128438
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/mati865 edited
https://github.com/llvm/llvm-project/pull/134494
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -847,7 +847,11 @@ void llvm::sys::PrintStackTrace(raw_ostream &OS, int
Depth) {
const char *name = strrchr(dlinfo.dli_fname, '/');
if (!name)
+#ifdef __CYGWIN__
+ OS << format(" %-*s", width, &dlinfo.dli_fname);
mati865 wrote:
Good point, som
thurstond wrote:
> @thurstond Well can you provide a more recent buildbot failure link where
> #130182 is not on the list of possible culpirits? Because the link @fmayer
> provided for sure included it.
@mizvekov I localized the MSan error to this patch by re-running the buildbot
script with
owenca wrote:
> When I changed the `AlignConsecutiveAssignments` option, I was told to reuse
> the same option name. Now the program allows the user to specify the option
> as either a string or an associative array.
Reusing the option name is IMO better than adding `SFS_Custom`. @irymarchyk i
sstwcw wrote:
When I changed the `AlignConsecutiveAssignments` option, I was told to reuse
the same option name. Now the program allows the user to specify the option as
either a string or an associative array.
https://github.com/llvm/llvm-project/pull/134337
_
llvmbot wrote:
Failed to cherry-pick: d71ee7d23048ca64d14a7536927a006867cea39a
https://github.com/llvm/llvm-project/actions/runs/14285590977
Please manually backport the fix and push it to your github fork. Once this is
done, please create a [pull
request](https://github.com/llvm/llvm-proje
owenca wrote:
/cherry-pick d71ee7d23048ca64d14a7536927a006867cea39a
https://github.com/llvm/llvm-project/pull/134472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/owenca closed
https://github.com/llvm/llvm-project/pull/134472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Owen Pan
Date: 2025-04-05T13:35:45-07:00
New Revision: d71ee7d23048ca64d14a7536927a006867cea39a
URL:
https://github.com/llvm/llvm-project/commit/d71ee7d23048ca64d14a7536927a006867cea39a
DIFF:
https://github.com/llvm/llvm-project/commit/d71ee7d23048ca64d14a7536927a006867cea39a.diff
LOG:
owenca wrote:
> But why does this fix it?
See
[here](https://github.com/llvm/llvm-project/blob/52eb11f925ddeba4e1b3840fd636ee87387f3ada/clang/lib/Lex/Lexer.cpp#L3893).
Somehow I thought that setting C17 would also set C11. 😞
https://github.com/llvm/llvm-project/pull/134472
__
DanielCChen wrote:
> May I ask not to merge this yet? I have a question above, but I will not be
> at work until next Thursday to discuss this in a timely manner.
@vzakhari Sure, I will wait until you come back.
https://github.com/llvm/llvm-project/pull/134362
___
https://github.com/Artem-B closed
https://github.com/llvm/llvm-project/pull/132883
___
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 `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/5523
Here is the relevant piece of the bui
https://github.com/brad0 edited https://github.com/llvm/llvm-project/pull/133661
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -871,13 +871,81 @@ struct FormatStyle {
/// void f() { bar(); }
/// \endcode
SFS_All,
+/// Configure merge behavior using AllowShortFunctionsOnASingleLineOptions
+SFS_Custom,
};
/// Dependent on the value, ``int f() { return 0; }`` can be put on
@@ -5687,11 +5687,10 @@ bool TokenAnnotator::mustBreakBefore(const
AnnotatedLine &Line,
if (Right.is(tok::r_brace) && Left.is(tok::l_brace) &&
!Left.Children.empty()) {
// Support AllowShortFunctionsOnASingleLine for JavaScript.
- return Style.AllowShort
@@ -1907,6 +1954,8 @@ FormatStyle getMozillaStyle() {
FormatStyle MozillaStyle = getLLVMStyle();
MozillaStyle.AllowAllParametersOfDeclarationOnNextLine = false;
MozillaStyle.AllowShortFunctionsOnASingleLine = FormatStyle::SFS_Inline;
+ MozillaStyle.AllowShortFunctionsOnA
@@ -1893,6 +1938,8 @@ FormatStyle getChromiumStyle(FormatStyle::LanguageKind
Language) {
} else {
ChromiumStyle.AllowAllParametersOfDeclarationOnNextLine = false;
ChromiumStyle.AllowShortFunctionsOnASingleLine = FormatStyle::SFS_Inline;
+ChromiumStyle.AllowShortF
@@ -1501,6 +1536,8 @@ FormatStyle getLLVMStyle(FormatStyle::LanguageKind
Language) {
LLVMStyle.AllowShortCompoundRequirementOnASingleLine = true;
LLVMStyle.AllowShortEnumsOnASingleLine = true;
LLVMStyle.AllowShortFunctionsOnASingleLine = FormatStyle::SFS_All;
+ LLVMStyl
@@ -1472,6 +1483,30 @@ static void expandPresetsSpacesInParens(FormatStyle
&Expanded) {
Expanded.SpacesInParensOptions = {};
}
+static void expandPresetsShortFunctionsOnSingleLine(FormatStyle &Expanded) {
+ if (Expanded.AllowShortFunctionsOnASingleLine == FormatStyle::SFS_
https://github.com/HazardyKnusperkeks approved this pull request.
But why does this fix it?
https://github.com/llvm/llvm-project/pull/134472
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-com
mizvekov wrote:
@thurstond Well can you provide a more recent buildbot failure link where
https://github.com/llvm/llvm-project/pull/130182 is not on the list of possible
culpirits? Because the link @fmayer provided for sure included it.
https://github.com/llvm/llvm-project/pull/132748
https://github.com/GeorgeKA created
https://github.com/llvm/llvm-project/pull/133806
Alias template class template argument deduction is a documented C++20 feature.
C++17 also happens to support it, but there is no message output to indicate
the officially supported version. This PR adds that
amykhuang wrote:
Hi we're seeing some msan failures after this patch in tests such as
clang-tools-extra/test/clang-tidy/checkers/modernize/use-using.cpp
Here's the top of the stack trace
```
==6262==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x560847d4ff8a in
clang::DependentT
https://github.com/HazardyKnusperkeks approved this pull request.
https://github.com/llvm/llvm-project/pull/134473
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jianghc724 wrote:
should be cvts_biasph_hf8 :)
https://github.com/llvm/llvm-project/pull/131592
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
spall wrote:
> this is not NFC, so we should verify that we can call these intrinsics with
> `half` values even if 16-bit types aren't enabled, and that they properly
> codegen to 32-bit varia
> > > > > For example, for `abs`, it still depends on the
> > > > > _HLSL_16BIT_AVAILABILITY availab
https://github.com/efriedma-quic closed
https://github.com/llvm/llvm-project/pull/126382
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shiltian closed
https://github.com/llvm/llvm-project/pull/122629
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
thurstond wrote:
> @fmayer this patch touches nowhere near where those backtraces indicate.
> #130182 is a far more likely culprit.
#130182 cannot be the cause of the ongoing MSan buildbot failures, because it
was already reverted two days ago in #134239
https://github.com/llvm/llvm-project/
https://github.com/Ankur-0429 updated
https://github.com/llvm/llvm-project/pull/133878
>From 289f8630dccf916b8cf7cc43758bae60df036c5d Mon Sep 17 00:00:00 2001
From: Ankur Ahir
Date: Wed, 2 Apr 2025 00:53:33 -0700
Subject: [PATCH] clang frontend crash with friend class declaration and
overloade
https://github.com/VitaNuo edited
https://github.com/llvm/llvm-project/pull/133910
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/wangpc-pp approved this pull request.
https://github.com/llvm/llvm-project/pull/132529
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,8530 @@
+//===-- AArch64.cpp - Emit LLVM Code for builtins
-===//
+//
+// 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: A
https://github.com/ficol created
https://github.com/llvm/llvm-project/pull/134102
Add missing CGFPOptionsRAII for fptoi and itofp cases
>From 5f0a65433744a9b1abd3aa82417d716a0aa5b33b Mon Sep 17 00:00:00 2001
From: "Ficek, Jakub"
Date: Wed, 2 Apr 2025 17:41:30 +0200
Subject: [PATCH] [clang] fp
https://github.com/naveen-seth updated
https://github.com/llvm/llvm-project/pull/133462
>From a23ba4d51332180ff5d1b5bc9de2d0c6c04cbf66 Mon Sep 17 00:00:00 2001
From: naveen-seth
Date: Fri, 28 Mar 2025 06:59:06 +0100
Subject: [PATCH] [clang][modules] Guard against bad -fmodule-file mappings
(#1
https://github.com/kadircet commented:
> Are you able to test this PR and confirm it fixes the regressions you
> encountered?
hi @carlosgalvezp , yes this fixes the particular issues we had, thanks!
https://github.com/llvm/llvm-project/pull/132725
__
@@ -16223,6 +16324,70 @@ bool Sema::CompleteConstructorCall(CXXConstructorDecl
*Constructor,
return Invalid;
}
+bool Sema::isTypeAwareOperatorNewOrDelete(const NamedDecl *ND) const {
+ const FunctionDecl *FnDecl = nullptr;
ojhunt wrote:
Removed and replac
https://github.com/offsetof created
https://github.com/llvm/llvm-project/pull/132779
CWG2803 "Overload resolution for reference binding of similar types"
CWG2958 "Overload resolution involving lvalue transformation and qualification
conversion"
>From 6c5441fd1e22e93de3a6c681842fe19f6e96fa62 Mo
https://github.com/kazutakahirata closed
https://github.com/llvm/llvm-project/pull/133201
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -749,13 +752,8 @@ genHTML(const EnumInfo &I, const ClangDocContext &CDCtx) {
Out.emplace_back(std::move(Table));
- if (I.DefLoc) {
-if (!CDCtx.RepositoryUrl)
- Out.emplace_back(writeFileDefinition(*I.DefLoc));
-else
- Out.emplace_back(
- write
zeule wrote:
> IMO, a boolean option, e.g. `AllowBreakBeforeQPropertyKeyword` should
> suffice.
I don't like to hardcode neither the macro name nor the keywords, which depend
on Qt version. Implementation would not differ save for the source we fetch
keywords from.
https://github.com/llvm/
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes ,
=?utf-8?q?Théo?= De Magalhaes
Message-ID:
In-Reply-To:
mizvekov wrote:
mizvekov wrote:
@fmayer this patch touches nowhere near where those backtraces indicate.
https://github.com/llvm/llvm-project/pull/130182 is a far more likely culprit.
https://github.com/llvm/llvm-project/pull/132748
___
cfe-commits mailing list
cfe-co
@@ -1655,6 +1667,10 @@ bool RISCVAsmParser::matchAndEmitInstruction(SMLoc
IDLoc, unsigned &Opcode,
return generateImmOutOfRangeError(Operands, ErrorInfo, 1, (1 << 5));
case Match_InvalidUImm5GE6Plus1:
return generateImmOutOfRangeError(Operands, ErrorInfo, 6, (1 << 5)
@@ -3239,61 +3162,11 @@ bool Sema::SubstTypeConstraint(
TC->getTemplateArgsAsWritten();
if (!EvaluateConstraints) {
-bool ShouldExpandExplicitTemplateArgs =
-TemplArgInfo && ArgumentPackSubstitutionIndex != -1 &&
-llvm::any_of(TemplArgInfo->argument
https://github.com/naveen-seth created
https://github.com/llvm/llvm-project/pull/133462
When using -fmodule-file== with incorrect inputs, the
compiler crashes in two scenarios:
1. A module is mapped to the right BMI file but one of its transitively
exported module dependencies is also mapped
https://github.com/maryammo commented:
Can we have a test where it shows with this PR, the backend computeFSAdditions
can override the CRBits passed by frontend?
https://github.com/llvm/llvm-project/pull/133617
___
cfe-commits mailing list
cfe-commits
https://github.com/kadircet approved this pull request.
https://github.com/llvm/llvm-project/pull/131591
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -127,6 +136,8 @@ struct MissingFeatures {
static bool ternaryOp() { return false; }
static bool tryOp() { return false; }
static bool zextOp() { return false; }
+ static bool opPtrStride() { return false; }
+ static bool opPtrDiff() { return false; }
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (metkarpoonam)
Changes
Implement dst algorithm in the hlsl_intrinsics.h and added test cases for HLSL
codegen and sema
fixes: https://github.com/llvm/llvm-project/issues/99108
---
Full diff: https://github.com/llvm/llvm-project/pull/
@@ -223,6 +223,13 @@ endif()
# This can be used to detect whether we're in the runtimes build.
set(LLVM_RUNTIMES_BUILD ON)
+if (LLVM_ENABLE_PER_TARGET_RUNTIME_DIR AND UNIX AND ${CMAKE_SYSTEM_NAME}
MATCHES "AIX")
+ # Set LLVM_ENABLE_PER_TARGET_RUNTIME_DIR=OFF as AIX doesn't s
Author: Younan Zhang
Date: 2025-03-24T16:46:48+08:00
New Revision: 38d71c9bdcf6b10c6fe02d5bd74fc8e6efb50a4d
URL:
https://github.com/llvm/llvm-project/commit/38d71c9bdcf6b10c6fe02d5bd74fc8e6efb50a4d
DIFF:
https://github.com/llvm/llvm-project/commit/38d71c9bdcf6b10c6fe02d5bd74fc8e6efb50a4d.diff
pratlucas wrote:
I see this change re-landed yesterday but we continue to see failures related
to the extra `-unknown` component in our downstream testing of
[arm/arm-toolchain](https://github.com/arm/arm-toolchain), which are similar to
what was described in the comment above:
```
arm-softwar
@@ -0,0 +1,127 @@
+// RUN: %clang_analyze_cc1 -std=c++20
-analyzer-checker=core,debug.ExprInspection -analyzer-config
inline-lambdas=true -verify %s
+
+#include "Inputs/system-header-simulator-cxx.h"
+void clang_analyzer_warnIfReached();
+void clang_analyzer_eval(int);
+
+void c
https://github.com/mariusdr edited
https://github.com/llvm/llvm-project/pull/133574
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
clayborg wrote:
FYI: There is already VTable support in our lldb::SBValue class and it is part
of the public API in LLDB and doesn't require any of this:
```
/// If this value represents a C++ class that has a vtable, return an value
/// that represents the virtual function table.
///
//
https://github.com/hulxv updated
https://github.com/llvm/llvm-project/pull/131280
>From bf9bd4156cb7f652c9cf0477f537e5c58b470448 Mon Sep 17 00:00:00 2001
From: hulxv
Date: Fri, 14 Mar 2025 07:39:15 +0200
Subject: [PATCH 1/7] [clang-doc] [feat] add `--repository-line-prefix`
argument (fix #5981
https://github.com/jadhbeika updated
https://github.com/llvm/llvm-project/pull/128742
>From fa3dd1423e4bf2209feb9713f1833e653ec43a74 Mon Sep 17 00:00:00 2001
From: Jad Hbeika
Date: Wed, 19 Feb 2025 12:53:11 -0800
Subject: [PATCH 1/4] [Clang] [OpenMP] Support NOWAIT with optional argument
---
Author: Brad Smith
Date: 2025-03-21T02:13:33-04:00
New Revision: 910f7f45f27d1f3cfad779669d0e0f15ff5b9686
URL:
https://github.com/llvm/llvm-project/commit/910f7f45f27d1f3cfad779669d0e0f15ff5b9686
DIFF:
https://github.com/llvm/llvm-project/commit/910f7f45f27d1f3cfad779669d0e0f15ff5b9686.diff
LO
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?=
Message-ID:
In-Reply-To:
https://github.com/jeremyd2019 edited
https://github.com/llvm/llvm-project/pull/134494
___
cfe-commits mailing list
cfe-commits@lists.llvm.o
https://github.com/spall updated
https://github.com/llvm/llvm-project/pull/131666
>From 4d4541232fb8ada1a4a17701919809a2a727d52d Mon Sep 17 00:00:00 2001
From: Sarah Spall
Date: Mon, 17 Mar 2025 12:01:11 -0700
Subject: [PATCH 1/2] remove Macros implementing overloads for min and max.
Implement
Author: Yaxun (Sam) Liu
Date: 2025-04-02T18:28:56-04:00
New Revision: dedb632b833f14ef28c6f8a7f5e8983c1be60fa9
URL:
https://github.com/llvm/llvm-project/commit/dedb632b833f14ef28c6f8a7f5e8983c1be60fa9
DIFF:
https://github.com/llvm/llvm-project/commit/dedb632b833f14ef28c6f8a7f5e8983c1be60fa9.dif
https://github.com/simpal01 updated
https://github.com/llvm/llvm-project/pull/134099
>From 7f6302053575732f633c69bbf55f2624da1e8bf4 Mon Sep 17 00:00:00 2001
From: Simi Pallipurath
Date: Wed, 2 Apr 2025 12:35:16 +0100
Subject: [PATCH 1/4] Refine multilib selection to handle alignment based on
a
@@ -436,9 +436,9 @@ class StdLibraryFunctionsChecker
llvm::raw_ostream &Out) const override;
ValueConstraintPtr negate() const override {
- NotNullBufferConstraint Tmp(*this);
+ BufferNullnessConstraint Tmp(*this);
Tmp.Cannot
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?= ,
Mateusz =?utf-8?q?Mikuła?=
Message-ID:
In-Reply-To:
@@ -847,7 +847,11 @@ void llvm::sys::PrintStackTrace(raw_ostream &OS, int
Depth) {
const char *name = strrchr(dlinfo.dli_fname, '/');
if (!name)
+#ifdef __
@@ -32,6 +32,26 @@ enum E2 : S::I { e };
#endif
} // namespace cwg2516
+namespace cwg2517 { // cwg2517: 21
+#if __cplusplus >= 202302L
imdj wrote:
Shouldn't it follow the status mentioned here
https://cplusplus.github.io/CWG/issues/2517.html? or it there a m
@@ -0,0 +1,32 @@
+// RUN: rm -rf %t && mkdir -p %t
+// RUN: clang-doc --format=md --doxygen --output=%t --executor=standalone %s
+// RUN: clang-doc --format=html --doxygen --output=%t --executor=standalone %s
+// RUN: FileCheck %s < %t/GlobalNamespace/MyClass.md
--check-prefix=MD
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 5 "ninja check
1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/27/builds/8021
Here is the relevant piece o
https://github.com/Sirraide commented:
I think splitting this up by target is a good idea.
https://github.com/llvm/llvm-project/pull/132252
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-comm
Author: Mohamed Emad
Date: 2025-03-28T16:45:09-07:00
New Revision: 515d1ae679ea25687423be37abec74565d755921
URL:
https://github.com/llvm/llvm-project/commit/515d1ae679ea25687423be37abec74565d755921
DIFF:
https://github.com/llvm/llvm-project/commit/515d1ae679ea25687423be37abec74565d755921.diff
https://github.com/Un1q32 updated
https://github.com/llvm/llvm-project/pull/124651
>From d4e97c4113086c3d2dfa3bf6e9ecfee377f8c4b6 Mon Sep 17 00:00:00 2001
From: Un1q32
Date: Mon, 27 Jan 2025 18:00:34 -0500
Subject: [PATCH 1/3] [Clang] Link libgcc_s.1.dylib when building for macOS
10.5 and olde
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Alexandros Lamprineas (labrinea)
Changes
Removes attr-target-version.c which doesn't have a clear purpose.
Introduces AArch64/fmv-detection.c to check detection bitmasks.
Adds coverage in AArch64/fmv-resolver-emission.c
---
Patch is 87.47
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `sanitizer-aarch64-linux`
running on `sanitizer-buildbot7` while building `clang` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/51/builds/13779
Here is the relevant piece of the
jrtc27 wrote:
Is there a reason why these aren't lowercase like the rest?
https://github.com/llvm/llvm-project/pull/132481
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/yonghong-song closed
https://github.com/llvm/llvm-project/pull/133666
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Yingwei Zheng
Date: 2025-04-03T18:03:42+08:00
New Revision: 61907ebd764afe75aa7134627f41827e6893d6d0
URL:
https://github.com/llvm/llvm-project/commit/61907ebd764afe75aa7134627f41827e6893d6d0
DIFF:
https://github.com/llvm/llvm-project/commit/61907ebd764afe75aa7134627f41827e6893d6d0.diff
@@ -994,6 +992,127 @@ mlir::LogicalResult
CIRToLLVMUnaryOpLowering::matchAndRewrite(
<< elementType;
}
+mlir::LLVM::IntegerOverflowFlags
+CIRToLLVMBinOpLowering::getIntOverflowFlag(cir::BinOp op) const {
+ if (op.getNoUnsignedWrap())
+return mlir:
https://github.com/bcardosolopes approved this pull request.
https://github.com/llvm/llvm-project/pull/132266
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jroelofs approved this pull request.
https://github.com/llvm/llvm-project/pull/132727
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -2234,6 +2234,101 @@ enum class CXXNewInitializationStyle {
Braces
};
+enum class TypeAwareAllocationMode : unsigned { No, Yes };
+inline bool isTypeAwareAllocation(TypeAwareAllocationMode Mode) {
+ return Mode == TypeAwareAllocationMode::Yes;
+}
+inline TypeAwareAllocat
topperc wrote:
> > SiFive's AME proposal locates in OP-V/OP-VE category
>
> Yes, this is a good point. I do think we should also remove other vendor
> instruction sets which abused the standard op fields.
The RISC-V specification does not take a hard stance on non-conforming
extensions. It sh
1 - 100 of 734 matches
Mail list logo
