public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Chad <chad.page@gmail.com>
To: linux-8086@vger.kernel.org
Subject: ACK ANSI C Compiler
Date: Tue, 16 Aug 2005 20:20:14 -0700	[thread overview]
Message-ID: <f784f526050816202027df0ae2@mail.gmail.com> (raw)
In-Reply-To: <f784f5260508162016217b1073@mail.gmail.com>

I've downloaded and compiled ACK, which took about 4.5minutes on my
p-m notebook - been looking for something like the 'em' targets for a
few days now.  Very nice, and I'm glad it's BSD licensed, too.

Getting ELKS user space apps working will mostly be a library issue -
the convertor shouldn't be a big deal.  In fact, 'file' thinks a.out
is a Linux-8086 executable already.  It looks like we can either port
the bin86 libc or adapt included (minix?) libc to make ELKS system
calls.

Given the way ack works we might have real trouble with the kernel's
inline assembly - we'll have to move as much of the embedded assembly
as possible into assembly files, and make the ack linker deal with
them.  I'd have to look at the minix code to see how things are dealt
with there.

- Chad

OBCrazyTalk: With particularly twisted hacks of em, and a multi-task
interpreter, and some *really* tight and small code, something
ELKSlike might, just might run on a Z80... ;)  It would certainly run
under regular Linux as a process, though.

       reply	other threads:[~2005-08-17  3:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f784f5260508162016217b1073@mail.gmail.com>
2005-08-17  3:20 ` Chad [this message]
2005-08-17  9:37   ` ACK ANSI C Compiler David Given
2005-08-15 16:12 ACK ANSI C compiler David Given
2005-08-15 19:18 ` Hans
2005-08-16 18:49   ` Harry Kalogirou
2005-08-16 23:56     ` 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=f784f526050816202027df0ae2@mail.gmail.com \
    --to=chad.page@gmail.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