On Feb 28, 2006, at 19:59, Nicolas Cannasse wrote:
Yes I understand that there is different cores for Parrot, but what are the flags appropriate for doing some comparisons ? Some flags might do very good in some cases and quite bad in some others. They might also take tremendous time to JIT the code, hence not being usable on larger applications.
The time needed to JIT some code isn't the big deal, the more that the plan is to recompile heavily used (or small) subroutines only, and not whole applications. The currently exisiting JIT code (-j) is compiling a whole file. The new (and still experimental) -{S,C}j options will recompile code per subroutine or even per basic block for the direct threaded run core.
Is there one single config that the Parrot team is focusing on bringing to 1.0 ?
A single option can't cover all possible usage of Parrot. But it basically boils down to two options: -Os ... optimize for size (multiple processes of Parrot with shared code)
-Ot ... use more memory to run faster
Nicolas
leo
