From: Jim Newsome <jim@jimnewsome.net>
To: Maxime Devos <maximedevos@telenet.be>, 56684@debbugs.gnu.org
Cc: Jim Newsome <jnewsome@torproject.org>
Subject: [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58
Date: Thu, 21 Jul 2022 20:33:51 -0500 [thread overview]
Message-ID: <4a7aaaa8-6a0d-e187-381b-0d6cde010f63@jimnewsome.net> (raw)
In-Reply-To: <86c503a4-bd43-6ba8-a307-452c57cf1cfa@telenet.be>
On 7/21/22 19:08, Maxime Devos wrote:
> E.g., you could try going directly from 1.57 to 1.60 without
> intermediate steps. If that's possible, it would be less inefficient to
> compile.
I dug into this a bit.
The Rust bootstrapping docs say to use x.py to download the stage0
compiler. https://rustc-dev-guide.rust-lang.org/building/bootstrapping.html
x.py is a thin wrapper around bootstrap.py:
https://github.com/rust-lang/rust/blob/master/x.py
bootstrap.py decides what compiler to use as stage0 from stage0.json:
https://github.com/rust-lang/rust/blob/master/src/bootstrap/bootstrap.py
1.62.1 was compiled with 1.61.0:
https://github.com/rust-lang/rust/blob/1.62.1/src/stage0.json#L6
1.61.0 was compiled with 1.60.0:
https://github.com/rust-lang/rust/blob/1.61.0/src/stage0.json#L6
1.60.0 was compiled with 1.59.0:
https://github.com/rust-lang/rust/blob/1.60.0/src/stage0.json#L6
1.59.0 was compiled with 1.58.0:
https://github.com/rust-lang/rust/blob/1.59.0/src/stage0.json#L6
1.58.0 was compiled with 1.57.0:
https://github.com/rust-lang/rust/blob/1.58.0/src/stage0.json#L6
So it looks like each release was compiled with a compiler from one
feature-release back. In my patchset, I took the highest patch-version
at each feature-version, since I don't think it makes sense to include
outdated patch-levels, and it should be safe.
Trying to compile a release with an older compiler than it was
originally compiled with seems unlikely to go well. It's not explicitly
stated that it *won't* work, but it seems unlikely that it would, and
would take a lot of time to verify by trial and error.
next prev parent reply other threads:[~2022-07-22 1:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:01 [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58 Jim Newsome
2022-07-21 22:09 ` [bug#56684] [PATCH 2/3] Bump rust 1.58 -> 1.59 Jim Newsome
2022-07-21 22:09 ` [bug#56684] [PATCH 3/3] Bump rust 1.59 -> 1.60 Jim Newsome
2022-07-21 22:14 ` [bug#56684] This is based on the core-updates branch Jim Newsome
2022-07-22 0:08 ` [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58 Maxime Devos
2022-07-22 0:47 ` Jim Newsome
2022-07-22 1:33 ` Jim Newsome [this message]
2022-07-22 9:07 ` Maxime Devos
2022-08-03 6:54 ` [bug#56684] Cannot bootstrap 1.59/1.60 -> 1.62.1 directly kiasoc5 via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a7aaaa8-6a0d-e187-381b-0d6cde010f63@jimnewsome.net \
--to=jim@jimnewsome.net \
--cc=56684@debbugs.gnu.org \
--cc=jnewsome@torproject.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).