From: Arne Babenhauserheide <arne_bab@web.de>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: gcc@gcc.gnu.org, info-gnu@gnu.org, bootstrappable@freelists.org,
rb-general@lists.reproducible-builds.org, guix-devel@gnu.org,
guile-user@gnu.org
Subject: Re: GNU Mes 0.19 released
Date: Mon, 17 Dec 2018 00:20:58 +0100 [thread overview]
Message-ID: <877eg92h45.fsf@web.de> (raw)
In-Reply-To: <877eg91av2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Mes has now brought the Reduced Binary Seed bootstrap to Guix (bootstrap
> a GNU/Linux system without binary GNU toolchain or equivalent)
That’s awesome!
> This release introduces strings as byte-array, hash-tables and native
> structs. While that does increase the footprint somewhat, it fixes
> our performance issue; tinycc is now compiled in ~8min (WAS: ~1h30).
Wow! I did not expect such a huge difference.
> Next targets:
>
> - translate mes.c into unsnarfed mes.M2
> - use Gash to remove bash, coreutils&co, grep, sed, tar from the Guix
> bootstrap binaries
Is this about configure+make?
> - bootstrap gcc-3.x or 4.x directly, drop initial gcc-2.95.3 target?
Do you have a document showing the bootstrap path — ideally in graph
form, i.e. with plantuml activity diagram?
http://plantuml.com/activity-diagram-legacy
> - Debian?
- Gentoo?
> - ARM, the Hurd?
The Hurd would be nice!
Thank you for your great work!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2018-12-16 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 20:21 GNU Mes 0.19 released Jan Nieuwenhuizen
2018-12-16 23:20 ` Arne Babenhauserheide [this message]
2018-12-17 11:19 ` [bootstrappable] " Ricardo Wurmus
2018-12-17 20:56 ` Arne Babenhauserheide
2018-12-17 21:37 ` Jan Nieuwenhuizen
2018-12-17 23:34 ` Arne Babenhauserheide
2018-12-17 12:08 ` Jérémy Korwin-Zmijowski
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877eg92h45.fsf@web.de \
--to=arne_bab@web.de \
--cc=bootstrappable@freelists.org \
--cc=gcc@gcc.gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=info-gnu@gnu.org \
--cc=janneke@gnu.org \
--cc=rb-general@lists.reproducible-builds.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.
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).