From: "Mike Gran" <spk121@yahoo.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: on using 8cc in reproducible bootstrap process
Date: Sun, 18 Jun 2017 07:53:22 -0700 [thread overview]
Message-ID: <20170618145322.GA1568@joshua.dnsalias.com> (raw)
In-Reply-To: <87d1a1csiw.fsf@gnu.org>
On Sun, Jun 18, 2017 at 03:52:23PM +0200, Jan Nieuwenhuizen wrote:
> Hi!
>
> The next leap forward is to compile gcc. I have been looking at
> compiling Tinycc[3]. A couple of weeks ago, rain1 has been working with
> the tcc developers to succeed in compiling gcc using tcc[4].
> which one would you advise, or do you have a better alternative? Should
> I 1) learn about anonymous structs and make Mescc richer, or would you
> like to (help and) take patches for 2)?
For what it is worth, the hacker ragge and the OpenBSD community spent
some time a couple of years ago getting the old PCC Porable C Compiler
back up and running. Because it is based on a much older program, it
may not have these new features with which you are struggling.
http://pcc.ludd.ltu.se/
-Mike Gran
next prev parent reply other threads:[~2017-06-18 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 13:52 on using 8cc in reproducible bootstrap process Jan Nieuwenhuizen
2017-06-18 14:53 ` Mike Gran [this message]
2017-06-18 22:39 ` Rui Ueyama
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=20170618145322.GA1568@joshua.dnsalias.com \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
--cc=janneke@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.
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).