From: David Given <dg@cowlark.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Regarding the Future of ELKS
Date: Sun, 06 May 2007 13:54:14 +0100 [thread overview]
Message-ID: <463DCFF6.9020005@cowlark.com> (raw)
In-Reply-To: <463D00EF.9060901@alaska.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Royce Williams wrote:
>[...]
> http://pcemu.sourceforge.net/
PCEMU is mine, kinda; it's moderately accurate (will run DOS and most apps),
but the thing that makes it really useful for me is that it's got a largely
undocumented built-in debugger of about the same level of functionality as
DEBUG.COM. I usually find it easier to use this for machine-code level
debugging than struggling with gdb and qemu.
I did try ELKS on it a while ago and it did run, although there were some
timing loop issues.
...incidentally, since then I have also been working on the Amsterdam Compiler
Kit suite of compilers, and recently did a release; it the latest 6.0 now
contains support for 8086, 80386 and 8080 code generators. It's also been
hugely cleaned up --- I could add support for ELKS executables more or less
trivially, if anyone wants it (and can point me at the spec); the only bit
that's the slightest bit tricky is the syscall library. It supports genuine
ANSI C, and also Pascal and Modula 2 (also Occam 1 and Basic, should anyone
care)...
http://tack.sourceforge.net
- --
┌── dg@cowlark.com ─── http://www.cowlark.com ───────────────────
│ "Parents let children ride bicycles on the street. But parents do not
│ allow children to hear vulgar words. Therefore we can deduce that cursing
│ is more dangerous than being hit by a car." --- Scott Adams
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGPc/2f9E0noFvlzgRAjAQAJ48kOIOiAOTsphuTnfR81zn6lVTvwCgozpp
a1UGFUphNDEN1zgOgUHJZd8=
=AHyt
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-05-06 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 18:58 Regarding the Future of ELKS Jody
2007-05-05 22:10 ` Royce Williams
2007-05-05 22:14 ` NOTICE REGARDING SENDING MAIL TO THE ELKS LIST Jody
2007-05-06 10:08 ` Regarding the Future of ELKS Gábor Lénárt
2007-05-06 12:54 ` David Given [this message]
2007-05-06 13:46 ` Alan Cox
2007-05-06 17:13 ` David Given
2007-05-06 18:37 ` Alan Cox
2007-05-05 22:25 ` Mario Frasca
2007-05-06 9:23 ` Hans
2007-05-06 17:46 ` Luis A. Montes
2007-05-07 12:19 ` Mario Urban
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 18:12 chriscureau
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=463DCFF6.9020005@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