Author: Jesse Huang
Date: 2025-03-22T14:48:52+08:00
New Revision: 20b5728b7b1ccc4509a316efb270d46cc9526d69
URL:
https://github.com/llvm/llvm-project/commit/20b5728b7b1ccc4509a316efb270d46cc9526d69
DIFF:
https://github.com/llvm/llvm-project/commit/20b5728b7b1ccc4509a316efb270d46cc9526d69.diff
L
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/10370
https://github.com/jaidTw closed
https://github.com/llvm/llvm-project/pull/132259
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -378,6 +370,14 @@ def FeatureStdExtZca
"part of the C extension, excluding compressed "
"floating point loads/stores">;
+def FeatureStdExtC
+: RISCVExtension<2, 0, "Compressed Instructions", [FeatureStdExtZca]>,
+ RISCVExte
tbaederr wrote:
It looks like this is similar to `__builtin_constant_p` - what is the proposed
behavior wrt. side effects in the evaluated expression? gcc and clang disagree
about this a lot currently: https://godbolt.org/z/rbneznT9z
https://github.com/llvm/llvm-project/pull/132524
___
https://github.com/tbaederr deleted
https://github.com/llvm/llvm-project/pull/132524
___
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: Kees Cook (kees)
Changes
Provide a way to introspect expressions to see if they are assignable, which
becomes very useful in macros that want to perform additional work on arguments
that are lvalues. GCC is adding this builtin as well:
h
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Timm Baeder (tbaederr)
Changes
As pointed out by @shafik, this confuses static analysis and most
probably humans as well. Add an assertion to ensure the given array has at
least one element.
---
Full diff: https://github.com/llvm/llvm-pr
@@ -964,6 +964,13 @@ def IsConstantEvaluated : LangBuiltin<"CXX_LANG"> {
let Prototype = "bool()";
}
+def IsLValue : Builtin {
+ let Spellings = ["__builtin_is_modifiable_lvalue"];
+ let Attributes = [NoThrow, CustomTypeChecking, UnevaluatedArguments,
+
https://github.com/tbaederr created
https://github.com/llvm/llvm-project/pull/132527
As pointed out by @shafik, this confuses static analysis and most probably
humans as well. Add an assertion to ensure the given array has at least one
element.
>From ed5dd8936d615c19f7b6d7d3ec607374f28ebf47 M
https://github.com/tbaederr closed
https://github.com/llvm/llvm-project/pull/132523
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Timm Baeder
Date: 2025-03-22T07:12:27+01:00
New Revision: d67951694b3c7e918b9a5e6a0e6e346e42d72755
URL:
https://github.com/llvm/llvm-project/commit/d67951694b3c7e918b9a5e6a0e6e346e42d72755
DIFF:
https://github.com/llvm/llvm-project/commit/d67951694b3c7e918b9a5e6a0e6e346e42d72755.diff
L
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-fast` running on `sanitizer-buildbot3` while building
`clang,libc` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/169/builds/9678
Here is the relevant pi
@@ -230,10 +230,16 @@ bool PEI::runOnMachineFunction(MachineFunction &MF) {
// with stack arguments.
TFI->spillFPBP(MF);
+ LLVM_DEBUG(llvm::dbgs() << "Before calculateCallFrameInfo \n");
lenary wrote:
Oh yeah, oops, lots of it. will remove.
https://gith
kazutakahirata wrote:
@svs-quic I've reverted this PR for now. I'm happy to try your revised patch.
Thanks!
https://github.com/llvm/llvm-project/pull/132184
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailm
https://github.com/DeinAlptraum closed
https://github.com/llvm/llvm-project/pull/132378
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/kees created https://github.com/llvm/llvm-project/pull/132524
Provide a way to introspect expressions to see if they are assignable, which
becomes very useful in macros that want to perform additional work on arguments
that are lvalues. GCC is adding this builtin as well:
ht
svs-quic wrote:
> Please avoid "Revert 'Revert" in commit names. Use "Recommit".
Thanks I've made the change while committing.
https://github.com/llvm/llvm-project/pull/132520
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.
Author: Matheus Izvekov
Date: 2025-03-22T02:05:40-03:00
New Revision: 45270853192db53022ccadf4767999af4fe4e332
URL:
https://github.com/llvm/llvm-project/commit/45270853192db53022ccadf4767999af4fe4e332
DIFF:
https://github.com/llvm/llvm-project/commit/45270853192db53022ccadf4767999af4fe4e332.dif
https://github.com/svs-quic closed
https://github.com/llvm/llvm-project/pull/132520
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Sudharsan Veeravalli
Date: 2025-03-22T11:07:48+05:30
New Revision: e7107973b83b7053f3ba92a40a33a27db0c90529
URL:
https://github.com/llvm/llvm-project/commit/e7107973b83b7053f3ba92a40a33a27db0c90529
DIFF:
https://github.com/llvm/llvm-project/commit/e7107973b83b7053f3ba92a40a33a27db0c9052
topperc wrote:
Please avoid "Revert 'Revert" in commit names. Use "Recommit".
https://github.com/llvm/llvm-project/pull/132520
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
phoebewang wrote:
> LGTM. Clang format changes look valid.
I think the `(__mmask8) - 1` doesn't make sense. Seems clang-format takes
`__mmask8` as a variable rather than a type. It appares since some version and
really annoying.
https://github.com/llvm/llvm-project/pull/132426
___
https://github.com/benshi001 closed
https://github.com/llvm/llvm-project/pull/131976
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Ben Shi
Date: 2025-03-22T13:22:32+08:00
New Revision: 597accfea6150e77304427fb97d0c3798178e040
URL:
https://github.com/llvm/llvm-project/commit/597accfea6150e77304427fb97d0c3798178e040
DIFF:
https://github.com/llvm/llvm-project/commit/597accfea6150e77304427fb97d0c3798178e040.diff
LOG:
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Timm Baeder (tbaederr)
Changes
Unfortunately, a few circumstances make the implementation here less than
ideal, but we need to handle overlapping regions anyway.
---
Full diff: https://github.com/llvm/llvm-project/pull/132523.diff
2 Fil
https://github.com/mizvekov closed
https://github.com/llvm/llvm-project/pull/132516
___
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-driver
Author: Sudharsan Veeravalli (svs-quic)
Changes
…on (#132184)""
This reverts commit fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.
With a minor fix for the build failures.
---
Patch is 21.58 KiB, truncated to 20.00 KiB below, full version:
h
https://github.com/hekota updated
https://github.com/llvm/llvm-project/pull/131032
>From 7ebfc826ca27c71ef80f4a1b38b2d3a2e155b777 Mon Sep 17 00:00:00 2001
From: Helena Kotas
Date: Wed, 12 Mar 2025 14:09:24 -0700
Subject: [PATCH 1/3] [HLSL][NFC] Refactoring HLSLExternalSemaSource
Moving builder
erichkeane wrote:
> > How'd you manage to find the right ones? IMO we should be using
> > include-what-you-use on these to make sure we get it right (if you have
> > already, disregard this).
> > Also, can you share before-split/after-split/after-this build time
> > benchmarks? Does this get u
llvmbot wrote:
@llvm/pr-subscribers-mc
Author: Sudharsan Veeravalli (svs-quic)
Changes
…on (#132184)""
This reverts commit fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.
With a minor fix for the build failures.
---
Patch is 21.58 KiB, truncated to 20.00 KiB below, full version:
https://git
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Sudharsan Veeravalli (svs-quic)
Changes
…on (#132184)""
This reverts commit fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.
With a minor fix for the build failures.
---
Patch is 21.58 KiB, truncated to 20.00 KiB below, full version:
https://
llvmbot wrote:
@llvm/pr-subscribers-backend-risc-v
Author: Sudharsan Veeravalli (svs-quic)
Changes
…on (#132184)""
This reverts commit fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.
With a minor fix for the build failures.
---
Patch is 21.58 KiB, truncated to 20.00 KiB below, full version:
Author: Jannick Kremer
Date: 2025-03-22T02:40:20+01:00
New Revision: 619ba920efc25aebb5e7e9e7a777964588616441
URL:
https://github.com/llvm/llvm-project/commit/619ba920efc25aebb5e7e9e7a777964588616441
DIFF:
https://github.com/llvm/llvm-project/commit/619ba920efc25aebb5e7e9e7a777964588616441.diff
https://github.com/svs-quic created
https://github.com/llvm/llvm-project/pull/132520
…on (#132184)""
This reverts commit fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.
With a minor fix for the build failures.
>From 120916cbfeb248dbf9647ffea563e202afcfafe1 Mon Sep 17 00:00:00 2001
From: Sudharsan V
https://github.com/rniwa created
https://github.com/llvm/llvm-project/pull/132518
This PR adds the support for treating capturing of "self" as safe if the lambda
simultaneously captures "protectedSelf", which is a RetainPtr of "self".
This PR also fixes a bug that the checker wasn't generating
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-sve-vls`
running on `linaro-g3-04` while building `clang,llvm` at step 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/143/builds/6370
Here is the relevant piece of th
tbaederr wrote:
The tests should go into a file not under `ByteCode/` since they aren't
specific to the bytecode interpreter. There should be existing placement new
tests in `SemaCXX/`.
https://github.com/llvm/llvm-project/pull/132460
___
cfe-commits
DanielCChen wrote:
The intention is to make this PR for flang-rt only. As discussed with
@daltenty, I remove the NFC-change of adding an overriding `getCompilerRT` in
`AIX.cpp` as it actually breaches into clang space.
https://github.com/llvm/llvm-project/pull/131041
__
kazutakahirata wrote:
> hi @kazutakahirata i had fixed the failure in #132502 and was just about to
> merge it.
Oops. Sorry about that. Would you mind relanding this and #132502, maybe in a
single merge?
https://github.com/llvm/llvm-project/pull/132184
__
@@ -16,3 +17,16 @@ def test_file(self):
self.assertEqual(str(file), "t.c")
self.assertEqual(file.name, "t.c")
self.assertEqual(repr(file), "")
+
+def test_file_eq(self):
+path = os.path.join(kInputsDir, "hello.cpp")
+header_path = os.
llvmbot wrote:
@llvm/pr-subscribers-libc
Author: Matheus Izvekov (mizvekov)
Changes
This moves the diagnostic for member pointers pointing into non-class into
BuildMemberPointer, so that it can be used from RebuildMemberPointer, when
instantiating templates.
Also adds a minor tweak to t
https://github.com/mizvekov created
https://github.com/llvm/llvm-project/pull/132516
This moves the diagnostic for member pointers pointing into non-class into
BuildMemberPointer, so that it can be used from RebuildMemberPointer, when
instantiating templates.
Also adds a minor tweak to the di
https://github.com/DanielCChen updated
https://github.com/llvm/llvm-project/pull/131041
>From c394e25b3af722d76338bf7ab02d87de2a23074b Mon Sep 17 00:00:00 2001
From: Daniel Chen
Date: Wed, 12 Mar 2025 18:23:14 -0400
Subject: [PATCH 01/12] [flang-rt] Pass the whole path of libflang_rt.runtime.a
svs-quic wrote:
hi @kazutakahirata i had fixed the failure in #132502 and was just about to
merge it.
https://github.com/llvm/llvm-project/pull/132184
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/lis
https://github.com/ZhongUncle edited
https://github.com/llvm/llvm-project/pull/132510
___
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-analysis
Author: Kazu Hirata (kazutakahirata)
Changes
DenseSet, SmallPtrSet, SmallSet, SetVector, and StringSet recently
gained C++23-style insert_range. This patch replaces:
Dest.insert(Src.begin(), Src.end());
with:
Dest.insert_range(Src)
ZhongUncle wrote:
I am not familiar with PR, so accidentally closed this PR. I create a new one
#132510
https://github.com/llvm/llvm-project/pull/132360
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/lis
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-global-isel`
running on `linaro-clang-aarch64-global-isel` while building `clang,llvm` at
step 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/125/builds/6449
Here is
llvmbot wrote:
@llvm/pr-subscribers-clang-tools-extra
Author: None (ZhongUncle)
Changes
Fixes https://github.com/llvm/llvm-project/issues/59819. The underlying problem
was fixed in https://reviews.llvm.org/D142560, but this patch adds a proper
regression test.
I am not familiar with PR,
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
https://github.com/ZhongUncle created
https://github.com/llvm/llvm-project/pull/132510
Fixes https://github.com/llvm/llvm-project/issues/59819. The underlying problem
was fixed in https://reviews.llvm.org/D142560, but this patch adds a proper
regression test.
I am not familiar with PR, so acc
llvmbot wrote:
@llvm/pr-subscribers-clang
@llvm/pr-subscribers-clang-static-analyzer-1
Author: Kazu Hirata (kazutakahirata)
Changes
DenseSet, SmallPtrSet, SmallSet, SetVector, and StringSet recently
gained C++23-style insert_range. This patch replaces:
Dest.insert(Src.begin(), Src.end(
https://github.com/kazutakahirata created
https://github.com/llvm/llvm-project/pull/132507
DenseSet, SmallPtrSet, SmallSet, SetVector, and StringSet recently
gained C++23-style insert_range. This patch replaces:
Dest.insert(Src.begin(), Src.end());
with:
Dest.insert_range(Src);
This pat
https://github.com/kr-2003 updated
https://github.com/llvm/llvm-project/pull/132427
>From 72aafcc255bbcfccb3fa5317e260faf97a3dfed5 Mon Sep 17 00:00:00 2001
From: kr-2003
Date: Fri, 21 Mar 2025 20:45:11 +0530
Subject: [PATCH 1/3] [clang][analyzer] Removed warnings for unnamed bitfields
---
...
@@ -0,0 +1,36 @@
+// RUN: %clang_cc1 -finclude-default-header -triple
dxil-pc-shadermodel6.6-library %s -fnative-half-type -emit-llvm-only
-disable-llvm-passes -verify
+
+float test_too_few_arg() {
+ return __builtin_hlsl_dot2add();
+ // expected-error@-1 {{too few arguments t
https://github.com/ZhongUncle closed
https://github.com/llvm/llvm-project/pull/132360
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/ilovepi created
https://github.com/llvm/llvm-project/pull/132482
Currently, when we set URLs from JS, we set them only using the protocol
and host locations. This works fine when docs are served from the base
directory of the site, but if you want to nest it under another
dire
Author: Kazu Hirata
Date: 2025-03-21T20:28:11-07:00
New Revision: fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e
URL:
https://github.com/llvm/llvm-project/commit/fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e
DIFF:
https://github.com/llvm/llvm-project/commit/fe7776eab87b3c79372b2056a6e0dd9ef1c4b10e.diff
L
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-armv7-global-isel`
running on `linaro-clang-armv7-global-isel` while building `clang,llvm` at step
6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/39/builds/5224
Here is the
svs-quic wrote:
I've already subscribed to pr-subscribers-backend:RISC-V but the change
renaming VariantKind to Specifier was directly commited to the repo. Is there a
way I can get notified for direct commits as well?
https://github.com/llvm/llvm-project/pull/132184
__
https://github.com/Endilll edited
https://github.com/llvm/llvm-project/pull/130383
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff 3840f787a21a66686f5d8bf61877d41f3a65f205
109fd75a7fd3e5d8292579e571440c429a0b9cc2 --e
https://github.com/DeinAlptraum updated
https://github.com/llvm/llvm-project/pull/130383
>From e8bf3b6f08f0e0030ea36fe8c42fcde166ad27e3 Mon Sep 17 00:00:00 2001
From: Mathias Stearn
Date: Thu, 19 Dec 2024 16:22:04 +0100
Subject: [PATCH 1/6] [libclang/python] Add equality comparison operators fo
https://github.com/DeinAlptraum updated
https://github.com/llvm/llvm-project/pull/130383
>From e8bf3b6f08f0e0030ea36fe8c42fcde166ad27e3 Mon Sep 17 00:00:00 2001
From: Mathias Stearn
Date: Thu, 19 Dec 2024 16:22:04 +0100
Subject: [PATCH 1/6] [libclang/python] Add equality comparison operators fo
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/13424
Here is the relevant pie
https://github.com/DeinAlptraum updated
https://github.com/llvm/llvm-project/pull/130383
>From e8bf3b6f08f0e0030ea36fe8c42fcde166ad27e3 Mon Sep 17 00:00:00 2001
From: Mathias Stearn
Date: Thu, 19 Dec 2024 16:22:04 +0100
Subject: [PATCH 1/5] [libclang/python] Add equality comparison operators fo
hulxv wrote:
@ilovepi done
https://github.com/llvm/llvm-project/pull/131280
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
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/Endilll commented:
@AaronBallman do you have a clue why equality comparison for in-memory files
works differently compared to on-disk files?
https://github.com/llvm/llvm-project/pull/130383
___
cfe-commits mailing list
cfe-commits@l
@@ -16,3 +17,16 @@ def test_file(self):
self.assertEqual(str(file), "t.c")
self.assertEqual(file.name, "t.c")
self.assertEqual(repr(file), "")
+
+def test_file_eq(self):
+path = os.path.join(kInputsDir, "hello.cpp")
+header_path = os.
@@ -16,3 +17,30 @@ def test_file(self):
self.assertEqual(str(file), "t.c")
self.assertEqual(file.name, "t.c")
self.assertEqual(repr(file), "")
+
+def test_file_eq(self):
+path = os.path.join(inputs_dir, "hello.cpp")
+header_path = os.
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `sanitizer-x86_64-linux`
running on `sanitizer-buildbot1` while building `clang,llvm` at step 2
"annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/66/builds/11552
Here is the relevant piece o
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `clang-aarch64-sve-vla`
running on `linaro-g3-04` while building `clang,llvm` at step 6 "build stage 1".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/17/builds/6696
Here is the relevant piece of the
@@ -548,11 +543,28 @@ SystemZTargetLowering::SystemZTargetLowering(const
TargetMachine &TM,
}
// Handle floating-point types.
+ if (!useSoftFloat()) {
+// Promote all f16 operations to float, with some exceptions below.
+for (unsigned Opc = 0; Opc < ISD::BUILTIN_
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`libc-x86_64-debian-dbg-bootstrap-build` running on `libc-x86_64-debian` while
building `clang,llvm` at step 4 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/200/builds/5915
Here is the r
https://github.com/DeinAlptraum updated
https://github.com/llvm/llvm-project/pull/130383
>From e8bf3b6f08f0e0030ea36fe8c42fcde166ad27e3 Mon Sep 17 00:00:00 2001
From: Mathias Stearn
Date: Thu, 19 Dec 2024 16:22:04 +0100
Subject: [PATCH 1/4] [libclang/python] Add equality comparison operators fo
https://github.com/phoebewang closed
https://github.com/llvm/llvm-project/pull/132405
___
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 `ml-opt-rel-x86-64` running
on `ml-opt-rel-x86-64-b1` while building `clang,llvm` at step 5
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/185/builds/15391
Here is the relevant
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib`
running on `gribozavr4` while building `clang,llvm` at step 5
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/60/builds/22772
Here is the relevant piec
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-aarch64-windows`
running on `linaro-armv8-windows-msvc-05` while building `clang,llvm` at step 4
"build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/141/builds/7235
Here is the relevant pie
ilovepi wrote:
Yeah that seems reasonable. You'll still want to check the validity of the
optionals, which could make the logic a bit less nice, but overall I expect the
code to be cleaner than what we have in a lot of places, right now.
https://github.com/llvm/llvm-project/pull/131280
___
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-ppc64le-linux-test-suite` running on `ppc64le-clang-test-suite` while
building `clang,llvm` at step 5 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/95/builds/11073
Here
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-qemu` running on `sanitizer-buildbot3` while building
`clang,llvm` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/139/builds/12429
Here is the relevant p
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `openmp-s390x-linux`
running on `systemz-1` while building `clang,llvm` at step 5 "compile-openmp".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/88/builds/9454
Here is the relevant piece of the buil
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`clang-x86_64-linux-abi-test` running on `sie-linux-worker2` while building
`clang,llvm` at step 6 "build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/8/builds/12857
Here is the rele
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `lldb-aarch64-ubuntu`
running on `linaro-lldb-aarch64-ubuntu` while building `clang,llvm` at step 4
"build".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/59/builds/14729
Here is the relevant piece
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `ml-opt-dev-x86-64` running
on `ml-opt-dev-x86-64-b2` while building `clang,llvm` at step 5
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/137/builds/15621
Here is the relevant
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/8063
Here i
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`ppc64le-lld-multistage-test` running on `ppc64le-lld-multistage-test` while
building `clang,llvm` at step 6 "build-stage1-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/168/builds/10022
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-x86_64-linux-fuzzer` running on `sanitizer-buildbot6` while building
`clang,llvm` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/32/builds/15075
Here is the relevant
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `ml-opt-devrel-x86-64`
running on `ml-opt-devrel-x86-64-b2` while building `clang,llvm` at step 5
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/175/builds/15467
Here is the rel
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder
`sanitizer-aarch64-linux-fuzzer` running on `sanitizer-buildbot11` while
building `clang,llvm` at step 2 "annotate".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/159/builds/18559
Here is the releva
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `premerge-monolithic-linux`
running on `premerge-linux-1` while building `clang,llvm` at step 6
"build-unified-tree".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/153/builds/26572
Here is the relev
https://github.com/svs-quic closed
https://github.com/llvm/llvm-project/pull/132184
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: quic_hchandel
Date: 2025-03-22T07:57:07+05:30
New Revision: 3840f787a21a66686f5d8bf61877d41f3a65f205
URL:
https://github.com/llvm/llvm-project/commit/3840f787a21a66686f5d8bf61877d41f3a65f205
DIFF:
https://github.com/llvm/llvm-project/commit/3840f787a21a66686f5d8bf61877d41f3a65f205.diff
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff 052a4b54a75364f13ea5001bba00691da4d8c239
953bbddc9baa63e8d7649026b08a6cbbbcdeec31 --e
@@ -1502,6 +1659,9 @@ void
RISCVFrameLowering::determineCalleeSaves(MachineFunction &MF,
auto *RVFI = MF.getInfo();
if (RVFI->isPushable(MF) && SavedRegs.test(RISCV::X26))
SavedRegs.set(RISCV::X27);
+
+ // SiFive Preemptible Interrupt Handlers need additional frame en
@@ -1502,6 +1659,9 @@ void
RISCVFrameLowering::determineCalleeSaves(MachineFunction &MF,
auto *RVFI = MF.getInfo();
if (RVFI->isPushable(MF) && SavedRegs.test(RISCV::X26))
SavedRegs.set(RISCV::X27);
+
+ // SiFive Preemptible Interrupt Handlers need additional frame en
https://github.com/erichkeane commented:
How'd you manage to find the right ones? IMO we should be using
include-what-you-use on these to make sure we get it right (if you have
already, disregard this).
Also, can you share before-split/after-split/after-this build time benchmarks?
Does this
1 - 100 of 420 matches
Mail list logo
