From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: ndesaulniers@google.com, falcon@tinylab.org, guoren@kernel.org,
linux-riscv@lists.infradead.org, npiggin@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
paulburton@kernel.org, vincent.chen@sifive.com,
tim.bird@sony.com, llvm@lists.linux.dev
Subject: Re: [PATCH v3] RISC-V: Enable dead code elimination
Date: Tue, 20 Jun 2023 21:22:43 +0100 [thread overview]
Message-ID: <20230620-hull-boxy-63d71a9c376d@spud> (raw)
In-Reply-To: <mhng-ae249af7-37cc-400c-be0d-c1fa6f75c8ef@palmer-ri-x1c9a>
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
On Tue, Jun 20, 2023 at 01:17:26PM -0700, Palmer Dabbelt wrote:
> On Tue, 20 Jun 2023 13:13:06 PDT (-0700), ndesaulniers@google.com wrote:
> > On Wed, May 17, 2023 at 04:29:36PM +0800, Zhangjin Wu wrote:
> > > Select CONFIG_HAVE_LD_DEAD_CODE_DATA_ELIMINATION for RISC-V, allowing
> > > the user to enable dead code elimination. In order for this to work,
> > > ensure that we keep the alternative table by annotating them with KEEP.
> > >
> >
> > Just cross referencing the report from Palmer against v2; I see orphan
> > section warnings from the linker related to the EFI stub when building
> > allmodconfig with this patch applied.
> >
> > v2: thread for reference.
> > https://lore.kernel.org/linux-riscv/CAKwvOdmsgMN5oQpDLh12D0X-CfQDtHC-EtxHcBnADkhnyitMKQ@mail.gmail.com/
>
> Sorry for replying to the v2, I'm marking that as superseeded in patchwork.
> IIUC it is a real issue on your end too? I'm also not 100% sure about the
> hang, I just let LLD cook for about 10 minutes before I noticed it was still
> running and posted.
Repeating myself for the sake of the archives or w/e, two different
submitters with differing version numbers. The v2 from Jisheng is more
recent than the v3 here from Zhangjin, they agreed in this mail thread
to merge their work.
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-20 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 8:29 [PATCH v3] RISC-V: Enable dead code elimination Zhangjin Wu
2023-05-17 8:41 ` Zhangjin Wu
2023-05-21 2:23 ` guoren
2023-05-21 4:09 ` Bin Meng
2023-05-21 8:48 ` Jisheng Zhang
2023-05-21 8:51 ` Jisheng Zhang
2023-05-21 9:08 ` Jisheng Zhang
2023-05-21 12:41 ` Zhangjin Wu
2023-05-21 13:32 ` Conor Dooley
2023-05-21 14:56 ` Zhangjin Wu
2023-05-21 15:06 ` Conor Dooley
2023-06-20 20:13 ` Nick Desaulniers
2023-06-20 20:17 ` Palmer Dabbelt
2023-06-20 20:22 ` Conor Dooley [this message]
2023-06-20 20:26 ` Nick Desaulniers
2023-06-20 20:41 ` Palmer Dabbelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230620-hull-boxy-63d71a9c376d@spud \
--to=conor@kernel.org \
--cc=falcon@tinylab.org \
--cc=guoren@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=paulburton@kernel.org \
--cc=tim.bird@sony.com \
--cc=vincent.chen@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox