From: "Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov>
To: "info-gnu@gnu.org" <info-gnu@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"rb-general@lists.reproducible-builds.org"
<rb-general@lists.reproducible-builds.org>,
"bootstrappable@freelists.org" <bootstrappable@freelists.org>
Subject: Stage0 Release 0.4.0, M2-Planet Release 1.5.0 and mescc-tools-seed Release 1.2
Date: Mon, 3 Feb 2020 10:38:41 +0000 [thread overview]
Message-ID: <DM6PR09MB595743A3BA12720997D780FCC6000@DM6PR09MB5957.namprd09.prod.outlook.com> (raw)
Today I am pleased to announce the following releases:
https://savannah.nongnu.org/projects/stage0/
https://github.com/oriansj/stage0
In stage0 we have gained hand written (in assembly) C compilers for:
AMD64 :: cc_amd64.s
Knight :: cc_knight-native.s and cc_knight-posix.s
ARMv7l :: cc_armv7l.s
AArch64 :: cc_aarch64.s
Along with C High level prototypes for all of them
(All of the above was completed in a 4 hour speed run)
https://github.com/oriansj/M2-Planet
In M2-Planet we gained more posix primitives and thanks to recent fuzzing have dropped a considerable number of possible segfaults.
Knight-native gained support for large binaries (2GB)
Oh and to bury the lead a bit.
Deesix single handedly ported AArch64 support into M2-Planet! (up next RISC-V [32 and 64bit])
https://github.com/oriansj/mescc-tools-seed
In mescc-tools-seed we eliminated all binaries (not that there was much anyway)
So you'll have to clone https://github.com/oriansj/bootstrap-seeds if you want a generated 357byte hex0 binary
- Jeremiah
next reply other threads:[~2020-02-03 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 10:38 Orians, Jeremiah (DTMB) [this message]
2020-02-04 13:14 ` Stage0 Release 0.4.0, M2-Planet Release 1.5.0 and mescc-tools-seed Release 1.2 Efraim Flashner
2020-02-04 13:42 ` Orians, Jeremiah (DTMB)
2020-02-04 17:22 ` Jan Nieuwenhuizen
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=DM6PR09MB595743A3BA12720997D780FCC6000@DM6PR09MB5957.namprd09.prod.outlook.com \
--to=oriansj@michigan.gov \
--cc=bootstrappable@freelists.org \
--cc=guix-devel@gnu.org \
--cc=info-gnu@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.
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).