public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: palmer@rivosinc.com, conor@kernel.org, guoren@kernel.org,
	linux-riscv@lists.infradead.org, npiggin@gmail.com,
	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 13:13:06 -0700	[thread overview]
Message-ID: <ZJIIUn8Da15neIwI@google.com> (raw)
In-Reply-To: <20230517082936.37563-1-falcon@tinylab.org>

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/

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-06-20 20:13 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 [this message]
2023-06-20 20:17   ` Palmer Dabbelt
2023-06-20 20:22     ` Conor Dooley
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=ZJIIUn8Da15neIwI@google.com \
    --to=ndesaulniers@google.com \
    --cc=conor@kernel.org \
    --cc=falcon@tinylab.org \
    --cc=guoren@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --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