Update of /cvsroot/sbcl/sbcl/src/compiler/ppc
In directory sfp-cvsdas-3.v30.ch3.sourceforge.com:/tmp/cvs-serv26458/src/compiler/ppc
Modified Files:
parms.lisp
Log Message:
1.0.38.10: Support for building on OpenBSD/PPC (patch by Josh Elsasser).
* Dynamic space assignments.
* New Config.* makefile fragment.
* OpenBSD-specific support in ppc-arch.c and ppc-bsd-os.c
* Fixed test suite issues relating to OpenBSD/PPC. This was that the
foreign stack alignment needed setting and that OpenBSD, unlike other
PowerPC targets, requires -fPIC in CFLAGS when building shared objects.
* It turns out that os_context_sp_addr() in ppc-bsd-os.c is only used
when ARCH_HAS_STACK_POINTER is set, which only occurs on x86oid systems
at the present time.
Index: parms.lisp
===================================================================
RCS file: /cvsroot/sbcl/sbcl/src/compiler/ppc/parms.lisp,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- parms.lisp 8 May 2009 20:58:23 -0000 1.35
+++ parms.lisp 23 May 2010 18:23:59 -0000 1.36
@@ -137,6 +137,26 @@
(def!constant dynamic-1-space-start #x67000000)
(def!constant dynamic-1-space-end #x7efff000)))
+;;; Text and data segments start at #x01800000. Range for randomized
+;;; malloc() starts #x20000000 (MAXDSIZ) after end of data seg and
+;;; extends 256 MB. Use 512 - 64 MB for dynamic space so we can run
+;;; under default resource limits.
+;;; FIXME: MAXDSIZ is a kernel parameter, and can vary as high as 1GB.
+;;; These parameters should probably be tested under such a configuration,
+;;; as rare as it might or might not be.
+#!+openbsd
+(progn
+ #!+gencgc
+ (progn
+ (def!constant dynamic-space-start #x4f000000)
+ (def!constant dynamic-space-end #x6afff000))
+ #!-gencgc
+ (progn
+ (def!constant dynamic-0-space-start #x4f000000)
+ (def!constant dynamic-0-space-end #x5cfff000)
+ (def!constant dynamic-1-space-start #x5f000000)
+ (def!constant dynamic-1-space-end #x6cfff000)))
+
#!+darwin
(progn
#!+gencgc
|