All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yash Shinde <Yash.Shinde@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
	Khem Raj <raj.khem@gmail.com>,
	Randy MacLeod <rwmacleod@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [RFC] rust: Upgrade 1.85.1->1.86.0
Date: Fri, 6 Jun 2025 18:20:03 +0530	[thread overview]
Message-ID: <aef59cd9-51f8-4d6e-a43b-39b3514ee4a6@windriver.com> (raw)
In-Reply-To: <105472d8-aa33-4894-b23f-0a4be90367c1@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

Hi,

I cleaned the previously built sources and re-triggered the rust builds.
The earlier data was based on testing with the older builds.
After cleaning and re-building, the build time and FS usage are now 
comparable
to rust v1.85.1.

Here is the new data:

rust version
	Build time(rust-native)
	Build time (rust target)
	FS usage
(build/tmp/work/core2-64-poky-linux/rust/1.86.0/rustc-1.86.0-src/build)
v 1.85.1
	20 mins
	33 mins
	6.3 G
v 1.86
	25 mins
	35 mins
	6.6 G


I have sent the rust v1.86.0 upgrade here:
https://lists.openembedded.org/g/openembedded-core/message/218136


Regards,
Yash

[-- Attachment #2: Type: text/html, Size: 1753 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Yash Shinde" <Yash.Shinde@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
	Khem Raj <raj.khem@gmail.com>,
	Randy MacLeod <rwmacleod@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [RFC] rust: Upgrade 1.85.1->1.86.0
Date: Fri, 06 Jun 2025 05:57:41 -0700	[thread overview]
Message-ID: <aef59cd9-51f8-4d6e-a43b-39b3514ee4a6@windriver.com> (raw)
Message-ID: <20250606125741.LR_VWyaNylMCefOzk6fHg9sLUZ-RmEc2GI7itcsv4FI@z> (raw)
In-Reply-To: <105472d8-aa33-4894-b23f-0a4be90367c1@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Hi,

I cleaned the previously built sources and re-triggered the rust builds.
The earlier data was based on testing with the older builds.
After cleaning and re-building, the build time and FS usage are now comparable
to rust v1.85.1.

Here is the new data:

rust version Build time(rust-native) Build time (rust target) FS usage
(build/tmp/work/core2-64-poky-linux/rust/1.86.0/rustc-1.86.0-src/build) v 1.85.1 20 mins 33 mins 6.3 G v 1.86 25 mins 35 mins 6.6 G

I have sent the rust v1.86.0 upgrade here:
https://lists.openembedded.org/g/openembedded-core/message/218138

Regards,
Yash

[-- Attachment #2: Type: text/html, Size: 1178 bytes --]

  parent reply	other threads:[~2025-06-06 12:50 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
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 [this message]
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=aef59cd9-51f8-4d6e-a43b-39b3514ee4a6@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 \
    --cc=rwmacleod@gmail.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 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.