From: "Arnd Bergmann" <arnd@arndb.de>
To: "Masahiro Yamada" <masahiroy@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, "Han Shen" <shenhan@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Kees Cook" <kees@kernel.org>, "Rong Xu" <xur@google.com>,
"Jann Horn" <jannh@google.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] [RFC, DO NOT APPLY] vmlinux.lds: revert link speed regression
Date: Tue, 21 Jan 2025 08:41:38 +0100 [thread overview]
Message-ID: <fef7c633-5577-4cdf-803a-a1fe10787186@app.fastmail.com> (raw)
In-Reply-To: <CAK7LNASo+wGhpCVhBi+ew1mOtLbSXgx3AiQ6D7RtXO5P=R0EfQ@mail.gmail.com>
On Tue, Jan 21, 2025, at 01:19, Masahiro Yamada wrote:
> On Tue, Jan 21, 2025 at 6:29 AM Arnd Bergmann <arnd@kernel.org> wrote:
>>
>> linux-6.12 linux-6.13
>> ld.lld v20 1.2s 1.2s
>> ld.bfd v2.36 3.2s 5.2s
>> ld.bfd v2.39 59s 388s
>>
>
> Is this problem specific to the BFD linker from binutils?
I only tried the bfd and lld linkers, but I assume it's limited
to the bfd one.
> Did you observe a link speed regression with LLVM=1 build?
No, the ld.lld line above is what I see with LLVM=1, it's
very fast (1.2s) both before and after the change. New
ld.bfd versions were much slower before the regression
for this particular config and got even slower (seven minutes
for each of the three vmlinux link stages).
Arnd
next prev parent reply other threads:[~2025-01-21 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 21:21 [PATCH] [RFC, DO NOT APPLY] vmlinux.lds: revert link speed regression Arnd Bergmann
2025-01-21 0:19 ` Masahiro Yamada
2025-01-21 7:41 ` Arnd Bergmann [this message]
2025-01-21 17:36 ` Rong Xu
2025-01-21 17:45 ` Rong Xu
2025-01-21 21:17 ` Arnd Bergmann
2025-01-22 18:47 ` Rong Xu
2025-01-22 20:29 ` Arnd Bergmann
2025-01-22 22:37 ` Rong Xu
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 23:59 Sam James
2025-01-23 7:33 ` 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=fef7c633-5577-4cdf-803a-a1fe10787186@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=shenhan@google.com \
--cc=xur@google.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