ack/plat/linuxppc
George Koehler a585ddf578 Fix parameters of signal handlers for linuxppc.
Linux passes the arguments in registers, but our compiler expects
arguments on the stack.  Signal handlers got garbage instead of the
signal number.  Some handlers, like the one in lang/m2/libm2/sigtrp.c,
need the correct signal number.

I write a "bridge" in PowerPC assembly that moves the arguments to the
stack.  I put the bridge in sigaction(), so I provide a signal() that
calls sigaction().  I remove the *.c glob or wildcard from build.lua,
so linuxppc only compiles its own signal.c, not the other signal.c for
linux386 and linux68k.

My bridge uses sigprocmask(), so I also add sigprocmask().  Because
linux386 and linux68k use globs, they also get sigprocmask().  I sync
the header files so all three Linux platforms declare execve(),
sigprocmask(), and unlink(), but not remove(), because we have
remove() in <stdio.h>.

I am using sigaction.s to test some features that we recently added to
our PowerPC assembler.  These are the "hi16[...]" and "lo16[...]"
syntax, and also the extended names like "beq", "cmpwi", "li", "subi".
2017-01-22 00:52:32 -05:00
..
include Fix parameters of signal handlers for linuxppc. 2017-01-22 00:52:32 -05:00
libsys Fix parameters of signal handlers for linuxppc. 2017-01-22 00:52:32 -05:00
tests Enable tests for linuxppc via qemu-ppc. 2016-11-26 11:56:17 +01:00
boot.s Remove .linenumber and .filename; use hol0 and hol0+4. 2016-09-30 13:40:36 -04:00
build-pkg.lua Mostly add support for the experimental and largely broken linuxppc platform. 2016-09-15 23:12:03 +02:00
build-tools.lua Plats which use aelflod need to depend on it. 2016-11-26 12:07:08 +01:00
descr Fix an issue throughout where B couldn't be built by ackprogram due to symbol 2016-12-29 17:11:53 +00:00
README Check in incomplete Linux PowerPC and M68K work. 2013-05-08 00:48:48 +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