https://github.com/vabridgers updated
https://github.com/llvm/llvm-project/pull/108900
>From 754ae098e55cd9ea6f7ebeed37aad761598af0f2 Mon Sep 17 00:00:00 2001
From: einvbri
Date: Tue, 17 Sep 2024 01:25:20 +0200
Subject: [PATCH] [analyzer] Indicate UnarySymExpr is not supported by Z3
Random tes
cor3ntin wrote:
I think that if we don't have a fix in the next 24-48 hours, and no clarity on
the issue - a revert should be considered (note that I think it will be
disruptive for llvm too as we are, I think, 3 patches deep, but i agree that
keeping a regression on trunk for too long is unde
https://github.com/hokein approved this pull request.
https://github.com/llvm/llvm-project/pull/109099
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/79942
>From efac76027bd9294d734c3eee77ad582ad0fa9ebe Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Wed, 19 Jul 2023 20:30:29 -0700
Subject: [PATCH] [Clang][CMake] Add CSSPGO support to LLVM_BUILD_INSTRUMENTED
Build
Author: Nicolas van Kempen
Date: 2024-09-18T14:57:31-04:00
New Revision: 1be4c9710bd09e2f56908ca6cee54cb80ca1774d
URL:
https://github.com/llvm/llvm-project/commit/1be4c9710bd09e2f56908ca6cee54cb80ca1774d
DIFF:
https://github.com/llvm/llvm-project/commit/1be4c9710bd09e2f56908ca6cee54cb80ca1774d.
jplehr wrote:
I guess that makes sense.
https://github.com/llvm/llvm-project/pull/109152
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/nicovank closed
https://github.com/llvm/llvm-project/pull/107521
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
shiltian wrote:
I'm not sure about this. What does `compiler-rt` provide?
https://github.com/llvm/llvm-project/pull/109152
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jhuber6 wrote:
> I'm not sure about this. What does `compiler-rt` provide?
It's `clang_rt.builtins`. So, basically complex number multiplication /
division, wide integer stuff (I think the backend handles i128 now though). We
currently have a wrapper header that defined `__mulsc3` for the devi
https://github.com/damyanp approved this pull request.
LGTM, I'm happy to get this warning in!
https://github.com/llvm/llvm-project/pull/108894
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-
@@ -0,0 +1,2267 @@
+// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py
UTC_ARGS: --function-signature --include-generated-funcs --replace-value-regex
"__omp_offloading_[0-9a-z]+_[0-9a-z]+" "reduction_size[.].+[.]"
"pl_cond[.].+[.|,]" --prefix-filechec
alexfh wrote:
It was faster than I thought. The original code for case 2 is indeed invalid.
Having looked carefully at the two definitions of PrintTo, I clearly see they
are violating ODR. And both are originating in the internal code, so nothing
specific to Eigen. Thanks again for the good ex
@@ -2419,8 +2419,13 @@ Value *ScalarExprEmitter::VisitCastExpr(CastExpr *CE) {
return Visit(const_cast(E));
case CK_NoOp: {
-return CE->changesVolatileQualification() ? EmitLoadOfLValue(CE)
- : Visit(const_cast(E));
+i
Author: Kazu Hirata
Date: 2024-09-18T14:18:04-07:00
New Revision: abb317ff9aba8a58449d91f6162597e54d02a57c
URL:
https://github.com/llvm/llvm-project/commit/abb317ff9aba8a58449d91f6162597e54d02a57c
DIFF:
https://github.com/llvm/llvm-project/commit/abb317ff9aba8a58449d91f6162597e54d02a57c.diff
L
https://github.com/kazutakahirata closed
https://github.com/llvm/llvm-project/pull/109145
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Matheus Izvekov
Date: 2024-09-18T18:22:14-03:00
New Revision: e0ad34e56590fa2e6ffdf617e044de7eadee2139
URL:
https://github.com/llvm/llvm-project/commit/e0ad34e56590fa2e6ffdf617e044de7eadee2139
DIFF:
https://github.com/llvm/llvm-project/commit/e0ad34e56590fa2e6ffdf617e044de7eadee2139.dif
https://github.com/mizvekov closed
https://github.com/llvm/llvm-project/pull/109065
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tlively commented:
WebAssembly changes LGTM.
https://github.com/llvm/llvm-project/pull/109160
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jurahul edited
https://github.com/llvm/llvm-project/pull/109220
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tkoeppe updated
https://github.com/llvm/llvm-project/pull/109169
From d8a46761ef175194c7e7272313807d2ef25aa497 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thomas=20K=C3=B6ppe?=
Date: Wed, 18 Sep 2024 17:04:44 +
Subject: [PATCH] [clang-tidy] Make modernize-use-nullptr matcher
@@ -84,6 +84,14 @@ void test_macro_expansion4() {
#undef MY_NULL
}
+template struct pear {
+ T x;
+};
+void test_templated() {
+ pear p = { NULL };
tkoeppe wrote:
Done now. A key insight was that the test defines `NULL` as `0`, so in order
for the new che
eddyz87 wrote:
@peilin-ye ,
> However, I didn't want to use `lock` because I feel like it's too similar to
> the x86 `LOCK` prefix (implies a full memory barrier, which could be
> confusing here). WDYT? Cc: @yonghong-song @4ast
Well, we already confuse people in a way, since existing `lock *
eddyz87 wrote:
> > Also a question regarding 3 commits in one pull request. As far as I
> > understand [current](https://llvm.org/docs/GitHub.html) policy, the idea is
> > to have a separate pull request for each commit (and fork branches from one
> > another to build a stack). Otherwise the c
zyn0217 wrote:
For visibility, see the last attempt at removal:
https://github.com/llvm/llvm-project/pull/80081
AFAIK, some Clangd features e.g. code folding, are still relying on it, so
ditching it completely is probably not an option at the moment.
https://github.com/llvm/llvm-project/pull/
llvmbot wrote:
@llvm/pr-subscribers-mc
Author: Jun Wang (jwanggit86)
Changes
Three instructions, namely, buffer_store_lds_dword, buffer_wbinvl1, and
buffer_wbinvl1_vol are obsolete in GFX940 and should not be supported.
---
Patch is 211.53 KiB, truncated to 20.00 KiB below, full version:
https://github.com/jwanggit86 closed
https://github.com/llvm/llvm-project/pull/109223
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jwanggit86 wrote:
Based off wrong branch.
https://github.com/llvm/llvm-project/pull/109223
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: ofAlpaca
Date: 2024-09-19T08:33:37+08:00
New Revision: 258fc7f582877d3bc2a26e62da4f50e467d8c640
URL:
https://github.com/llvm/llvm-project/commit/258fc7f582877d3bc2a26e62da4f50e467d8c640
DIFF:
https://github.com/llvm/llvm-project/commit/258fc7f582877d3bc2a26e62da4f50e467d8c640.diff
LOG:
https://github.com/zyn0217 closed
https://github.com/llvm/llvm-project/pull/108142
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/shafik commented:
In case I don't get a chance to look at this in more detail right away can you
please reference specific CWG issues in the summary and in comments in the
code? Thank you.
https://github.com/llvm/llvm-project/pull/109208
_
@@ -678,6 +690,37 @@ struct AAAMDAttributesFunction : public AAAMDAttributes {
return !A.checkForAllCallLikeInstructions(DoesNotRetrieve, *this,
UsedAssumedInformation);
}
+
+ // Returns true if FlatScratchInit is needed, i.e
https://github.com/shiltian updated
https://github.com/llvm/llvm-project/pull/108786
>From cad9ac7478a158c455b8865cab8bb553a46f7773 Mon Sep 17 00:00:00 2001
From: Shilei Tian
Date: Tue, 17 Sep 2024 21:47:45 -0400
Subject: [PATCH] [IR] Introduce `T` to `DataLayout` to
represent flat address spa
tarunprabhu wrote:
The buildkite is failing on Windows because `flang` does not print anything on
Windows. It is not clear to me why this is the case. I do not have access to a
windows machine on which to debug this. The test, `time.f90` has been disabled
on Windows with a comment explaining w
https://github.com/bob80905 created
https://github.com/llvm/llvm-project/pull/109180
This PR adds the step intrinsic and an HLSL function that uses it.
The SPIRV backend is also implemented.
Used https://github.com/llvm/llvm-project/pull/106471 as a reference.
Fixes https://github.com/llvm/llvm
llvmbot wrote:
@llvm/pr-subscribers-clang-codegen
Author: Joshua Batista (bob80905)
Changes
This PR adds the step intrinsic and an HLSL function that uses it.
The SPIRV backend is also implemented.
Used https://github.com/llvm/llvm-project/pull/106471 as a reference.
Fixes https://github.
@@ -13,23 +13,23 @@ namespace hlsl {
namespace __detail {
-#define _HLSL_INLINE
\
- __attribute__((__always_inline__, __nodebug__)) static inline
bogner wrote:
Note that while constexpr implies `inl
llvmbot wrote:
@llvm/pr-subscribers-backend-directx
Author: Joshua Batista (bob80905)
Changes
This PR adds the step intrinsic and an HLSL function that uses it.
The SPIRV backend is also implemented.
Used https://github.com/llvm/llvm-project/pull/106471 as a reference.
Fixes https://githu
@@ -69,29 +69,25 @@ void BPFSubtarget::initSubtargetFeatures(StringRef CPU,
StringRef FS) {
CPU = "v3";
if (CPU == "probe")
CPU = sys::detail::getHostCPUNameForBPF();
- if (CPU == "generic" || CPU == "v1")
+ if (CPU.empty() || CPU == "generic" || CPU == "v1")
-
AlexVlx wrote:
> > Instead of removing the test case altogether, does it not suffice to remove
> > the SYCL reference / SYCL specific flag, which I interpret as the problem
> > being addressed? SYCL per se is not a target, but rather a language?
> > Apologies if I'm missing something.
>
> I t
@@ -84,6 +84,14 @@ void test_macro_expansion4() {
#undef MY_NULL
}
+template struct pear {
+ T x;
+};
+void test_templated() {
+ pear p = { NULL };
tkoeppe wrote:
It definitely does, but I was hoping that the absence would cause some kind of
test failure!
https://github.com/tkoeppe updated
https://github.com/llvm/llvm-project/pull/109169
From d6a67729477b178d2439dfd31539a82ab7041e10 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thomas=20K=C3=B6ppe?=
Date: Wed, 18 Sep 2024 17:04:44 +
Subject: [PATCH 1/2] [clang-tidy] Make modernize-use-nullptr mat
alexfh wrote:
Thanks for the clarification! The fact that there's code around that isn't
quite following the standard, is not news, but the regular way to approach
tightening the compiler is to provide an opt-out mechanism for some time (one
release cycle?) in the shape of a flag or otherwise
alexfh wrote:
> However, I suspect that the parentheses reduction and the one with a ternary
> are actually the same issue - The code is IFNDR per
> https://eel.is/c++draft/temp.over.link#5
>
> In you last example, M*2 and the conditional with M+N after the substitution
> of the default argum
https://github.com/zygoloid updated
https://github.com/llvm/llvm-project/pull/109208
>From 81193568c17a89f6cf42f43a82fb1fbf0f90184d Mon Sep 17 00:00:00 2001
From: Richard Smith
Date: Wed, 18 Sep 2024 21:59:56 +
Subject: [PATCH 1/2] Implement current CWG direction for string literal
compari
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Richard Smith (zygoloid)
Changes
Track the identity of each string literal object produced by evaluation
with a global version number. Accept comparisons between literals of the
same version, and between literals of different versions that
https://github.com/zygoloid ready_for_review
https://github.com/llvm/llvm-project/pull/109208
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/zygoloid edited
https://github.com/llvm/llvm-project/pull/109208
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/tarunprabhu created
https://github.com/llvm/llvm-project/pull/109210
Add support for -fdiagnostics-color and -fdiagnostics-color=. Add documentation
for -fdiagnostics-color= which should also be visible in clang.
Partially addresses requests in #89888
>From c5c827ab2c65da7b
https://github.com/zygoloid created
https://github.com/llvm/llvm-project/pull/109208
Track the identity of each string literal object produced by evaluation
with a global version number. Accept comparisons between literals of the
same version, and between literals of different versions that cann
llvmbot wrote:
@llvm/pr-subscribers-flang-driver
Author: Tarun Prabhu (tarunprabhu)
Changes
Add support for -fdiagnostics-color and -fdiagnostics-color=. Add documentation
for -fdiagnostics-color= which should also be visible in clang.
Partially addresses requests in #89888
---
Full dif
llvmbot wrote:
@llvm/pr-subscribers-clang-driver
Author: Tarun Prabhu (tarunprabhu)
Changes
Add support for -fdiagnostics-color and -fdiagnostics-color=. Add documentation
for -fdiagnostics-color= which should also be visible in clang.
Partially addresses requests in #89888
---
Full dif
https://github.com/zygoloid updated
https://github.com/llvm/llvm-project/pull/109208
>From 81193568c17a89f6cf42f43a82fb1fbf0f90184d Mon Sep 17 00:00:00 2001
From: Richard Smith
Date: Wed, 18 Sep 2024 21:59:56 +
Subject: [PATCH 1/3] Implement current CWG direction for string literal
compari
mizvekov wrote:
> Wow, I would never have thought it was a problem. Making these the same type
> removes the compilation error. Can you explain why this is a problem from the
> C++ standard PoV?
That's https://eel.is/c++draft/temp.deduct.type#20
In deduced contexts for an NTTP, the type of th
@@ -2419,8 +2419,13 @@ Value *ScalarExprEmitter::VisitCastExpr(CastExpr *CE) {
return Visit(const_cast(E));
case CK_NoOp: {
-return CE->changesVolatileQualification() ? EmitLoadOfLValue(CE)
- : Visit(const_cast(E));
+i
e-kwsm wrote:
This PR is ready but I have no permission.
https://github.com/llvm/llvm-project/pull/94014
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
alexfh wrote:
I see. A clear diagnostic wouldn't hurt indeed. Thanks a lot for the analysis!
No more concerns from our side at this point.
https://github.com/llvm/llvm-project/pull/100692
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https:/
@@ -839,9 +839,11 @@ int clang_scan_deps_main(int argc, char **argv, const
llvm::ToolContext &) {
auto R = std::make_reverse_iterator(FlagsEnd);
for (auto I = R, E = Args.rend(); I != E; ++I) {
StringRef Arg = *I;
+if ((I + 1) == E)
https://github.com/tkoeppe updated
https://github.com/llvm/llvm-project/pull/109169
From 6e056a2aad2b9b7957c18c8dfb8f64a44c7c785f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thomas=20K=C3=B6ppe?=
Date: Wed, 18 Sep 2024 17:04:44 +
Subject: [PATCH] [clang-tidy] Make modernize-use-nullptr matcher
Michael137 wrote:
> This change leads to a crash in `ConstStructBuilder::Build()` for the
> following program:
>
> ```
> struct S {
> };
>
> union U {
> struct S s;
> int x;
> };
>
> void foo() {
> union U bar = {};
> }
> ```
>
> `isEmptyRecordForLayout` returns false for `union
@@ -2419,8 +2419,13 @@ Value *ScalarExprEmitter::VisitCastExpr(CastExpr *CE) {
return Visit(const_cast(E));
case CK_NoOp: {
-return CE->changesVolatileQualification() ? EmitLoadOfLValue(CE)
- : Visit(const_cast(E));
+i
jhuber6 wrote:
> I like this direction and I think it should be the right way. However, IMHO,
> I think it needs discussion (and potentially an RFC).
Moving from the header to the definition in `compiler-rt` would warrant an RFC,
this patch just automatically links something that exists and wi
https://github.com/elizabethandrews created
https://github.com/llvm/llvm-project/pull/109182
The tests added for SYCL device compilation in
https://github.com/llvm/llvm-project/pull/88182 are incorrect SYCL tests. Code
technically should not have been emitted in SYCL device compilation for the
@@ -6037,13 +6038,24 @@ class AttributedType : public Type, public
llvm::FoldingSetNode {
private:
friend class ASTContext; // ASTContext creates these
+ const Attr *Attribute;
+
QualType ModifiedType;
QualType EquivalentType;
AttributedType(QualType canon, attr
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: None (elizabethandrews)
Changes
The tests added for SYCL device compilation in
https://github.com/llvm/llvm-project/pull/88182 are incorrect SYCL tests. Code
technically should not have been emitted in SYCL device compilation for these
t
mstorsjo wrote:
> > For the Mips backend itself, I would ask the Mips backend code
> > maintainer... but we don't have a maintainer for Mips. And we don't have
> > any buildbots. I'm really not sure about adding complexity to a backend
> > which is already suffering from a lack of anyone that
https://github.com/aaupov updated
https://github.com/llvm/llvm-project/pull/79942
>From 2a5a3f2f55bd2b7479278fa72f6f05e54033532c Mon Sep 17 00:00:00 2001
From: Amir Ayupov
Date: Wed, 19 Jul 2023 20:30:29 -0700
Subject: [PATCH] [Clang][CMake] Add CSSPGO support to LLVM_BUILD_INSTRUMENTED
Build
@@ -84,6 +84,14 @@ void test_macro_expansion4() {
#undef MY_NULL
}
+template struct pear {
+ T x;
+};
+void test_templated() {
+ pear p = { NULL };
fmayer wrote:
Doesn't this need some `CHECK` or `CHECK-NOT`?
https://github.com/llvm/llvm-project/pull/1091
@@ -33,7 +33,6 @@ enum CPUFeatures {
FEAT_FP,
FEAT_SIMD,
FEAT_CRC,
- FEAT_SHA1,
andrewcarlotti wrote:
> And the clang and gcc implementations of FMV are already ABI incompatible for
> other reasons.
Are they? I'm not currently aware of any incompatibil
https://github.com/nicovank created
https://github.com/llvm/llvm-project/pull/109178
Simplifies two cases and matches two new cases previously missing,
`container.end() [!=]= container.find(...)`.
I had split this change from #107521 for easier review.
>From a8b8ce089e9eeadf1b8b424e426f7372
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
Author: Nicolas van Kempen (nicovank)
Changes
Simplifies two cases and matches two new cases previously missing,
`container.end() [!=]= container.find(...)`.
I had split this change from #107521 for easier review.
---
Full diff: ht
https://github.com/eddyz87 edited
https://github.com/llvm/llvm-project/pull/108636
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -766,8 +766,19 @@ static void EmitAtomicOp(CodeGenFunction &CGF, AtomicExpr
*Expr, Address Dest,
// LLVM atomic instructions always have synch scope. If clang atomic
// expression has no scope operand, use default LLVM synch scope.
if (!ScopeModel) {
+llvm::SyncSc
mizvekov wrote:
It's one thing that we might tweak the rules to account for redundant
parenthesis.
But the more complete example shows there is no way to order these unrelated
things.
Note that we hadn't so far implemented these rules for partial ordering of
function templates, but the same i
@@ -69,29 +69,25 @@ void BPFSubtarget::initSubtargetFeatures(StringRef CPU,
StringRef FS) {
CPU = "v3";
if (CPU == "probe")
CPU = sys::detail::getHostCPUNameForBPF();
- if (CPU == "generic" || CPU == "v1")
+ if (CPU.empty() || CPU == "generic" || CPU == "v1")
-
https://github.com/eddyz87 edited
https://github.com/llvm/llvm-project/pull/108636
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -621,6 +642,16 @@ let Predicates = [BPFHasLdsx] in {
def LDD : LOADi64;
+class acquiring_load
+: PatFrag<(ops node:$ptr), (base node:$ptr)> {
+ let IsAtomic = 1;
eddyz87 wrote:
Note: in #107343 we decided to fallback to more strong orderings if there
https://github.com/eddyz87 commented:
I think this looks fine, but syntax seems like it adds to zoo we already have.
E.g. there are already instructions like `lock *(u32 *)(r1 + 0x0) &= w2` and we
treat these as having `monotonic` / `memory_order_relaxed` semantics (see
#107343).
It seems, to m
@@ -33,7 +33,6 @@ enum CPUFeatures {
FEAT_FP,
FEAT_SIMD,
FEAT_CRC,
- FEAT_SHA1,
efriedma-quic wrote:
We've generally been more conservative with compiler-rt.builtins compared with
other parts of compiler-rt, like sanitizers. People do ship static lib
alexfh wrote:
Wow, I would never have thought it was a problem. Making these the same type
removes the compilation error. Can you explain why this is a problem from the
C++ standard PoV?
https://github.com/llvm/llvm-project/pull/100692
___
cfe-commit
goldsteinn wrote:
ping5
https://github.com/llvm/llvm-project/pull/91101
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -434,6 +434,15 @@ struct AAAMDAttributesFunction : public AAAMDAttributes {
indicatePessimisticFixpoint();
return;
}
+
+for (Instruction &I : instructions(F)) {
+ if (isa(I) &&
jwanggit86 wrote:
@arsenm Following constants to see if
https://github.com/zygoloid edited
https://github.com/llvm/llvm-project/pull/109208
___
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 `clang-x86_64-debian-fast`
running on `gribozavr4` while building `clang` at step 4 "cmake-configure".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/56/builds/7718
Here is the relevant piece of the b
@@ -870,6 +904,15 @@ bool ConstStructBuilder::Build(const APValue &Val, const
RecordDecl *RD,
if (!EltInit)
return false;
+if (ZeroInitPadding) {
+ if (!DoZeroInitPadding(Layout, FieldNo, *Field, SizeSoFar,
+ IsFlexibleArray, All
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib`
running on `gribozavr4` while building `clang` at step 4 "cmake-configure".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/60/builds/7937
Here is the relevant piece of the b
https://github.com/hnrklssn created
https://github.com/llvm/llvm-project/pull/109171
This reverts commits c96ee0ffaf5ee7afa1f4b0be0662852f57b47244 and
9ceb9676678ad979a0b767450855d7852ce6a553.
Discussion in github PR #108658.
>From 0c8a40ed24b0b5f319fd2fb49a27703dc7f1 Mon Sep 17 00:00:00
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Henrik G. Olsson (hnrklssn)
Changes
This reverts commits c96ee0ffaf5ee7afa1f4b0be0662852f57b47244 and
9ceb9676678ad979a0b767450855d7852ce6a553.
Discussion in github PR #108658.
---
Patch is 34.08 KiB, truncated to 20.00 KiB below, full
kazutakahirata wrote:
I cannot immediately think of common ways in which an iterator stays valid, but
if you don't enable assertions or `LLVM_ENABLE_ABI_BREAKING_CHECKS`, you may be
able to avoid a crash although that doesn't necessarily mean that clang-tidy i
https://github.com/MichelleCDjunaidi updated
https://github.com/llvm/llvm-project/pull/106675
>From 08324e3586acb16cbf010fd6013c21f2b5faa64e Mon Sep 17 00:00:00 2001
From: MichelleCDjunaidi <87893361+michellecdjuna...@users.noreply.github.com>
Date: Fri, 30 Aug 2024 14:55:16 +0800
Subject: [PATC
MichelleCDjunaidi wrote:
I will need help to merge this once approved. Thank you so much!
https://github.com/llvm/llvm-project/pull/106675
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commi
Author: Henrik G. Olsson
Date: 2024-09-18T10:51:53-07:00
New Revision: 13502c7f2c053b2a060f7b9926328cfda46404de
URL:
https://github.com/llvm/llvm-project/commit/13502c7f2c053b2a060f7b9926328cfda46404de
DIFF:
https://github.com/llvm/llvm-project/commit/13502c7f2c053b2a060f7b9926328cfda46404de.di
Author: Helena Kotas
Date: 2024-09-18T10:51:30-07:00
New Revision: f2128267c26e548bef59209e7a351ff94d343bf3
URL:
https://github.com/llvm/llvm-project/commit/f2128267c26e548bef59209e7a351ff94d343bf3
DIFF:
https://github.com/llvm/llvm-project/commit/f2128267c26e548bef59209e7a351ff94d343bf3.diff
https://github.com/hekota closed
https://github.com/llvm/llvm-project/pull/108924
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/hnrklssn closed
https://github.com/llvm/llvm-project/pull/109171
___
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 `premerge-monolithic-linux`
running on `premerge-linux-1` while building `clang` at step 5
"cmake-configure".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/153/builds/9302
Here is the relevant piece
https://github.com/kazutakahirata updated
https://github.com/llvm/llvm-project/pull/109145
>From c230f7e30e60f11c5675ec1dd9f49f5f6378dc6f Mon Sep 17 00:00:00 2001
From: Kazu Hirata
Date: Wed, 18 Sep 2024 00:19:25 -0700
Subject: [PATCH 1/2] [clang-tidy] Fix performance-unnecessary-value-param
T
@@ -118,10 +118,19 @@ class FunctionParmMutationAnalyzer {
static FunctionParmMutationAnalyzer *
getFunctionParmMutationAnalyzer(const FunctionDecl &Func, ASTContext
&Context,
ExprMutationAnalyzer::Memoized &Memorized) {
-auto [it, Ins
@@ -96,6 +96,8 @@ def note_constexpr_pointer_constant_comparison : Note<
"at runtime">;
def note_constexpr_literal_comparison : Note<
"comparison of addresses of literals has unspecified value">;
+def note_constexpr_opaque_call_comparison : Note<
+ "comparison against opaq
@@ -2061,15 +2063,21 @@ static bool EvaluateIgnoredValue(EvalInfo &Info, const
Expr *E) {
return true;
}
-/// Should this call expression be treated as a no-op?
-static bool IsNoOpCall(const CallExpr *E) {
+/// Should this call expression be treated as forming an opaque con
@@ -2142,11 +2150,81 @@ static const ValueDecl *GetLValueBaseDecl(const LValue
&LVal) {
return LVal.Base.dyn_cast();
}
-static bool IsLiteralLValue(const LValue &Value) {
- if (Value.getLValueCallIndex())
+// Information about an LValueBase that is some kind of string.
+st
1 - 100 of 410 matches
Mail list logo
