ilovepi wrote:
Hi, I think we're seeing some breakage in our CI after this patch.
We see the lldb-api :: tools/lldb-dap/console/TestDAP_console.py test failing.
https://ci.chromium.org/ui/p/fuchsia/builders/toolchain.ci/clang-linux-arm64/b8749666263730294449/overview
```
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH 1/2] [CMAKE] Enable FatLTO as a build option for LLVM
---
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH 1/2] [CMAKE] Enable FatLTO as a build option for LLVM
---
@@ -1251,6 +1253,10 @@ elseif(LLVM_ENABLE_LTO)
endif()
endif()
+if(LLVM_ENABLE_FATLTO AND (FUCHSIA OR UNIX))
+append("-ffat-lto-objects" CMAKE_EXE_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS)
ilovepi wrote:
Dang, I thought I had done that. That's probably
ilovepi wrote:
This speeds up a 2 stage build by about 3 minutes, tests time are still much
closer than expected. Locally I saw a bout a 5-8% speedup to build clang unit
tests, but maybe the unit tests are too small in the overall test regime to
make a difference.
I'll try to collect more
https://github.com/ilovepi ready_for_review
https://github.com/llvm/llvm-project/pull/80480
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/80480
>From 2793f30243a0b93d8a1f52343ab974bf9eef4e03 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 22 Aug 2023 15:24:03 +
Subject: [PATCH] [CMAKE] Enable FatLTO as a build option for LLVM
---
https://github.com/ilovepi approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/79256
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -513,29 +547,125 @@ void RISCV::relocate(uint8_t *loc, const Relocation
, uint64_t val) const {
break;
case R_RISCV_RELAX:
-return; // Ignored (for now)
-
+return;
+ case R_RISCV_TLSDESC:
+// The addend is stored in the second word.
+if
@@ -513,29 +547,125 @@ void RISCV::relocate(uint8_t *loc, const Relocation
, uint64_t val) const {
break;
case R_RISCV_RELAX:
-return; // Ignored (for now)
-
+return;
+ case R_RISCV_TLSDESC:
+// The addend is stored in the second word.
+if
https://github.com/ilovepi approved this pull request.
LGTM on my end. Thanks for all the help on this.
https://github.com/llvm/llvm-project/pull/79239
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
ilovepi wrote:
@topperc Is there anything else you think needs to be done for the code
generation?
https://github.com/llvm/llvm-project/pull/66915
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
@@ -80,6 +80,11 @@ static cl::opt EnableRISCVDeadRegisterElimination(
" them with stores to x0"),
cl::init(true));
+// TODO: This should be controlled by -mtls-dialect=
+cl::opt EnableRISCVTLSDESC("riscv-enable-tlsdesc",
ilovepi wrote:
ilovepi wrote:
As @MaskRay pointed out in #66916, there's a bit too much context in this
review, so please just ignore my earlier question about moving to a stacked PR.
https://github.com/llvm/llvm-project/pull/66915
___
lldb-commits mailing list
https://github.com/ilovepi closed
https://github.com/llvm/llvm-project/pull/66916
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ilovepi wrote:
sounds good. I'll go ahead and close this in favor of
https://github.com/llvm/llvm-project/pull/77516 then, and leave the LLVM PR
alone.
https://github.com/llvm/llvm-project/pull/66916
___
lldb-commits mailing list
ilovepi wrote:
@topperc @MaskRay , do either of you have strong feelings about abandoning this
in favor of https://github.com/llvm/llvm-project/pull/77515? That PR was made
w/ `spr` and should be a bit easier to understand/review (since it won't have
merge or fixup commits) and will make the
ilovepi wrote:
@MaskRay , do you think this is worth abandoning in favor of
https://github.com/llvm/llvm-project/pull/77516? If so, I guess I'd also need
to abandon https://github.com/llvm/llvm-project/pull/66915, which is
unfortunate.
https://github.com/llvm/llvm-project/pull/66916
ilovepi wrote:
> The base branch can be edited if you click "Edit" near the title, which will
> help reveal the lld side changes...
hmm, I was hoping that would work, but the base branch is in my fork. I think
to make it work correctly I'd have to be using the "user" branches in the main
@@ -71,6 +71,18 @@ enum Fixups {
// Used to generate an R_RISCV_ALIGN relocation, which indicates the linker
// should fixup the alignment after linker relaxation.
fixup_riscv_align,
+ // 20-bit fixup corresponding to %tlsdesc_hi(foo) for instructions like
+ // auipc
+
@@ -0,0 +1,44 @@
+# RUN: llvm-mc -filetype=obj -triple riscv32 < %s --defsym RV32=1 |
llvm-objdump -d -M no-aliases - | FileCheck %s --check-prefixes=INST,RV32
+# RUN: llvm-mc -filetype=obj -triple riscv64 < %s | llvm-objdump -d -M
no-aliases - | FileCheck %s
@@ -3,8 +3,8 @@
# Out of range immediates
## simm12
-flh ft1, -2049(a0) # CHECK: :[[@LINE]]:10: error: operand must be a symbol
with %lo/%pcrel_lo/%tprel_lo modifier or an integer in the range [-2048, 2047]
-fsh ft2, 2048(a1) # CHECK: :[[@LINE]]:10: error: operand must be a
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/66916
>From ce9772dd519a62025cf545ded306bf40c75f2924 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 19 Sep 2023 20:53:54 +
Subject: [PATCH 01/17] [RISCV] Support Global Dynamic TLSDESC in the RISC-V
backend
https://github.com/ilovepi updated
https://github.com/llvm/llvm-project/pull/66915
>From ce9772dd519a62025cf545ded306bf40c75f2924 Mon Sep 17 00:00:00 2001
From: Paul Kirth
Date: Tue, 19 Sep 2023 20:53:54 +
Subject: [PATCH 01/15] [RISCV] Support Global Dynamic TLSDESC in the RISC-V
backend
ilovepi wrote:
Indeed. Thank you!
https://github.com/llvm/llvm-project/pull/69493
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ilovepi wrote:
Well, seems like someone broke ToT w/ a compiler error. I'll let you know if
the forward fix fails to address the issue.
https://github.com/llvm/llvm-project/pull/69493
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
ilovepi wrote:
Our next cI run should finish in about 25 minutes, so we'll find out soon.
https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-linux-x64/b8761696932167687409/overview
https://github.com/llvm/llvm-project/pull/69493
ilovepi wrote:
Seems like a mismatch on the diff, so maybe the check is too stringent.
If this will take a while to fix, would you mind reverting until it can be
addressed?
https://github.com/llvm/llvm-project/pull/69493
___
lldb-commits mailing
ilovepi wrote:
Test output:
```
TEST 'Profile-aarch64 :: instrprof-binary-correlate.c'
FAILED
Exit Code: 1
Command Output (stdout):
--
Binary files
ilovepi wrote:
I think our Linux CI is seeing failures related to this patch:
https://luci-milo.appspot.com/ui/p/fuchsia/builders/toolchain.ci/clang-linux-arm64/b8761705440671462977/overview
Profile-aarch64 :: instrprof-binary-correlate.c is failing on that bot for
both x86_64 and arm64.
ilovepi wrote:
I'm unclear on the specifics of the check, but it's probably something we can
adjust if that is the long-term solution.
CC @petrhosek Since he was interested in getting this resolved soon.
https://github.com/llvm/llvm-project/pull/71780
ilovepi wrote:
Fantastic!
https://github.com/llvm/llvm-project/pull/71780
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
ilovepi wrote:
Hi, we're seeing some breakages, similar to the above in our debugger tests
with this patch.
A failing bot can be found here:
https://luci-milo.appspot.com/ui/p/fuchsia/builders/ci/clang_toolchain.ci.core.x64-debug/b8764552260903625809/overview
You can find a fuller discussion
33 matches
Mail list logo