core.ops ate my (miniscule) RAM

[David Chan]

Hi,

I'm using a Pentium 200 (well, Cyrix actually) with 32 MB of RAM, gcc
2.95.4, linux 2.2.17 and parrot out of CVS. Without swap, when I do
"make", compiling core_ops_cg.c fails due to lack of memory. Which is
unsurprising, as it is pretty big. It works if I use a 70 MB swap
partition.

Should parrot need this much memory to compile? Would it be good to
split the core_ops*.c files into pieces? Or am I living in a fantasy
world to think this is at all useful?

David
--
$_=".--- ..- ... - .- -. --- - .... . .-. .--. . .-. .-.. .... .- -.-.".
" -.- . .-.\n";s!([.-]+) ?!$_=$1;y/-./10/;$_=chr(-1+ord pack"B*","01".0 x(5
-length)."1$_");y/DWYKAQMOCVLSFENU\\IGBHPJXZ[~nfb`_ow{}/a-z0-9/;$_!ge;print

[Brent Dax]

David Chan:
# I'm using a Pentium 200 (well, Cyrix actually) with 32 MB of
# RAM, gcc 2.95.4, linux 2.2.17 and parrot out of CVS. Without
# swap, when I do "make", compiling core_ops_cg.c fails due to
# lack of memory. Which is unsurprising, as it is pretty big.
# It works if I use a 70 MB swap partition.

The computed-goto core (in core_ops_cg.c) can't be split.

--Brent Dax <bren...@cpan.org>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)

Wire telegraph is a kind of a very, very long cat. You pull his tail in
New York and his head is meowing in Los Angeles. And radio operates
exactly the same way. The only difference is that there is no cat.
--Albert Einstein (explaining radio)

[Nicholas Clark]

On Wed, Oct 02, 2002 at 08:26:20AM -0700, Brent Dax wrote:
> David Chan:
> # I'm using a Pentium 200 (well, Cyrix actually) with 32 MB of
> # RAM, gcc 2.95.4, linux 2.2.17 and parrot out of CVS. Without
> # swap, when I do "make", compiling core_ops_cg.c fails due to
> # lack of memory. Which is unsurprising, as it is pretty big.
> # It works if I use a 70 MB swap partition.
>
> The computed-goto core (in core_ops_cg.c) can't be split.

But as Brent explained to me in an e-mail a while back
( http://archive.develooper.com/perl6-i...@perl.org/msg11197.html )

You can pass Configure a flag to disable computed goto (--cgoto=0)

ie run Configure.pm as

./Configure.pl --cgoto=0

You don't need to build the computed goto core to have a working parrot.
There are other (slightly slower at run time) cores it also builds.

Nicholas Clark