[PATCH v2 0/4] riscv: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION
Nick Desaulniers
ndesaulniers at google.com
Fri Jun 23 10:17:54 PDT 2023
On Thu, Jun 22, 2023 at 11:18:03PM +0000, Nathan Chancellor wrote:
> If you wanted to restrict it to just LD_IS_BFD in arch/riscv/Kconfig,
> that would be fine with me too.
>
> select HAVE_LD_DEAD_CODE_DATA_ELIMINATION if LD_IS_BFD
Hi Jisheng, would you mind sending a v3 with the attached patch applied
on top / at the end of your series?
>
> Nick said he would work on a report for the LLVM side, so as long as
> this issue is handled in some way to avoid regressing LLD builds until
> it is resolved, I don't think there is anything else for the kernel to
> do. We like to have breadcrumbs via issue links, not sure if the report
> will be internal to Google or on LLVM's issue tracker though;
> regardless, we will have to touch this block to add a version check
> later, at which point we can add a link to the fix in LLD.
https://github.com/ClangBuiltLinux/linux/issues/1881
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-riscv-disable-DEAD_CODE_ELIMINATION-for-LLD.patch
Type: text/x-diff
Size: 1643 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20230623/c02cda0f/attachment.bin>
More information about the linux-riscv
mailing list