From: "Hans" <hans64@ht-lab.com>
To: linux-8086@vger.kernel.org
Subject: Re: ACK ANSI C compiler
Date: Mon, 15 Aug 2005 20:18:49 +0100 [thread overview]
Message-ID: <123f01c5a1ce$32c01070$6502a8c0@dionysus> (raw)
In-Reply-To: 200508151712.57698.dg@cowlark.com
Hi David,
Looks quite interesting and I will check it out when I have some free time.
I am currently using the free Watcom compiler which supports the 8086 and
upwards. I used this compiler (ver 10.0) years ago for a QNX based embedded
system and it was quite good. The 8086 support is OKish, you have to fix
some minor issues but nothing to difficult (like .386 pragma in the assembly
listings). The full source code is available and the user group seems quite
active.
See http://www.openwatcom.org/
To use it for my home grown system I wrote a simple runtime support and some
basic library calls like putch/getch/sprintf/printf. I then wrote a monitor
which included basic I/O interrupt handlers like int21/int10/int16.
By using a tiny model (.com) I avoid the requirement for a locator. I then
translate the binary com file into an intel hex file and upload it to my
board. So far it seems to work OK. When I have some more time I will put all
this stuff on my website.
Does ACK compiles ELKS?
Regards,
Hans.
----- Original Message -----
From: "David Given" <dg@cowlark.com>
To: <linux-8086@vger.kernel.org>
Sent: Monday, August 15, 2005 5:12 PM
Subject: ACK ANSI C compiler
I just thought that people here might be interested to know that I've been
(slowly) working on resurrecting the old ACK compiler toolchain, used by
Minix. It got open sourced a few years ago, under an extremely liberal BSD
license.
http://tack.sourceforge.net/
The reason why I say this is that it is, as far as I know, the only decent
free ANSI C i86 compiler. Tiny and small model only, unfortunately, but
that's all that ELKS requires. It should certainly be better than bcc, but
then a lot of things are...
--
+- David Given --McQ-+
| dg@cowlark.com | Wholesale theft is the sincerest form of flattery.
| (dg@tao-group.com) |
+- www.cowlark.com --+
next prev parent reply other threads:[~2005-08-15 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 16:12 ACK ANSI C compiler David Given
2005-08-15 19:18 ` Hans [this message]
2005-08-16 18:49 ` Harry Kalogirou
2005-08-16 23:56 ` David Given
2005-08-17 14:42 ` [PATCH 1 DMA] Small Error Fixes Nanakos Chrysostomos
2005-08-17 14:44 ` [PATCH 2 DIRECTHD] " Nanakos Chrysostomos
2005-08-17 14:45 ` [PATCH 3 META] " Nanakos Chrysostomos
[not found] <f784f5260508162016217b1073@mail.gmail.com>
2005-08-17 3:20 ` ACK ANSI C Compiler Chad
2005-08-17 9:37 ` David Given
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='123f01c5a1ce$32c01070$6502a8c0@dionysus' \
--to=hans64@ht-lab.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