From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: Future of ELKS
Date: Sat, 22 May 2004 13:12:15 +0100 [thread overview]
Message-ID: <40AF439F.5030206@cowlark.com> (raw)
In-Reply-To: <40AE357B.9090002@eridani.co.uk>
Michael McConnell wrote:
[...]
> Minix actually uses the Amsterdam Compiler Kit, and is invoked as 'cc'.
So it does --- I could have sworn it used bcc!
Having managed to track down a copy of the ACK
(http://www.cs.vu.nl/vakgroepen/cs/ack.html), I notice that it actually
seems to be a really quite sophisticated cross-platform cross-language
compiler suite. Like a gcc-light.
It supports generating code for the PDP-11, VAX, 68000, SPARC, 8080,
8086, 80386, Z80, Z8000 and the NS16032. It understands Modula-2, K&R C,
Fortran, Pascal, Basic, Occam, and --- get this --- *ANSI C*.
I haven't got it working yet, but has anyone used its ANSI C mode? How
well does it work? Would this be suitable for a self-hosted ANSI C
compiler for the 8086? A brief glance at the license would seem to
indicate it's OSI compatible, but IANAL.
(The other thing I'm wondering about --- since the ACK has been around
for years, and was well-known back in the early days of ELKS, why did
ELKS standardise on bcc rather than the ACK?)
--
dg@cowlark.com --- http://www.cowlark.com
My other account has a real signature.
next prev parent reply other threads:[~2004-05-22 12:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:55 Future of ELKS Miguel Bolanos
2004-05-20 3:39 ` I'm in Void
2004-05-20 14:47 ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15 ` Miguel Bolanos
2004-05-20 15:37 ` Eduardo Pereira Habkost
2004-05-20 16:06 ` Andrey Romanenko
2004-05-21 5:51 ` Dan Olson
2004-05-20 17:30 ` Javier Sedano
2004-05-21 8:32 ` Gábor Lénárt
2004-05-21 14:15 ` Jody
2004-05-24 9:29 ` Gábor Lénárt
2004-05-24 18:20 ` Alan Cox
2004-05-20 23:43 ` David Given
2004-05-21 1:04 ` Stefan de Konink
2004-05-21 3:39 ` Chad Page
2004-05-29 16:58 ` Gregg C Levine
2004-05-21 5:55 ` Dan Olson
2004-05-21 6:08 ` Jody
2004-05-21 13:24 ` Eduardo Pereira Habkost
2004-05-21 16:30 ` David Given
2004-05-21 16:59 ` Michael McConnell
2004-05-22 12:12 ` David Given [this message]
2004-05-22 17:29 ` Chad Page
2004-05-21 18:38 ` Jody
2004-05-22 8:53 ` jb1
2004-05-22 17:00 ` Chad Page
2004-05-24 9:42 ` Gábor Lénárt
2004-05-20 16:54 ` Javier Sedano
2004-05-21 5:50 ` Dan Olson
2004-05-21 9:08 ` Arnaldo Carvalho de Melo
2004-05-21 10:24 ` Alan Cox
2004-05-24 12:20 ` Gábor Lénárt
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano
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=40AF439F.5030206@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.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 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.