All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rui Salvaterra <rsalvaterra@gmail.com>
To: tobias.karnat@remondis.de, npiggin@gmail.com
Cc: sedat.dilek@gmail.com, x86@kernel.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] x86: enable dead code and data elimination
Date: Thu, 1 Jul 2021 11:00:30 +0100	[thread overview]
Message-ID: <CALjTZvZCi07iVbEOOn8bduueRFLE3MOicWa2WFvxap+zFzpiSg@mail.gmail.com> (raw)
In-Reply-To: <OF02B93D81.2CCB21DA-ONC1258705.0032D3B2-C1258705.00338684@remondis.de>

Hi, Tobias,

On Thu, 1 Jul 2021 at 10:22, <tobias.karnat@remondis.de> wrote:
>
> Hello,
>
> I have found your patch to enable x86 dead code and data elimination on the openwrt-devel mailing list and I wonder if you can sent it upstream to the kernel mailing list?

As I quoted, mine is an adaptation of Nicholas Piggin's original
patch, basically a forward-port to 5.4 (5.10 in my OpenWrt tree [1]).
Since the original proposal has been sent upstream and hasn't been
merged, there are probably good reasons for it (even though it works
perfectly for my use case). Nicholas, any idea on why your original
patch [2] hasn't been merged?

[1] https://github.com/rsalvaterra/openwrt/commit/0082c486b5637dc8e1771e2b9b38b728cb2fa01d
[can be rebased at any time, caveat lector]
[2] https://lore.kernel.org/lkml/20170709031333.29443-1-npiggin@gmail.com/]

> It works for me even combined with the new Clang ThinLTO kernel build. @Sedat you might be interested as well, as I saw your attempt here https://lkml.org/lkml/2021/2/27/181

I haven't tested with Clang, only GCC, but it's nice to know.

Thanks,
Rui

       reply	other threads:[~2021-07-01 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF02B93D81.2CCB21DA-ONC1258705.0032D3B2-C1258705.00338684@remondis.de>
2021-07-01 10:00 ` Rui Salvaterra [this message]
2021-07-02  0:30   ` [PATCH] x86: enable dead code and data elimination Nicholas Piggin

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=CALjTZvZCi07iVbEOOn8bduueRFLE3MOicWa2WFvxap+zFzpiSg@mail.gmail.com \
    --to=rsalvaterra@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=sedat.dilek@gmail.com \
    --cc=tobias.karnat@remondis.de \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.