ack/plat/linux68k
George Koehler 20a4d401d0 Add first long-long test for linux386.
Skip the long-long test set on other platforms, because they don't
have long long.  Each platform would need to implement 8-byte
operations like `adi 8` in its code generator, and set long long to
8 bytes in its descr file.

The first test is for negation, addition, and subtraction.  It also
requires comparison for equality.
2019-09-05 13:13:02 -04:00
..
emu Remove extra #include <stdio.h> to fix uint 2018-06-10 16:24:35 -04:00
include All the Linux include directories are the same, so common them all out into a 2018-06-24 19:57:43 +02:00
libsys All the Linux include directories are the same, so common them all out into a 2018-06-24 19:57:43 +02:00
tests Add first long-long test for linux386. 2019-09-05 13:13:02 -04:00
boot.s Ensure that procedure labels are word aligned (required by the EM spec). 2019-06-17 22:26:31 +02:00
build-pkg.lua linux68k builds now. 2016-08-14 11:34:18 +02:00
build-tools.lua Plats which use aelflod need to depend on it. 2016-11-26 12:07:08 +01:00
descr All the Linux include directories are the same, so common them all out into a 2018-06-24 19:57:43 +02:00
README Add missing linux68k platform and liblinux support library. 2013-05-09 00:56:10 +01:00

# $Source: /cvsroot/tack/Ack/plat/linux386/README,v $
# $State: Exp $
# $Revision: 1.2 $


The linux386 platform
=====================

linux386 is an i386-based BSP that produces Linux ELF executables.

This port only implements a very limited number of system calls; basically,
just enough to make the demo apps run. Adding more is easy, but there are some
subtleties that require more thought. The port should be considered only in
proof-of-concept stage right now.

Important note: you *can't* link access ELF shared libraries from these
executables. In other words, you have to all your work from inside ACK.

IEEE floating point is available, but requires an FPU.

The executables are generated with aelfslod and are extremely simple; there's
one rwx ELF section which contains all the application's code and data. This
is not optimal, but it does work.


Bugs
====

isatty() is a stub and always returns 0.


Example command line
====================

ack -mlinux386 -O -o linux386.exe examples/paranoia.c

The file linux386.exe can then be run on a i386 Linux machine (or on an
emulation thereof).


David Given
dg@cowlark.com