From: Nathan Chancellor <nathan@kernel.org>
To: Rong Xu <xur@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Miguel Ojeda <ojeda@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alice Ryhl <aliceryhl@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Rafael Aquini <aquini@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Stafford Horne <shorne@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Piotr Gorski <piotrgorski@cachyos.org>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Teresa Johnson <tejohnson@google.com>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v11 3/3] kbuild: distributed build support for Clang ThinLTO
Date: Fri, 29 May 2026 11:47:14 -0700 [thread overview]
Message-ID: <20260529184714.GA2059596@ax162> (raw)
In-Reply-To: <CAF1bQ=SOG3qr4K3h=SBgM=e42RmV6WjOfyMOmi_qBOpYMoVaEQ@mail.gmail.com>
On Thu, May 28, 2026 at 04:09:10PM -0700, Rong Xu wrote:
> On Thu, May 28, 2026 at 3:07 PM Nathan Chancellor <nathan@kernel.org> wrote:
> > Sashiko has another comment as well.
> >
> > https://sashiko.dev/#/patchset/26003?part=3
>
> Are you referring to KBUILD_VMLINUX_OBJS and KBUILD_VMLINUX_LIBS part?
Yes.
> I'm not sure if that's true: in my build, KBUILD_VMLINUX_OBJS includes
> lib/lib.a etc.
> In line 1296 of Makefile:
> KBUILD_VMLINUX_OBJS := built-in.a $(patsubst %/, %/lib.a, $(filter %/,
> $(libs-y)))
>
> We can see native objects in lib/*.
> % find lib -name '*.thinlto-native.o' |wc
> 204 204 7104
Ah yes, I should have double checked that before brining it up.
KBUILD_VMLINUX_LIBS would contain archives such as
drivers/firmware/efi/libstub/lib.a, which we obviously do not want to
process into vmlinux.a, so I think that comment is obviously invalid.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-05-29 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 20:39 [PATCH v11 0/3] kbuild: distributed build support for Clang ThinLTO xur
2026-05-28 20:39 ` [PATCH v11 1/3] kbuild: move vmlinux.a build rule to scripts/Makefile.vmlinux_a xur
2026-05-28 20:39 ` [PATCH v11 2/3] kbuild: change --thin back to 'T' in $(AR) xur
2026-05-28 20:39 ` [PATCH v11 3/3] kbuild: distributed build support for Clang ThinLTO xur
2026-05-28 22:07 ` Nathan Chancellor
2026-05-28 23:09 ` Rong Xu
2026-05-29 18:47 ` Nathan Chancellor [this message]
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=20260529184714.GA2059596@ax162 \
--to=nathan@kernel.org \
--cc=aliceryhl@google.com \
--cc=aquini@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=morbo@google.com \
--cc=mpe@ellerman.id.au \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=ojeda@kernel.org \
--cc=piotrgorski@cachyos.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=shorne@gmail.com \
--cc=tejohnson@google.com \
--cc=tglx@linutronix.de \
--cc=venkat88@linux.ibm.com \
--cc=xur@google.com \
--cc=yonghong.song@linux.dev \
/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