From: "liuyuntao (F)" <liuyuntao12@huawei.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Fangrui Song <maskray@google.com>,
Russell King <linux@armlinux.org.uk>, Andrew Davis <afd@ti.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jonathan Corbet <corbet@lwn.net>, Mike Rapoport <rppt@kernel.org>,
Rob Herring <robh@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Walleij <linus.walleij@linaro.org>, <llvm@lists.linux.dev>
Subject: Re: [PATCH-next v2] arm32: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION
Date: Mon, 11 Mar 2024 17:39:14 +0800 [thread overview]
Message-ID: <79b87ef0-77c4-45a9-aae2-1754f1b407fe@huawei.com> (raw)
In-Reply-To: <CAMuHMdXKk9S9voKVPvO+xvn1zFW3FnKyVHQGDkC7b9Ynkcnvmw@mail.gmail.com>
On 2024/3/11 17:14, Geert Uytterhoeven wrote:
> Hi Yuntao,
>
> On Sat, Mar 9, 2024 at 2:24 PM liuyuntao (F) <liuyuntao12@huawei.com> wrote:
>> On 2024/3/9 16:20, Arnd Bergmann wrote:
>>> On Sat, Mar 9, 2024, at 07:14, liuyuntao (F) wrote:
>>>> On 2024/3/8 21:15, Arnd Bergmann wrote:
>>>>> On Thu, Mar 7, 2024, at 16:12, Yuntao Liu wrote:
>>>>
>>>> Thanks for the tests, CONFIG_LD_DEAD_CODE_DATA_ELIMINATION and
>>>> CONFIG_TRIM_UNUSED_KSYMS do indeed result in a significant improvement.
>>>> I found that arm32 still doesn't support CONFIG_LTO_CLANG. I've done
>>>> some work on it, but without success. I'd like to learn more about the
>>>> CONFIG_LTO_CLANG patch. Do you have any relevant links?
>>>
>>> I did not try to get it to boot and gave up when I did not see
>>> any size improvement. I think there were previous attempts to
>>> do it elsewhere, which I did not try to find.
>>>
>>
>> I tested this patch, the size improvement was only about one
>> ten-thousandth, and the compilation time had increased by about a quarter,
>> and the kernel did not boot.
>>
>> Strangely, LTO has actually increased the compilation time
>> significantly, which seems contrary to its purpose.
>
> The purpose of LTO is to reduce code size. Doing so requires more
> processing, hence the total build time increases.
>
> Gr{oetje,eeting}s,
>
> Geert
>
Thanks, Geert, I got it.
next prev parent reply other threads:[~2024-03-11 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 15:12 Yuntao Liu
2024-03-08 13:15 ` Arnd Bergmann
2024-03-08 14:27 ` Ard Biesheuvel
2024-03-08 15:37 ` Ard Biesheuvel
2024-03-09 0:01 ` Ard Biesheuvel
2024-03-09 6:46 ` liuyuntao (F)
2024-03-09 6:42 ` liuyuntao (F)
2024-03-09 6:56 ` liuyuntao (F)
2024-03-09 6:14 ` liuyuntao (F)
2024-03-09 8:20 ` Arnd Bergmann
2024-03-09 13:24 ` liuyuntao (F)
2024-03-11 9:14 ` Geert Uytterhoeven
2024-03-11 9:39 ` liuyuntao (F) [this message]
2024-03-11 11:41 ` Arnd Bergmann
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=79b87ef0-77c4-45a9-aae2-1754f1b407fe@huawei.com \
--to=liuyuntao12@huawei.com \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=maskray@google.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®