From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: ACK ANSI C compiler
Date: Wed, 17 Aug 2005 00:56:15 +0100 [thread overview]
Message-ID: <200508170056.16047.dg@cowlark.com> (raw)
In-Reply-To: <1124218178.3131.12.camel@cool>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Tuesday 16 August 2005 19:49, Harry Kalogirou wrote:
> > Does ACK compiles ELKS
>
> No it doesn't. Actually it is going to be a nightmare to make it compile
> under
> ACK. But we probably should face the daemons...
Apart from inline assembly, the biggest problem would most likely be
generating the output binaries: the ACK's linker won't generate output files.
Instead, the linker (it's called led) produces ack.out format files, just
like any other object file, and relies on an architecture specific program to
convert them into executable binaries.
(Given the vast number of different output formats, this is entirely
reasonable, if a little unhelpful.)
For ELKS, you'd probably have to write two binary converters: one for the
kernel, and one for the executables themselves. Neither of these would be
particularly difficult, especially since ELKS binaries are heavily based on
Minix binaries, and of course a Minix converter is supplied.
(arch/i86/cv/cv.c if anyone's interested.)
--
"Curses! Foiled by the chilled dairy treats of righteousness!" --- Earthworm
Jim (evil)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-16 23:56 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
2005-08-16 18:49 ` Harry Kalogirou
2005-08-16 23:56 ` David Given [this message]
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=200508170056.16047.dg@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