mirror of
https://github.com/Mercury-Language/mercury.git
synced 2025-12-11 11:53:51 +00:00
3321413a9b
Branches: main, 10.04 (where applicable) README.Linux-PPC: README.ThreadScope: RELEASE_NOTES: compiler/options.m: library/calendar.m: library/string.m: Fix spelling and double up words.
74 lines
2.9 KiB
Plaintext
74 lines
2.9 KiB
Plaintext
Mercury should build "out-of-the-box" on Linux for PPC.
|
|
Thanks to Robert A. Abernathy for his help with this port.
|
|
|
|
You will need to use a recent release of gcc which supports global
|
|
register variables for this configuration - gcc 2.8.0 seems to
|
|
work fine, whereas gcc 2.7.2 doesn't. Global register variables
|
|
allow considerably more efficient code to be generated. Another option
|
|
is egcs (see <http://www.cygnus.com/egcs/>).
|
|
|
|
In addition, there are a few things that could be done to "tune" this
|
|
port. Currently the Linux-PPC port does not yet support shared
|
|
libraries, or mprotect()-based stack overflow detection. These
|
|
features are not necessary, but they would of course be nice to have.
|
|
Appended below is some information about what would need to be done to
|
|
add support for these features. Intrepid hackers, read on ;-)
|
|
|
|
----------------------------------------------------------------------
|
|
|
|
> You'll notice that shared libraries aren't supported on this
|
|
> machine yet. The LinuxPPC on the machine is an ELF system
|
|
> and does support shared libs.
|
|
|
|
We don't try to auto-configure shared libraries;
|
|
it's not reliable, since often failures only exhibit
|
|
themselves on large programs, not simple test cases.
|
|
|
|
The code to handle shared libraries might be as simple as just
|
|
patching configure to tell it to assume that they work.
|
|
(The way to do this is shown in the patch appended below.)
|
|
But more likely it will also require a little bit
|
|
of ABI-dependent code in runtime/mercury_goto.h, similar to the
|
|
existing stuff there for __alpha or __sparc.
|
|
|
|
> checking for sys/siginfo.h... no
|
|
> checking for ucontext.h... no
|
|
> checking for sys/ucontext.h... no
|
|
> checking for asm/sigcontext.h... yes
|
|
...
|
|
> checking for `sigaction' field name... sa_handler
|
|
> checking for working `sigcontext_struct'... no
|
|
> checking for `siginfo_t'... no
|
|
|
|
The only other thing missing is stack overflow checking.
|
|
That requires a way of determining the fault address in a signal
|
|
handler, and there's no portable way of doing that.
|
|
We try a bunch of different ways, as shown above.
|
|
The method that is used on x86-linux is asm/sigcontext.h +
|
|
sigcontext_struct. Unfortunately the sigcontext_struct field name
|
|
we use in this method is hard-coded as `cr2', so it won't work on
|
|
PPC-Linux. There may be some way of getting the same information
|
|
on PPC-Linux. Try having a look at /usr/include/*/sigcontext.h.
|
|
|
|
Index: configure.in
|
|
===================================================================
|
|
RCS file: /home/staff/zs/imp/mercury/configure.in,v
|
|
retrieving revision 1.117
|
|
diff -u -u -r1.117 configure.in
|
|
--- configure.in 1997/11/02 12:41:48 1.117
|
|
+++ configure.in 1997/11/22 17:37:07
|
|
@@ -1404,6 +1404,10 @@
|
|
AC_MSG_RESULT(yes)
|
|
EXT_FOR_SHARED_LIB=so
|
|
;;
|
|
+ powerpc-*-linux|powerpc-*-linux-gnu)
|
|
+ AC_MSG_RESULT(yes)
|
|
+ EXT_FOR_SHARED_LIB=so
|
|
+ ;;
|
|
i?86-*-freebsd*)
|
|
# From Cornelis van der Laan <nils@ims.uni-stuttgart.de>
|
|
AC_MSG_RESULT(yes)
|
|
|
|
|
|
|