andcarminati wrote:
> Do you need someone to commit this?
Hi @topperc, if you can commit for me I would appreciate it.
https://github.com/llvm/llvm-project/pull/76432
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
andcarminati wrote:
After approval, commits are now squashed to merge.
https://github.com/llvm/llvm-project/pull/76432
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/andcarminati updated
https://github.com/llvm/llvm-project/pull/76432
>From f697a90f8375a66fb23bbaaefc2e1297e79e063a Mon Sep 17 00:00:00 2001
From: Andreu Carminati
Date: Mon, 15 Jan 2024 15:18:02 +0100
Subject: [PATCH] [Clang][RISCV] Forward --no-relax option to linker for RI
andcarminati wrote:
> Should this also be done in `tools::gnutools::Linker::ConstructJob`?
Addressed with a new commit.
https://github.com/llvm/llvm-project/pull/76432
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-
https://github.com/andcarminati updated
https://github.com/llvm/llvm-project/pull/76432
>From 13648eaf3becc5650924c3399fb1dc1ecb9fa7c7 Mon Sep 17 00:00:00 2001
From: Andreu Carminati
Date: Wed, 27 Dec 2023 09:47:54 +0100
Subject: [PATCH 1/2] [Clang][RISCV] Forward --no-relax option to linker fo
andcarminati wrote:
> The current patch doesn't do what the title implies ("Always emit relocations
> for resolved ").
Sure, I will close this PR because I created another one targeting just this
case: https://github.com/llvm/llvm-project/pull/76432
Regards.
https://github.com/llvm/llvm-proj
https://github.com/andcarminati closed
https://github.com/llvm/llvm-project/pull/73793
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/andcarminati created
https://github.com/llvm/llvm-project/pull/76432
In the case of -mno-relax option. Otherwise, we cannot prevent relaxation if we
split compilation and linking using Clang driver.
One can consider the following use case:
clang [...] -c -o myobject.o (just
andcarminati wrote:
> For the driver BareMetal.cpp change, claiming `-mno-relax` should not be done
> for non-RISCV targets (e.g. AArch32).
Thank you for the update. I updated the PR reverting the backend part and
addressing this issue just for RISC-V.
https://github.com/llvm/llvm-project/pu
https://github.com/andcarminati updated
https://github.com/llvm/llvm-project/pull/73793
>From a7ba3e4e7a84c49e80fe3e05c1a8ca83e7fd8c6e Mon Sep 17 00:00:00 2001
From: Andreu Carminati
Date: Tue, 28 Nov 2023 15:26:49 +0100
Subject: [PATCH 1/2] [RISCV][MC] Always emit relocations for resolved symb
andcarminati wrote:
> As far as I can tell this is pointless. If you want relaxation you need
> R_RISCV_RELAX and R_RISC_ALIGN relocations to be emitted. If you don't want
> relaxation you don't need these. Therefore it seems like all this does is
> emit a whole bunch of useless relocations fo
https://github.com/andcarminati edited
https://github.com/llvm/llvm-project/pull/73793
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
andcarminati wrote:
Hi @topperc , just another idea to solve the problem, mostly to discuss!
Regards.
https://github.com/llvm/llvm-project/pull/73793
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listin
https://github.com/andcarminati created
https://github.com/llvm/llvm-project/pull/73793
If relaxation is not itended, it can be disabled in the linker. Also, we cannot
trust Subtarget features here, because it may be empty in case of LTO codegen,
preventing relaxations.
Also forward --no-rela
14 matches
Mail list logo