@@ -14175,27 +14222,350 @@ bool SemaOpenMP::checkTransformableLoopNest(
return false;
},
[&OriginalInits](OMPLoopBasedDirective *Transform) {
-Stmt *DependentPreInits;
-if (auto *Dir = dyn_cast(Transform))
- DependentPreInits = Dir->
@@ -1480,6 +1493,108 @@ class SemaOpenMP : public SemaBase {
SmallVectorImpl &LoopHelpers,
Stmt *&Body, SmallVectorImpl> &OriginalInits);
+ /// @brief Categories of loops encountered during semantic OpenMP loop
+ /// analysis
+ ///
+ /// This enumeration identi
https://github.com/mstorsjo approved this pull request.
LGTM
IIRC @petrhosek had commented on this before, and was generally in favour of
it, but I'd still leave it open for a couple days if he wants to comment
further on it.
https://github.com/llvm/llvm-project/pull/138587
__
@@ -1151,6 +1151,106 @@ class OMPFullClause final : public
OMPNoChildClause {
static OMPFullClause *CreateEmpty(const ASTContext &C);
};
+/// This class represents the 'looprange' clause in the
+/// '#pragma omp fuse' directive
+///
+/// \code {c}
+/// #pragma omp fuse loop
https://github.com/AaronBallman closed
https://github.com/llvm/llvm-project/pull/140724
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Aaron Ballman
Date: 2025-05-21T06:36:21-04:00
New Revision: 7fe387ac35b0b37d2862beaf9c17062b62a221ed
URL:
https://github.com/llvm/llvm-project/commit/7fe387ac35b0b37d2862beaf9c17062b62a221ed
DIFF:
https://github.com/llvm/llvm-project/commit/7fe387ac35b0b37d2862beaf9c17062b62a221ed.diff
eZWALT wrote:
Gentle-ping, I'm not sure if GitHub has notified you of the comments :)
@alexey-bataev
https://github.com/llvm/llvm-project/pull/139293
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
@@ -11516,6 +11516,21 @@ def note_omp_implicit_dsa : Note<
"implicitly determined as %0">;
def err_omp_loop_var_dsa : Error<
"loop iteration variable in the associated loop of 'omp %1' directive may
not be %0, predetermined as %2">;
+def warn_omp_different_loop_ind_var_typ
https://github.com/frasercrmck updated
https://github.com/llvm/llvm-project/pull/137183
>From fcae18dd0b4af6f7517ba8eda368374fa693a5f9 Mon Sep 17 00:00:00 2001
From: Fraser Cormack
Date: Thu, 24 Apr 2025 11:24:30 +0100
Subject: [PATCH 1/5] [libclc] Support the generic address space
This commit
balazske wrote:
I have renamed the check, if OK the class name will be changed too (in a new
commit).
https://github.com/llvm/llvm-project/pull/140086
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
@@ -7639,6 +7639,8 @@ def warn_param_mismatched_alignment : Warning<
def err_objc_object_assignment : Error<
"cannot assign to class object (%0 invalid)">;
+def err_typecheck_array_prvalue_operand : Error<
+ "array prvalue is not permitted">;
AaronBallman w
@@ -7639,6 +7639,8 @@ def warn_param_mismatched_alignment : Warning<
def err_objc_object_assignment : Error<
"cannot assign to class object (%0 invalid)">;
+def err_typecheck_array_prvalue_operand : Error<
+ "array prvalue is not permitted">;
Sirraide wrote
AaronBallman wrote:
> > This is related to CWG2548
>
> Kinda, but not really. It has never been necessary to create that
> (non-)issue. Or does someone really believe that it is a C++ defect that `IA{
> 1, 2, 3 } - IA{ 1, 2, 3 }` is not allowed? So, it is just a bug since C++11
I think it is
https://github.com/AaronBallman approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/140233
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tblah approved this pull request.
LGTM, thanks
https://github.com/llvm/llvm-project/pull/140182
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -7639,6 +7639,8 @@ def warn_param_mismatched_alignment : Warning<
def err_objc_object_assignment : Error<
"cannot assign to class object (%0 invalid)">;
+def err_typecheck_array_prvalue_operand : Error<
+ "array prvalue is not permitted">;
languagelawyer
https://github.com/perry-ca edited
https://github.com/llvm/llvm-project/pull/140944
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -71,9 +76,9 @@ unsigned SpecialCaseList::Matcher::match(StringRef Query)
const {
for (const auto &[Pattern, Pair] : Globs)
if (Pair.first.match(Query))
return Pair.second;
- for (const auto &[Regex, LineNumber] : RegExes)
-if (Regex->match(Query))
- re
@@ -6,89 +6,121 @@ void test() {
int i = 0;
int j = 0;
int k = 0;
- int c = 10;
- int a[c];
+ constexpr int c = 10;
+ int a[c]; // Make 'c' constexpr to avoid variable-length array warnings.
- [i,j] { return i; };
+ [i] { return i; };
// CHECK: [i] { return i;
@@ -1633,8 +1633,8 @@ static void repeatForLambdaConversionFunctionCallingConvs(
CC_C,CC_X86StdCall, CC_X86FastCall, CC_X86VectorCall,
DefaultFree, DefaultMember, CallOpCC};
llvm::sort(Convs);
-llvm::iterator_range Range(
-std::begin(Conv
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`polly-x86_64-linux-shlib-plugin` running on `polly-x86_64-gce2` while building
`clang,llvm` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/75/builds/6884
Here is the relevant piec
vsapsai wrote:
Interesting, changing `private header "wrap_foo.h"` to `header "wrap_foo.h"` in
`b.wrap_foo` stops reproducing the error. I'm not sure it guarantees
> whenever resolving module for the header, pick one that has the header as
> modular over textual.
But seems we are closer to th
https://github.com/inbelic updated
https://github.com/llvm/llvm-project/pull/140147
>From fc2fc60145e65a1b32542cbaf9b4bd6ce3b1509d Mon Sep 17 00:00:00 2001
From: Finn Plummer
Date: Thu, 15 May 2025 17:48:07 +
Subject: [PATCH 1/2] [HLSL][RootSignature] Add parsing for empty RootParams
- def
https://github.com/qinkunbao edited
https://github.com/llvm/llvm-project/pull/140529
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/inbelic edited
https://github.com/llvm/llvm-project/pull/140147
___
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
`llvm-clang-key-instructions` running on `sie-linux-worker5` while building
`clang,llvm` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/208/builds/1347
Here is the rel
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-expensive-checks-ubuntu` running on `as-builder-4` while
building `clang,llvm` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/187/builds/6057
Here i
https://github.com/bd1976bris updated
https://github.com/llvm/llvm-project/pull/140956
>From 0d9218eda0b99b0d439afb8a84a056581362638e Mon Sep 17 00:00:00 2001
From: Dunbobbin
Date: Mon, 19 May 2025 10:17:00 +0100
Subject: [PATCH 1/3] [Windows][LLVM] Elide `PrettyStackTrace` output for usage
er
jansvoboda11 wrote:
FWIW I tried running this patch through my `clang-scan-deps` benchmark on an
internal Apple project and saw 16% increase in instruction count.
https://github.com/llvm/llvm-project/pull/140867
___
cfe-commits mailing list
cfe-commit
@@ -61,11 +61,14 @@ struct ScopedFatalErrorHandler {
/// @deprecated Use reportFatalInternalError() or reportFatalUsageError()
/// instead.
[[noreturn]] LLVM_ABI void report_fatal_error(const char *reason,
- bool gen_crash_diag = tru
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lld-x86_64-ubuntu-fast`
running on `as-builder-4` while building `clang,llvm` at step 5
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/33/builds/16878
Here is the relevant piec
@@ -186,7 +288,7 @@ void CIRSimplifyPass::runOnOperation() {
// Collect operations to apply patterns.
llvm::SmallVector ops;
getOperation()->walk([&](Operation *op) {
-if (isa(op))
+if (isa(op))
Andres-Salamanca wrote:
Just checked and it also fa
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`llvm-clang-x86_64-gcc-ubuntu-no-asserts` running on `doug-worker-6` while
building `clang,llvm` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/202/builds/1367
Here is
https://github.com/joaosaffran approved this pull request.
https://github.com/llvm/llvm-project/pull/140147
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
perry-ca wrote:
> I am not seeing any syntax tests for `_Export` in disallowed positions. For
> example:
>
> ```c++
> int _Export *x = 0;
> ```
>
> It's not the end of the world if it happens to be accepted, but it is
> potentially worth noting.
I'll add a few tests.
https://github.com/llvm
llvmbot wrote:
@llvm/pr-subscribers-clangir
Author: Erich Keane (erichkeane)
Changes
The array indexes(and sections) are represented by the acc.bounds operation,
which this ensures we fill in properly. The lowerbound is required, so we
always get that.
The upperbound or extent is requi
https://github.com/erichkeane created
https://github.com/llvm/llvm-project/pull/140971
The array indexes(and sections) are represented by the acc.bounds operation,
which this ensures we fill in properly. The lowerbound is required, so we
always get that.
The upperbound or extent is required.
@@ -3595,9 +3595,9 @@ def ObjCRequiresPropertyDefs : InheritableAttr {
def PointerAuth : TypeAttr {
let Spellings = [CustomKeyword<"__ptrauth">];
- let Args = [IntArgument<"Key">,
- BoolArgument<"AddressDiscriminated", 1>,
- IntArgument<"ExtraDiscr
https://github.com/ojhunt updated
https://github.com/llvm/llvm-project/pull/136828
>From 927380bdf377581e6e40507a12c374023352c613 Mon Sep 17 00:00:00 2001
From: Oliver Hunt
Date: Wed, 30 Apr 2025 22:26:59 -0700
Subject: [PATCH 1/5] [clang][PAC] add support for options parameter to
__ptrauth
T
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-s390x-linux-lnt`
running on `systemz-1` while building `clang,llvm` at step 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/136/builds/3988
Here is the relevant piece of the b
alexfh wrote:
> Interesting, changing `private header "wrap_foo.h"` to `header "wrap_foo.h"`
> in `b.wrap_foo` stops reproducing the error. I'm not sure it guarantees
>
> > whenever resolving module for the header, pick one that has the header as
> > modular over textual.
>
> But seems we are
https://github.com/gedare updated
https://github.com/llvm/llvm-project/pull/108332
>From 5972376f719665225b04bf121cda6c769e3392d9 Mon Sep 17 00:00:00 2001
From: Gedare Bloom
Date: Thu, 20 Jun 2024 17:35:39 -0600
Subject: [PATCH 1/6] Format: add AlignAfterControlStatement
Introduce new style op
https://github.com/ojhunt updated
https://github.com/llvm/llvm-project/pull/136828
>From 927380bdf377581e6e40507a12c374023352c613 Mon Sep 17 00:00:00 2001
From: Oliver Hunt
Date: Wed, 30 Apr 2025 22:26:59 -0700
Subject: [PATCH 1/4] [clang][PAC] add support for options parameter to
__ptrauth
T
https://github.com/zmodem updated
https://github.com/llvm/llvm-project/pull/138562
>From e221ba3b0f7b08bcfc56bf75f7505265c332637d Mon Sep 17 00:00:00 2001
From: Hans Wennborg
Date: Mon, 5 May 2025 20:24:15 +0200
Subject: [PATCH 1/7] [Sema] Warn about omitting deprecated enumerator in
switch
T
gedare wrote:
Take 3. This is now a simpler solution that separates rules for breaking within
`if`, loop, and `switch` control statements. These explicit style options
override the `AlwaysBreak` and `BlockIndent` options, which should be now only
effective for function-like parentheses and bra
@@ -327,6 +330,27 @@ a discriminator determined as follows:
is ``ptrauth_blend_discriminator(&x, discriminator)``; see
`ptrauth_blend_discriminator`_.
+``ptrauth_qualifier_options``
+~
+
+The options parameter to the ``__ptrauth`` qualifier is a
@@ -9694,6 +9694,304 @@ TEST_F(FormatTest, ParenthesesAndOperandAlignment) {
Style);
}
+TEST_F(FormatTest, AlignAfterConditionalStatements) {
gedare wrote:
Yes, it might be a good idea to consolidate all of the alignment tests in a new
file. I
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `arc-builder` running on
`arc-worker` while building `clang,llvm` at step 6
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/3/builds/16309
Here is the relevant pie
https://github.com/tclin914 updated
https://github.com/llvm/llvm-project/pull/140681
>From 80f55eaaead598b0b557aa32756f59b201fc0fcd Mon Sep 17 00:00:00 2001
From: Jim Lin
Date: Tue, 20 May 2025 10:13:26 +0800
Subject: [PATCH 1/4] [RISCV] Add Andes A25/AX25 processor definition
Andes A25/AX25 a
Author: Jim Lin
Date: 2025-05-22T09:22:32+08:00
New Revision: 569b6f6dade6a1a1b758d982bcd9d91abafb787f
URL:
https://github.com/llvm/llvm-project/commit/569b6f6dade6a1a1b758d982bcd9d91abafb787f
DIFF:
https://github.com/llvm/llvm-project/commit/569b6f6dade6a1a1b758d982bcd9d91abafb787f.diff
LOG:
https://github.com/tclin914 closed
https://github.com/llvm/llvm-project/pull/140681
___
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
`openmp-offload-sles-build-only` running on `rocm-worker-hw-04-sles` while
building `clang,llvm` at step 10 "Add check check-lld".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/140/builds/23578
Here
https://github.com/tclin914 edited
https://github.com/llvm/llvm-project/pull/140979
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/lenary approved this pull request.
https://github.com/llvm/llvm-project/pull/140979
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -65,6 +65,17 @@ enum class PointerAuthenticationMode : unsigned {
SignAndAuth
};
+static constexpr llvm::StringLiteral PointerAuthenticationOptionStrip =
"strip";
ojhunt wrote:
Oh, I hadn't included the updated to stringifying the qualifier so these wer
@@ -6831,43 +6832,60 @@ std::optional
ASTReader::isPreprocessedEntityInFileID(unsigned Index,
return false;
}
-namespace {
-
- /// Visitor used to search for information about a header file.
- class HeaderFileInfoVisitor {
- FileEntryRef FE;
-std::optional HFI;
-
-
yingcong-wu wrote:
Hi @sarnex , this change is crucial for the device sanitizers since it
addresses a long-standing OMP related issue of us. Please help keep this
change. Thanks.
https://github.com/llvm/llvm-project/pull/137187
___
cfe-commits mailin
https://github.com/ChuanqiXu9 edited
https://github.com/llvm/llvm-project/pull/140867
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ChuanqiXu9 commented:
> It turns out to be kind of a pain to use with HeaderFileInfoTrait. More
> importantly, we can't really afford to key by the internal key type since
> that only hashes on the size of the file and the hash collision gets pretty
> bad. Moreover, the mer
@@ -654,6 +654,10 @@ class ASTReader
/// Map from the TU to its lexical contents from each module file.
std::vector> TULexicalDecls;
+ unsigned HeaderFileInfoIdx = 0;
ChuanqiXu9 wrote:
And also, this seems unsafe since ModuleManager can remove modules te
@@ -654,6 +654,10 @@ class ASTReader
/// Map from the TU to its lexical contents from each module file.
std::vector> TULexicalDecls;
+ unsigned HeaderFileInfoIdx = 0;
ChuanqiXu9 wrote:
nit: Unloaded header file info idx.
And also I feel the name is odd.
https://github.com/kazutakahirata created
https://github.com/llvm/llvm-project/pull/140983
None
>From 5e16f3ea4637e1aab04a3f87f601a3e9c06c4449 Mon Sep 17 00:00:00 2001
From: Kazu Hirata
Date: Wed, 21 May 2025 14:12:52 -0700
Subject: [PATCH] [clang] Use llvm::find_if (NFC)
---
clang/lib/Analy
ilovepi wrote:
I've updated https://github.com/llvm/llvm-project/issues/140773 with a
reproducer.
https://github.com/llvm/llvm-project/pull/140930
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/
llvmbot wrote:
@llvm/pr-subscribers-clang-format
Author: Kazu Hirata (kazutakahirata)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/140983.diff
5 Files Affected:
- (modified) clang/lib/Analysis/ThreadSafety.cpp (+9-13)
- (modified) clang/lib/Format/MacroCallReconst
mpark wrote:
> > It turns out to be kind of a pain to use with HeaderFileInfoTrait. More
> > importantly, we can't really afford to key by the internal key type since
> > that only hashes on the size of the file and the hash collision gets pretty
> > bad. Moreover, the merging and condensing s
https://github.com/shiltian approved this pull request.
https://github.com/llvm/llvm-project/pull/140983
___
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: Kazu Hirata (kazutakahirata)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/140985.diff
4 Files Affected:
- (modified) clang/include/clang/Sema/Sema.h (+2-2)
- (modified) clang/lib/Interpreter/Interpreter.cpp (+7-8)
llvmbot wrote:
@llvm/pr-subscribers-clang-analysis
Author: Kazu Hirata (kazutakahirata)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/140983.diff
5 Files Affected:
- (modified) clang/lib/Analysis/ThreadSafety.cpp (+9-13)
- (modified) clang/lib/Format/MacroCallRecon
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Kazu Hirata (kazutakahirata)
Changes
---
Full diff: https://github.com/llvm/llvm-project/pull/140983.diff
5 Files Affected:
- (modified) clang/lib/Analysis/ThreadSafety.cpp (+9-13)
- (modified) clang/lib/Format/MacroCallReconstructor.
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-aarch64-linux-bootstrap-hwasan` running on `sanitizer-buildbot11`
while building `clang,llvm` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/55/builds/11683
Here is t
https://github.com/kazutakahirata created
https://github.com/llvm/llvm-project/pull/140985
None
>From 9d1d55f8c5283b71cac4893cd5c39a38d4c55353 Mon Sep 17 00:00:00 2001
From: Kazu Hirata
Date: Wed, 21 May 2025 14:09:49 -0700
Subject: [PATCH] [clang] Use llvm::is_contained (NFC)
---
clang/incl
https://github.com/mshockwave approved this pull request.
https://github.com/llvm/llvm-project/pull/140979
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/petrhosek approved this pull request.
https://github.com/llvm/llvm-project/pull/138587
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
zmodem wrote:
Thanks Aaron, that's a good example.
This is a pickle; it doesn't seem like there's an obviously Right Solution(tm)
here.
I think we're agreeing on the first part, that unhandled deprecated enums
should trigger the "not covered" warning.
Some users will prefer to handle that wi
hubert-reinterpretcast wrote:
> For reference, the XL documentation for _Export:
> https://www.ibm.com/docs/en/zos/3.1.0?topic=specifiers-export-function-specifier-c-only
@perry-ca, additional context from
https://www.ibm.com/docs/en/zos/3.1.0?topic=qualifiers-export-qualifier-c-only
would he
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `publish-sphinx-docs`
running on `as-worker-4` while building `clang,llvm` at step 5
"build-docs-llvm-html-docs-clang-html-docs-clang...".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/45/builds/12459
https://github.com/farzonl approved this pull request.
https://github.com/llvm/llvm-project/pull/138429
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Sarah Spall
Date: 2025-05-21T13:03:07-07:00
New Revision: 5ba57a81f213f17547be11e199888d8d156ececc
URL:
https://github.com/llvm/llvm-project/commit/5ba57a81f213f17547be11e199888d8d156ececc
DIFF:
https://github.com/llvm/llvm-project/commit/5ba57a81f213f17547be11e199888d8d156ececc.diff
L
https://github.com/spall closed https://github.com/llvm/llvm-project/pull/138429
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -61,11 +61,14 @@ struct ScopedFatalErrorHandler {
/// @deprecated Use reportFatalInternalError() or reportFatalUsageError()
/// instead.
[[noreturn]] LLVM_ABI void report_fatal_error(const char *reason,
- bool gen_crash_diag = tru
arsenm wrote:
I don't think you can reasonably test this with a lit test, you have to add
this as a proper build target in llvm/examples similar to Bye
https://github.com/llvm/llvm-project/pull/139059
___
cfe-commits mailing list
cfe-commits@lists.ll
arsenm wrote:
> I don't think you can reasonably test this with a lit test, you have to add
> this as a proper build target in llvm/examples similar to Bye.
A lit test could then drive the load of that plugin, but the lit test can't
contain the pass itself
https://github.com/llvm/llvm-projec
Xazax-hun wrote:
> What is the relationship of this new callback with the BranchCondition
> callback
+1, I am also interested to learn what is the main motivation behind the new
callback. Do you have some example use cases in mind? I think users might get
confused which one to use.
https://
@@ -28,25 +30,39 @@ int bar(C *c) {
int bar2(C *c) {
// CHECK-NEW-LABEL: _Z4bar2P1C
-// CHECK-NEW: load i32, {{.*}}, !tbaa [[TAG_int:!.*]]
+// CHECK-NEW: load i32, {{.*}}, !tbaa [[TAG_C_x:!.*]]
return c->x[2];
}
int bar3(C *c, int j) {
// CHECK-NEW-LABEL: _Z4bar3P1Ci
-
@@ -28,25 +30,39 @@ int bar(C *c) {
int bar2(C *c) {
// CHECK-NEW-LABEL: _Z4bar2P1C
-// CHECK-NEW: load i32, {{.*}}, !tbaa [[TAG_int:!.*]]
+// CHECK-NEW: load i32, {{.*}}, !tbaa [[TAG_C_x:!.*]]
return c->x[2];
}
int bar3(C *c, int j) {
// CHECK-NEW-LABEL: _Z4bar3P1Ci
-
https://github.com/raoanag edited
https://github.com/llvm/llvm-project/pull/136026
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/zyn0217 approved this pull request.
I'll approve it, because I have a similar experience that swapping the deferred
instantiation and immediate instantiation order caused a very subtle failure of
return type deduction.
However, just as what @AaronBallman suggested, please ho
@@ -61,11 +61,14 @@ struct ScopedFatalErrorHandler {
/// @deprecated Use reportFatalInternalError() or reportFatalUsageError()
/// instead.
[[noreturn]] LLVM_ABI void report_fatal_error(const char *reason,
- bool gen_crash_diag = tru
https://github.com/Mr-Anyone updated
https://github.com/llvm/llvm-project/pull/140278
>From 3945cae10c7f2629e7e875db29bd9aa4fa74055c Mon Sep 17 00:00:00 2001
From: Vincent
Date: Wed, 14 May 2025 16:36:35 -0400
Subject: [PATCH 1/4] [clang] Fixed Constant Evaluation don't Call Destructor
Within
Author: Andy Kaylor
Date: 2025-05-21T13:23:01-07:00
New Revision: 08279d3924a86371e96527f68ff7496e51581f9c
URL:
https://github.com/llvm/llvm-project/commit/08279d3924a86371e96527f68ff7496e51581f9c
DIFF:
https://github.com/llvm/llvm-project/commit/08279d3924a86371e96527f68ff7496e51581f9c.diff
L
https://github.com/andykaylor closed
https://github.com/llvm/llvm-project/pull/140945
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -3595,9 +3595,9 @@ def ObjCRequiresPropertyDefs : InheritableAttr {
def PointerAuth : TypeAttr {
let Spellings = [CustomKeyword<"__ptrauth">];
- let Args = [IntArgument<"Key">,
- BoolArgument<"AddressDiscriminated", 1>,
- IntArgument<"ExtraDiscr
https://github.com/inbelic edited
https://github.com/llvm/llvm-project/pull/140147
___
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-shlib`
running on `polly-x86_64-gce2` while building `clang,llvm` at step 5 "build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/99/builds/6612
Here is the relevant piece of the
efriedma-quic wrote:
You might want to look at convertUsersOfConstantsToInstructions, which
addresses similar use-cases. (You might be able to use it directly? If not,
you can at least reference the implementation.)
Recursively rewriting expression trees should work, and result in well-defin
@@ -882,6 +882,11 @@ if (LLVM_ENABLE_WARNINGS AND
(LLVM_COMPILER_IS_GCC_COMPATIBLE OR CLANG_CL))
# The LLVM libraries have no stable C++ API, so -Wnoexcept-type is not
useful.
append("-Wno-noexcept-type" CMAKE_CXX_FLAGS)
+ # LLVM has a policy of including virtual "ancho
https://github.com/bd1976bris updated
https://github.com/llvm/llvm-project/pull/140956
>From 0d9218eda0b99b0d439afb8a84a056581362638e Mon Sep 17 00:00:00 2001
From: Dunbobbin
Date: Mon, 19 May 2025 10:17:00 +0100
Subject: [PATCH 1/2] [Windows][LLVM] Elide `PrettyStackTrace` output for usage
er
https://github.com/inbelic updated
https://github.com/llvm/llvm-project/pull/140147
>From fc2fc60145e65a1b32542cbaf9b4bd6ce3b1509d Mon Sep 17 00:00:00 2001
From: Finn Plummer
Date: Thu, 15 May 2025 17:48:07 +
Subject: [PATCH 1/2] [HLSL][RootSignature] Add parsing for empty RootParams
- def
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-ppc64le-linux-multistage` running on `ppc64le-clang-multistage-test`
while building `clang,llvm` at step 4 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/76/builds/9771
Here i
@@ -61,11 +61,14 @@ struct ScopedFatalErrorHandler {
/// @deprecated Use reportFatalInternalError() or reportFatalUsageError()
/// instead.
[[noreturn]] LLVM_ABI void report_fatal_error(const char *reason,
- bool gen_crash_diag = tru
101 - 200 of 498 matches
Mail list logo
