From: Dan Kegel <dank@kegel.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: J Decker <d3ck0r@gmail.com>,
Bill Cunningham <bill.cu1234@gmail.com>,
gcc-help@gnu.org
Subject: Re: Simple C compiler
Date: Mon, 4 Oct 2021 12:30:36 -0700 [thread overview]
Message-ID: <CAPF-yOYKw83QEKc5UkVDJF+g5pxZv7Rgrwp4aOKXNhhC+TsMgQ@mail.gmail.com> (raw)
In-Reply-To: <7c0b247e-456c-8707-17b1-59e87db10598@redhat.com>
And then if you're interested in bootstrapping from zero, I think there are
a few tiny c compilers written in Forth!
e.g. maybe
https://groups.google.com/g/comp.lang.forth/c/lBYFfVJ1qhc
- Dan
Vladimir Makarov via Gcc-help <gcc-help@gcc.gnu.org> schrieb am Mo., 4.
Okt. 2021, 12:03:
>
> On 2021-10-04 12:59 a.m., J Decker via Gcc-help wrote:
> > https://github.com/open-watcom/open-watcom-v2/tree/master/bld/cc/c as an
> > alternative there is also openwatcom.
> > or I guess https://github.com/drh/lcc although I've not used this;
> seemed
> > almost like a compiler lacking a linker...
> >
> The following link contains comparison of 9 C compilers on generated
> code performance, compiler speed, and compiler size:
>
>
> https://developers.redhat.com/blog/2021/04/27/the-mir-c-interpreter-and-just-in-time-jit-compiler#how_the_mir_c_compiler_compares_with_other_c_compilers
>
>
>
next prev parent reply other threads:[~2021-10-04 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 3:33 Bill Cunningham
2021-10-04 4:59 ` J Decker
2021-10-04 5:02 ` Dan Kegel
2021-10-04 5:44 ` Anthony de Almeida Lopes
2021-10-04 15:16 ` Dan Kegel
2021-10-04 19:00 ` Vladimir Makarov
2021-10-04 19:30 ` Dan Kegel [this message]
2021-10-04 20:23 ` Anthony de Almeida Lopes
2021-10-04 6:41 ` Jonathan Wakely
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=CAPF-yOYKw83QEKc5UkVDJF+g5pxZv7Rgrwp4aOKXNhhC+TsMgQ@mail.gmail.com \
--to=dank@kegel.com \
--cc=bill.cu1234@gmail.com \
--cc=d3ck0r@gmail.com \
--cc=gcc-help@gnu.org \
--cc=vmakarov@redhat.com \
/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).