@@ -123,6 +121,25 @@ bool hasValidBranchWeightMD(const Instruction &I) {
return getValidBranchWeightMDNode(I);
}
+bool hasBranchWeightProvenance(const Instruction &I) {
+ auto *ProfileData = I.getMetadata(LLVMContext::MD_prof);
+ return hasBranchWeightProvenance(ProfileDat
@@ -55,6 +55,17 @@ MDNode *getBranchWeightMDNode(const Instruction &I);
/// Nullptr otherwise.
MDNode *getValidBranchWeightMDNode(const Instruction &I);
+/// Check if Branch Weight Metadata has an "expected" field from an
llvm.expect*
+/// intrinsic
+bool hasBranchWeightProve
https://github.com/david-xl edited
https://github.com/llvm/llvm-project/pull/86609
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Mehdi Amini
Date: 2024-06-05T21:13:29-07:00
New Revision: 60d8b31b055ebc9211ccd1326c8ee73602f71a88
URL:
https://github.com/llvm/llvm-project/commit/60d8b31b055ebc9211ccd1326c8ee73602f71a88
DIFF:
https://github.com/llvm/llvm-project/commit/60d8b31b055ebc9211ccd1326c8ee73602f71a88.diff
L
owenca wrote:
> @owenca Do you have a release note we can put in the release announcement?
Release note:
Fixes a clang-format regression (since 17.0.6) on formatting `goto` labels in
macro definitions.
https://github.com/llvm/llvm-project/pull/93494
owenca wrote:
@tstellar thanks!
> @owenca Do you have a release note we can put in the release announcement?
Release note:
Fixes clang-format (since 18.1.1) regressions on breaking before a stream
insertion operator (<<) when both operands are string literals.
https://github.com/llvm/llvm-pro
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/93494
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Owen Pan
Date: 2024-06-05T14:56:32-07:00
New Revision: 768118d1ad38bf13c545828f67bd6b474d61fc55
URL:
https://github.com/llvm/llvm-project/commit/768118d1ad38bf13c545828f67bd6b474d61fc55
DIFF:
https://github.com/llvm/llvm-project/commit/768118d1ad38bf13c545828f67bd6b474d61fc55.diff
LOG:
tstellar wrote:
@owenca Do you have a release note we can put in the release announcement?
https://github.com/llvm/llvm-project/pull/94091
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/l
tstellar wrote:
@owenca Do you have a release note we can put in the release announcement?
https://github.com/llvm/llvm-project/pull/93494
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
https://github.com/tstellar updated
https://github.com/llvm/llvm-project/pull/93494
>From 768118d1ad38bf13c545828f67bd6b474d61fc55 Mon Sep 17 00:00:00 2001
From: Owen Pan
Date: Tue, 21 May 2024 01:35:31 -0700
Subject: [PATCH] [clang-format] Fix a bug in formatting goto labels in macros
(#92494
https://github.com/tstellar closed
https://github.com/llvm/llvm-project/pull/94091
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Author: Owen Pan
Date: 2024-06-05T14:55:50-07:00
New Revision: 8c0fe0d65ed85966c0ac075e896620c55ca95227
URL:
https://github.com/llvm/llvm-project/commit/8c0fe0d65ed85966c0ac075e896620c55ca95227
DIFF:
https://github.com/llvm/llvm-project/commit/8c0fe0d65ed85966c0ac075e896620c55ca95227.diff
LOG:
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/90146
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/90146
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/86610
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/86609
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/86610
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/86609
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
kbeyls wrote:
> I'll also mention that I left the original variable naming but did re-format
> the file, whitespace being more friendly to diffs, and this being nice and
> tidily contained. If you or others have strong opinions, I'm happy to
> recapitalize the names.
I don't have a strong opi
owenca wrote:
@tstellar strictly speaking, this is a regression fix. (It's a churn within
18.x release cycle.)
1. Risk level: low IMO. (The other code owner @mydeveloperday approved it to be
included in 18.1.7.)
2. Last known working version: 18.1.4
https://github.com/llvm/llvm-project/pull/9
owenca wrote:
@tstellar
> 1. How risky is this fix?
Very low IMO. (@mydeveloperday @HazardyKnusperkeks @rymiel can chime in if
anyone thinks otherwise.)
> 2. When was the last known working version of clang-format?
17.0.6 (regressed since 18.1.1).
https://github.com/llvm/llvm-project/pull/9
@@ -16,22 +16,21 @@
## The output file must include all sections.
# RUN: llvm-readelf -S %t/a.elf | FileCheck %s
-# CHECK: There are 12 section headers, starting at offset 0x2140:
+# CHECK: There are 12 section headers, starting at offset 0x2138:
# CHECK: [Nr]
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/93761
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/MaskRay edited
https://github.com/llvm/llvm-project/pull/93761
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/MaskRay updated
https://github.com/llvm/llvm-project/pull/93761
>From 316e0a1effb50b15fa1df54a43d02704f735309d Mon Sep 17 00:00:00 2001
From: Fangrui Song
Date: Wed, 29 May 2024 20:14:18 -0700
Subject: [PATCH] =?UTF-8?q?[=F0=9D=98=80=F0=9D=97=BD=F0=9D=97=BF]=20initia?=
=?UTF
ahmedbougacha wrote:
I'll also mention that I left the original variable naming but did re-format
it, whitespace being more friendly to diffs, and this being nice and tidily
contained. If you or others have strong opinions, I'm happy to recapitalize
them.
https://github.com/llvm/llvm-project
ahmedbougacha wrote:
> Do I understand correctly that "remove big-endian support" results in this
> code not running correctly on big-endian machines? I don't recall the LLVM
> project claiming that it cannot run on big-endian machines. If I understand
> this correctly, I would not remove the
@@ -58,21 +38,15 @@
v2 = ROTL(v2, 32);
\
} while (0)
-/*
ahmedbougacha wrote:
Fair, added it back with minor tweaks; I didn't describe the template
parameters because, frankly, I'm not sure I wo
https://github.com/ahmedbougacha updated
https://github.com/llvm/llvm-project/pull/94394
>From 1e9a3fde97d907c3cd6be33db91d1c18c7236ffb Mon Sep 17 00:00:00 2001
From: Ahmed Bougacha
Date: Tue, 4 Jun 2024 12:41:47 -0700
Subject: [PATCH 1/4] [Support] Reformat SipHash.cpp to match libSupport.
Wh
tstellar wrote:
@owenca OK, can you give me more details:
1) How risky is this fix?
2) When was the last known working version of clang-format?
https://github.com/llvm/llvm-project/pull/93494
___
llvm-branch-commits mailing list
llvm-branch-commits@lis
@@ -2155,6 +2155,17 @@ bool RISCVAsmParser::parseVTypeToken(const AsmToken
&Tok, VTypeState &State,
break;
if (!RISCVVType::isValidLMUL(Lmul, Fractional))
break;
+
+if (Fractional) {
+ unsigned ELEN = STI->hasFeature(RISCV::FeatureStdExtZve64x) ? 64 :
@@ -71,18 +73,21 @@ vsetvli a2, a0, e32, m8, ta, ma
vsetvli a2, a0, e32, mf2, ta, ma
# CHECK-INST: vsetvli a2, a0, e32, mf2, ta, ma
+# CHECK-WARNING: :[[#@LINE-2]]:17: warning: SEW > 16 may not be compatible
with all RVV implementations{{$}}
# CHECK-ENCODING: [0x57,0x76,0x75
@@ -71,18 +73,21 @@ vsetvli a2, a0, e32, m8, ta, ma
vsetvli a2, a0, e32, mf2, ta, ma
# CHECK-INST: vsetvli a2, a0, e32, mf2, ta, ma
+# CHECK-WARNING: :[[#@LINE-2]]:17: warning: SEW > 16 may not be compatible
with all RVV implementations{{$}}
# CHECK-ENCODING: [0x57,0x76,0x75
@@ -2155,6 +2155,17 @@ bool RISCVAsmParser::parseVTypeToken(const AsmToken
&Tok, VTypeState &State,
break;
if (!RISCVVType::isValidLMUL(Lmul, Fractional))
break;
+
+if (Fractional) {
+ unsigned ELEN = STI->hasFeature(RISCV::FeatureStdExtZve64x) ? 64 :
@@ -2155,6 +2155,17 @@ bool RISCVAsmParser::parseVTypeToken(const AsmToken
&Tok, VTypeState &State,
break;
if (!RISCVVType::isValidLMUL(Lmul, Fractional))
break;
+
+if (Fractional) {
+ unsigned ELEN = STI->hasFeature(RISCV::FeatureStdExtZve64x) ? 64 :
@@ -2211,6 +2223,18 @@ ParseStatus RISCVAsmParser::parseVTypeI(OperandVector
&Operands) {
if (getLexer().is(AsmToken::EndOfStatement) && State == VTypeState_Done) {
RISCVII::VLMUL VLMUL = RISCVVType::encodeLMUL(Lmul, Fractional);
+if (Fractional) {
+ unsigned E
@@ -2155,6 +2155,17 @@ bool RISCVAsmParser::parseVTypeToken(const AsmToken
&Tok, VTypeState &State,
break;
if (!RISCVVType::isValidLMUL(Lmul, Fractional))
break;
+
+if (Fractional) {
+ unsigned ELEN = STI->hasFeature(RISCV::FeatureStdExtZve64x) ? 64 :
owenca wrote:
@tstellar this is a regression fix as labeled by the issue the original
pr/commit fixed. :)
https://github.com/llvm/llvm-project/pull/93494
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cg
https://github.com/agozillon approved this pull request.
LGTM, and tested it locally and it seems to fix the issue I encountered! Thank
you very much for this fix :-)
https://github.com/llvm/llvm-project/pull/94495
___
llvm-branch-commits mailing lis
tstellar wrote:
@owenca I'm only going to take regression fixes for 18.1.7.
https://github.com/llvm/llvm-project/pull/94091
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bra
tstellar wrote:
@owenca I'm only going to take regression fixes for 18.1.7.
https://github.com/llvm/llvm-project/pull/93494
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bra
https://github.com/AtariDreams updated
https://github.com/llvm/llvm-project/pull/91038
>From a62c1fce19ad9c1bf6899e9b528a07593909be8f Mon Sep 17 00:00:00 2001
From: Craig Topper
Date: Fri, 3 May 2024 09:59:33 -0700
Subject: [PATCH] [DAGCombiner] In mergeTruncStore, make sure we aren't storing
https://github.com/AtariDreams updated
https://github.com/llvm/llvm-project/pull/91038
>From 7f8d5e96e879f2e63a0c751547b4754f2634 Mon Sep 17 00:00:00 2001
From: Craig Topper
Date: Fri, 3 May 2024 09:59:33 -0700
Subject: [PATCH 1/3] [DAGCombiner] In mergeTruncStore, make sure we aren't
stor
llvmbot wrote:
@llvm/pr-subscribers-flang-openmp
@llvm/pr-subscribers-flang-fir-hlfir
Author: Krzysztof Parzyszek (kparzysz)
Changes
Derived type components may use a given `Symbol` regardless of what parent
objects they are a part of. Because of that, simply using a symbol address is
no
https://github.com/AtariDreams updated
https://github.com/llvm/llvm-project/pull/92478
>From aafe93171093465519add9aeab56c1f7f779f0f9 Mon Sep 17 00:00:00 2001
From: Nuri Amari
Date: Wed, 15 May 2024 09:21:02 -0700
Subject: [PATCH] [lld] Fix -ObjC load behavior with LTO (#92162)
When -ObjC is p
https://github.com/kparzysz created
https://github.com/llvm/llvm-project/pull/94495
Derived type components may use a given `Symbol` regardless of what parent
objects they are a part of. Because of that, simply using a symbol address is
not sufficient to determine object identity.
Make the de
@@ -330,35 +377,46 @@ AST_POLYMORPHIC_MATCHER_P(isExpandedFromMacro,
/// Matches declarations.
///
-/// Examples matches \c X, \c C, and the friend declaration inside \c C;
+/// Given
/// \code
/// void X();
/// class C {
-/// friend X;
+/// friend void X();
//
wangpc-pp wrote:
We may need it in binutils too. cc @kito-cheng
https://github.com/llvm/llvm-project/pull/94313
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangpc-pp updated
https://github.com/llvm/llvm-project/pull/94313
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/wangpc-pp updated
https://github.com/llvm/llvm-project/pull/94313
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Wentao Zhang (whentojump)
Changes
Backports #89869 and #91446 (and associated tests in
3591da9f1ccbd8b19fef4814f96638dbbe9c2b40) that fixes missing code regions and
`llvm-cov` crashes.
With them, we are able to measure MC/DC of large C/C
https://github.com/whentojump edited
https://github.com/llvm/llvm-project/pull/94438
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/whentojump milestoned
https://github.com/llvm/llvm-project/pull/94438
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/whentojump created
https://github.com/llvm/llvm-project/pull/94438
Backports #89869 and #91446 (and associated tests in
3591da9f1ccbd8b19fef4814f96638dbbe9c2b40) that fixes missing code regions and
`llvm-cov` crashes.
With them, we are able to measure MC/DC of large C/C++ p
@@ -1,25 +1,19 @@
-/*
- SipHash reference C implementation
-
- Copyright (c) 2012-2022 Jean-Philippe Aumasson
-
- Copyright (c) 2012-2014 Daniel J. Bernstein
-
- To the extent possible under law, the author(s) have dedicated all copyright
- and related and neighborin
@@ -58,21 +38,15 @@
v2 = ROTL(v2, 32);
\
} while (0)
-/*
-Computes a SipHash value
-*in: pointer to input data (read-only)
-inlen: input data length in bytes (any size_t value)
-*k: pointer to the k
https://github.com/kbeyls requested changes to this pull request.
Do I understand correctly that "remove big-endian support" results in this code
not running correctly on big-endian machines?
I don't recall the LLVM project claiming that it cannot run on big-endian
machines.
If I understand thi
@@ -58,21 +38,15 @@
v2 = ROTL(v2, 32);
\
} while (0)
-/*
kbeyls wrote:
It might be worthwhile to keep (an edited version of) this comment? It wasn't
immediately obvious to me what the value is of
@@ -58,21 +38,15 @@
v2 = ROTL(v2, 32);
\
} while (0)
-/*
-Computes a SipHash value
-*in: pointer to input data (read-only)
-inlen: input data length in bytes (any size_t value)
-*k: pointer to the k
https://github.com/kbeyls edited https://github.com/llvm/llvm-project/pull/94394
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
61 matches
Mail list logo
