20a4d401d0
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. |
||
---|---|---|
.. | ||
emu | ||
include | ||
libsys | ||
tests | ||
boot.s | ||
build-pkg.lua | ||
build-tools.lua | ||
descr | ||
README |
# $Source$ # $State$ # $Revision$ The pc86 platform ================= pc86 is an i86-based BSP that produces bootable floppy disk images that can be run on most PCs. It is intended to be quick and dirty rather than actually useful, although it may come in handy for hardware test purposes, boot loaders, and the like. The code runs in TINY mode, where CS, DS and SS all share the same segment. This means that there's not very much memory available. It would be very easy to change it to run in SMALL mode, where CS occupies one segment and DS and SS another, which would give 64kB for nearly all programs; I just haven't done it. IEEE floating point is available, but requires an FPU. This port only implements a very limited set of syscalls --- and most of those are stubs required to make the demo apps link. File descriptors 0, 1 and 2 represent the console. All reads block. There's enough TTY emulation to allow \n conversion and local echo (but it can't be turned off). Console output is echoed to the serial port (without any setup). This is used by qemu for running tests. Example command line ==================== ack -mpc86 -O -o pc86.img examples/paranoia.c The file pc86.img can then be copied onto a floppy and booted, or run via qemu or somesuch emulator. David Given dg@cowlark.com