All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Porting to different architectures
Date: Mon, 31 Jul 2006 17:03:32 +0100	[thread overview]
Message-ID: <44CE29D4.4040008@cowlark.com> (raw)
In-Reply-To: <44CE232F.4080606@wallman.org.uk>

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

Richard Wallman wrote:
[...]
> I've been working on getting it to work with GCC for 386+ processors,
> and it's not pretty. GCC support would make porting a lot easier, given
> the number of processor targets it supports.

Is anyone interested in hearing that I've nearly managed to get the ACK
(Minix' native compiler) into a usable state? It supports ANSI C, K&R C,
Pascal, Modula-2, Occam and Basic for a bunch of different
architectures, which include i80, i86 and i386. The code isn't as good
as what gcc produces, but it is a tiny fraction of the size, and it's
also BSD licensed.

I'm still working on the syscall libraries required for the ACK's own
built-in libc, but if you didn't want to use that, it's more or less
there now.

(It should also be reasonably easy to retarget --- compared to gcc, at
least. Does the 65C265 have a compiler?)

-- 
+- David Given --McQ-+ "You cannot truly appreciate _Atlas Shrugged_
|  dg@cowlark.com    | until you have read it in the original Klingon."
| (dg@tao-group.com) | --- Sea Wasp on r.a.sf.w
+- www.cowlark.com --+


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

  reply	other threads:[~2006-07-31 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans
2006-07-31 15:35   ` Richard Wallman
2006-07-31 16:03     ` David Given [this message]
2006-07-31 16:24       ` Richard Wallman
2006-07-31 16:32         ` David Given
2006-07-31 17:42     ` Jody Bruchon
2006-08-01  6:49       ` Richard Wallman
2006-08-01 17:15         ` Segin
2006-07-31 19:47     ` Javier Sedano
2006-07-31 21:44       ` Alan Cox
2006-08-01  2:57         ` Tom McCabe
2006-08-01  5:27           ` Jody Bruchon
2006-08-01 13:22             ` Alan Cox
2006-08-01 14:41               ` Vikas N Kumar
2006-08-01 15:28                 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29   ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43     ` Petr Koval
2006-07-31 15:51     ` Petr Koval
2006-08-02 13:24       ` Mattia Jona-Lasinio

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=44CE29D4.4040008@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.