public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: ELKS CVS imported into Git with all history
Date: Wed, 08 Feb 2012 00:15:04 +0000	[thread overview]
Message-ID: <4F31BE88.7010201@cowlark.com> (raw)
In-Reply-To: <4F3199D9.5000304@jodybruchon.com>

[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]

On 07/02/12 21:38, Jody Bruchon wrote:

> Additionally, I'd like to assemble a list of open-source compilers that
> can build for 8086 and either are targeted to other 16-bit CPUs or can
> be relatively easily retargeted (I use that term loosely with compilers.
> If anyone has suggestions for alternative compilers, please email me
> with them, and I'll build a list and examine the merits of each against
> the others.

I 'maintain' the Amsterdam Compiler Kit, the compiler written by Andy
Tanenbaum and Ceriel Jacobs. It's here:

http://tack.sourceforge.net

It compiles, poorly, for a bunch of different architectures; it contains
 its own runtime libraries and toolchains and is a turnkey solution to
producing (static) binaries for small devices. Plus it supports a
variety of different languages, including K&R C, ANSI C, Pascal and
Modula-2.

Alas, there's no 6809 support other than an assembler. (And possibly
linker support, too.)

(The scare quotes around 'maintain' are because I haven't touched it for
ages --- the compiler architecture is interesting but painfully limited
and rather less useful than I thought it would be, and there's very
nearly no interest. But it *is* a working compiler.)

-- 
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2012-02-08  0:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  5:14 ELKS CVS imported into Git with all history Jody
2012-02-06 11:48 ` howto start kqt4at5v
     [not found]   ` <4F30291D.5030908@telia.com>
2012-02-07 12:08     ` kqt4at5v
2012-02-07 14:06       ` Jody
2012-02-07 14:46         ` David Given
     [not found]           ` <CAMKR1ysKw2SaGObU38Gv8Sh1GMkxjRRkc7wwNPvNDKAa7Z=0pw@mail.gmail.com>
2012-02-07 16:29             ` David Given
2012-02-07 18:48         ` kqt4at5v
2012-02-07 20:02         ` kqt4at5v
2012-02-07 14:49 ` ELKS CVS imported into Git with all history Harley Laue
2012-02-07 21:38   ` Jody Bruchon
2012-02-08  0:15     ` David Given [this message]
2012-02-08  2:56     ` Kirn Gill
2012-02-08 21:28     ` Juan Perez-Sanchez
2012-02-09  2:53     ` Harley Laue

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=4F31BE88.7010201@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox