From: Andy Wingo <wingo@igalia.com>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: rust work in progress conflicts
Date: Fri, 06 May 2016 11:05:27 +0200 [thread overview]
Message-ID: <878tznftew.fsf@igalia.com> (raw)
In-Reply-To: <1462459586.3181019.599022233.5F377A74@webmail.messagingengine.com> (Alex Griffin's message of "Thu, 05 May 2016 09:46:26 -0500")
On Thu 05 May 2016 16:46, Alex Griffin <a@ajgrf.com> writes:
> On Thu, May 5, 2016, at 08:35 AM, Ludovic Courtès wrote:
>>
>> Yeah it’s OK to do it in the order: write the package bootstrapped from
>> the binary blob, and then work on bootstrapping it from OCaml.
>
> I do not think that bootstrapping Rust from OCaml is a practical goal.
> When you guys have talked about bootstrapping gcc from an older version,
> I don't think it has involved even a dozen gcc versions, let alone 319!
> It's a huge amount of work, to the point where it may even be easier to
> write a new Rust compiler from scratch. Even if it succeeded, it would
> take over a full week to build the current Rust release, meanwhile OCaml
> requires a blob anyway.
>
> I'd love to be proven wrong, but in any case I don't think it's
> reasonable to expect Jelle Licht to take on this project just because he
> assumed the mantle of rustc packager.
I agree with Alex FWIW.
Also FWIW, I think in the future a sane bootstrap is probably more
likely from a MIR interpreter (something like this but implemented from
another language: https://github.com/tsion/miri/tree/master/src).
But given that even OCaml includes a binary blob (!), I don't think that
we can practically require bootstrapped language implementations to
bootstrap all the way.
Andy
next prev parent reply other threads:[~2016-05-06 9:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:45 LLVM: "FileCheck" is missing Danny Milosavljevic
2016-03-25 21:58 ` Nils Gillmann
2016-03-25 22:06 ` rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing) Nils Gillmann
2016-05-04 10:34 ` Jelle Licht
2016-05-05 13:35 ` rust work in progress conflicts Ludovic Courtès
2016-05-05 14:46 ` Alex Griffin
2016-05-06 9:05 ` Andy Wingo [this message]
2016-05-06 9:15 ` Andy Wingo
2016-05-06 9:59 ` Ludovic Courtès
2016-05-05 15:06 ` ng0
2016-07-28 8:28 ` ng0
2016-07-28 18:31 ` Eric Le Bihan
2016-07-29 9:03 ` Andreas Enge
2016-07-29 11:40 ` Vincent Legoll
2016-07-29 14:37 ` ng0
2016-07-30 10:04 ` Eric Le Bihan
2016-07-29 15:16 ` Rust Ludovic Courtès
2016-07-29 15:34 ` Rust Alex Griffin
2016-07-29 16:08 ` Rust Jelle Licht
2016-07-30 13:34 ` Rust Ludovic Courtès
2016-07-30 17:57 ` Rust Pjotr Prins
2016-07-30 11:01 ` Rust Eric Le Bihan
2016-07-30 13:44 ` Rust Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 9:46 rust work in progress conflicts David Craven
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=878tznftew.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=a@ajgrf.com \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.