Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • And it doesn't make much difference what speed your processor is, since by far the most time is taken waiting for the disk to churn.

    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
    • Let's see if I understood correctly:
      • I have 256MB of phisical ram, so, I should not expect to compile it :-)
      • --cgoto=0 will turn off that core... what this means? I will have one, not using gotos and less efficient?
      • With 256M of RAM, you should expect to compile it.... very, very slowly. It'll swap a lot, though if you're not using much RAM (like, say, you're not running X11, or are logged out if its a windows box) it'll build less slowly.

        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.
        • Yes, with --cgoto=0 it compiles very quicly. At the moment I don't have anything written in parrot to test efficiency. I just like to compile it from time to time to see what new things are getting in it.

          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.

        • Running X, but not logged-in (under X) and compiling by ssh works just fine. All tests successfully.