Saturday July 31, 2004
10:29 AM
Parrot becoming a rhinocerous
Is Parrot becoming a rhinocerous, an elephant, a dragon or a dinossaur? I just can't compile it in my 1Ghz Pentium 3. It stucks in the same file for more than 30 minutes. I do not know how much more, as I interrupted it.
The file (at least, one of them) is ops/core_ops_cg.c. On my system, it takes up 380Kb of disk space. It does not contain so much comments like that... as I think it is a generated file. But, can't we divide and conquer?
Computed gotos (Score:1)
You're swapping... (Score:1)
core_ops_cg.c is, as noted, the computed goto core. To make this work, all of parrot's op functions are mashed together into a single function. It's huge, it gives GCC fits, and it takes a goodly chunk of memory to go. If you've less than 256M free, that file'll take forever to compile. (Even longer with optimizations turned on, because gcc usually gets halfway through it, gi
Re:You're swapping... (Score:1)
Re:You're swapping... (Score:1)
Parrot's got several generated cores. The computed goto core's the fastest, but it has others. The --cgoto=0 disables the computed goto core, which'll make things build faster, and parrot will still run, albeit a bit more slowly than it might otherwise.
Re:You're swapping... (Score:1)
I was trying to compile it in X11 and with some apps running. So, just for curiosity, tomorrow I'll try to compile it remotely on the machine and check if it compiles.
Thanks for the explanations.
Re:You're swapping... (Score:1)
Thanks!