From: Yash Shinde <Yash.Shinde@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
"MacLeod, Randy" <randy.macleod@windriver.com>,
"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [RFC] rust: Upgrade 1.85.1->1.86.0
Date: Mon, 2 Jun 2025 16:45:20 +0530 [thread overview]
Message-ID: <36532bcc-c9dd-430a-a932-ec81e9270f19@windriver.com> (raw)
In-Reply-To: <CANNYZj-Pa_jhraEz7qAHoDXLxfg-7ztH4UhdRPXirw6biZGWEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On 30-05-2025 18:45, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Fri, 30 May 2025 at 14:42, Yash Shinde<Yash.Shinde@windriver.com> wrote:
>
>> As Khem mentioned, setting lld = false in config.toml doesn't build LLD.
>> Furthermore, using "use-lld = false" ensures that LLD is not used as the
>> default linker,
>> causing the build to fall back to the system's default linker. This
>> restores the earlier behavior.
>> Also, the package QA error for rust-lld is not seen with this.
> What about build times though? Are they back to what they were?
>
The build time differences on my machine are as follows:
rust version
rust upstream builds
rust-native (yocto build)
rust target (yocto build)
v1.85.1
10 mins
20 mins
33 mins
v1.86.0
22 mins (with "lld" and "use-lld" set to "false")
30 mins (with default settings i.e lld = true)
31 mins (with "lld" and
"use-lld" set to "false") 43 mins (with "lld" and
"use-lld" set to "false")
Note: The machine being used is a shared resource and fairly busy. Build
times may differ due to other user's builds.
The FS usage is as follows:
Rust version
rust upstream builds
Yocto rust builds
(build/tmp/work/core2-64-poky-linux/rust/1.86.0/rustc-1.86.0-src/build)
v1.85.1
4.6 G
6.3 G
v1.86.0
15 G
8.8 G
The latest rust v1.86.0 upgrade changes are available at:
https://git.yoctoproject.org/poky-contrib/log/?h=harish/rust_1.86.0_v2
Regards,
Yash
> Alex
[-- Attachment #2: Type: text/html, Size: 4163 bytes --]
next prev parent reply other threads:[~2025-06-02 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 16:22 [RFC] rust: Upgrade 1.85.1->1.86.0 Yash Shinde
2025-05-27 12:47 ` [OE-core] " Alexander Kanavin
[not found] ` <184363192F51E64D.13855@lists.openembedded.org>
2025-05-27 13:40 ` Alexander Kanavin
2025-05-27 14:40 ` Yash Shinde
2025-05-27 14:06 ` Alexander Kanavin
2025-05-27 14:42 ` Yash Shinde
2025-05-27 16:26 ` Alexander Kanavin
2025-05-30 2:32 ` Khem Raj
2025-05-30 12:42 ` Yash Shinde
2025-05-30 13:15 ` Alexander Kanavin
2025-06-02 11:15 ` Yash Shinde [this message]
2025-06-02 13:03 ` Randy MacLeod
2025-06-02 17:09 ` Khem Raj
2025-06-03 18:31 ` Randy MacLeod
2025-06-03 20:56 ` Khem Raj
2025-06-06 12:50 ` Yash Shinde
2025-06-06 12:57 ` Yash Shinde
2025-06-03 19:14 ` Randy MacLeod
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=36532bcc-c9dd-430a-a932-ec81e9270f19@windriver.com \
--to=yash.shinde@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.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