Ian Lynagh wrote:
The attached e-mail seems to be about a problem using a library compiled
with an unregisterised ghc with a registerised ghc. The linking step is
giving many undefined reference to `stg_ap_p_ret's (with various
numbers of 'p's) as well as a few to `GHCziIOBase_zdWIO_entry', and
John Meacham wrote:
On Mon, Mar 13, 2006 at 04:06:59PM +0300, Bulat Ziganshin wrote:
SM I think what you're suggesting is that the runtime should detect the
SM amount of physical memory on the system and auto-tune itself to switch
SM to compacting collection when its residency reaches that
Hello John,
Thursday, March 16, 2006, 4:00:34 AM, you wrote:
i suggest checking of AVAILABLE physical ram, that is perfectly
possible in windows
JM the problem is that available physical ram is wasted ram. any good os
JM will never let there be any available ram because it will fill it up
JM
On Thu, Mar 16, 2006 at 10:05:44AM +, Simon Marlow wrote:
That's right - registerised and unregisterised code are completely
incompatible.
OK, thanks.
Its similar to the situation with profiled and unprofiled code.
But in this case we get a warning:
mismatched interface file ways:
Ian Lynagh wrote:
On Thu, Mar 16, 2006 at 10:05:44AM +, Simon Marlow wrote:
That's right - registerised and unregisterised code are completely
incompatible.
OK, thanks.
Its similar to the situation with profiled and unprofiled code.
But in this case we get a warning:
Hi DUncan,
Thanks for the help.
I've installed a ghc compiler on my Linux box in order to cross-compile and I'm getting the following error. Any ideas?
Thanks,
Mark
/usr/bin/ghc -H16m -O -H32m -istage1/utils
-istage1/basicTypes -istage1/types -istage1/hsSyn
-istage1/prelude -istage1/rename
On Thu, 2006-03-16 at 13:22 -0500, Mark Greenbank wrote:
Hi DUncan,
Thanks for the help.
I've installed a ghc compiler on my Linux box in order to
cross-compile and I'm getting the following error. Any ideas?
You'll have to be very specific about exactly what procedures you're
following.
