>>>>> "KF" == Ken Fox <[EMAIL PROTECTED]> writes:

  KF> Uri Guttman wrote:
  >> so my point is the the speed of the VM is a separate issue from the ease
  >> of code generation. an S2S VM would be easier to code generate for but
  >> may be slower to run. the speed difference is still an open point as dan
  >> has said. but since his goal is execution speed, that will determine the
  >> best parrot design, not ease of code generation.

  KF> Absolutely. Which is why I posted my numbers and my code.

that is good. i wasn't disagreeing with your alternative architecture. i
was just making sure that the priority was execution over compilation speed.

  KF> The other thing to consider is that Perl is still a
  KF> compile-on-the-fly system. I hope Perl 6 keeps this aspect of Perl
  KF> instead of moving to a more Javaesque development environment.

from what i gather, the compile and go is totally the case. dan has said
so several times.

  KF> This means time spent doing dataflow analysis to help with register
  KF> allocation is going to eat into perceived execution speed. Parrot might
  KF> fly, but if the Perl 6 compiler is slow, the user experience will be
  KF> poor. Hopefully the compiler will run quickly and generate decent code.
  KF> A separate super-optimizing compiler can be used for important things
  KF> like CGI.pm. ;)

i think complex optimizations will be done only with command line
options or offline or after profiling. basic programs will compile and
go as they do now. but you could create a java like environment with all
the used modules optimized to hell and even 'prelinked' to one
executable file (in native op code format) as was mentioned
recently. that single file could then be mmap'ed in and run with
hopefully impressive speed. that is one advantage of prelinking in
modules, you save on multiple file opens and mmap calls. but you don't
share the ram of the modules (assuming they are also stored in op code
format). but you do share the image of the prelinked program in multiple
processes. you choose the tradeoff as usual, ram vs. speed.

uri

-- 
Uri Guttman  ---------  [EMAIL PROTECTED]  ----------  http://www.sysarch.com
SYStems ARCHitecture and Stem Development ------ http://www.stemsystems.com
Search or Offer Perl Jobs  --------------------------  http://jobs.perl.org

Reply via email to