aeb8ed53e4
Also change UINT32_MAX in <stdint.h> from 4294967295 to 4294967295U. The U suffix avoids a promotion to long or unsigned long if it would fit in unsigned int. Define _EM_LLSIZE but not EM_LLSIZE. The leading underscore is a convention for such macros. If code always uses _EM_LLSIZE, we will never need to add EM_LLSIZE. The flag -D_EM_LLSIZE={q} is in plat/linux386/descr, not lib/descr/fe, so platforms without long long don't define _EM_LLSIZE. <stdint.h> doesn't keep the old code for _EM_LSIZE == 8, because I change it to _EM_LLSIZE == 8. No platform had _EM_LSIZE == 8, and the old limits like INT64_MAX were wrong. |
||
---|---|---|
.. | ||
include | ||
libsys | ||
tests | ||
boot.s | ||
build-pkg.lua | ||
build-tools.lua | ||
descr | ||
README |
# $Source$ # $State$ # $Revision$ 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