From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: How to reduce our vulnerability from self-hosted compilers
Date: Fri, 27 Feb 2015 11:49:30 +0100 [thread overview]
Message-ID: <87r3tbsk79.fsf@gnu.org> (raw)
In-Reply-To: <87385s8di2.fsf@netris.org> (Mark H. Weaver's message of "Thu, 26 Feb 2015 18:22:13 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Instead, I would prefer to do something closer to what we do in our core
> bootstrap. We should produce our own bootstrap binaries for each of
> these self-hosted compilers. Like our GCC bootstrap binaries, these
> binaries should be updated very rarely. Then, we should use our own
> bootstrap binaries to build the latest version of any self-hosted
> compiler. In some cases, if the bootstrap binaries are too old to build
> the latest compiler, this might involve multiple steps.
>
> Just as we have recipes to produce bootstrap gcc and binutils, we should
> have recipes to build bootstrap binaries for each self-hosted compiler
> in our system. Each time we produce an updated bootstrap compiler from
> an earlier one, it should be done with our deterministic package such
> that this update step can be independently verified by anyone who wishes
> to do so.
>
> What do you think?
It think it’s a good idea, but I wonder if it is generally applicable.
For instance, ISTR that GHC can be built with a couple of older versions
whereas MIT Scheme may well require itself. What exactly is possible is
not always well-documented and sometimes only known to few people.
Maybe we should try to apply it to some of the cases that we have, and
see how well that works?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-02-27 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 23:22 How to reduce our vulnerability from self-hosted compilers Mark H Weaver
2015-02-27 10:49 ` Ludovic Courtès [this message]
2015-02-27 21:12 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2015-02-27 11:25 Federico Beffa
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=87r3tbsk79.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.