Re: pramgas as compile-time-only

[Dan Sugalski]

On Tue, 8 Aug 2000, Nick Ing-Simmons wrote:

> Dan Sugalski <[EMAIL PROTECTED]> writes:
> >
> >The problem perl will always run into is that our executable code counts as 
> >data to CPUs, and lives in the D cache, along with all the data we work on. 
> 
> Hmm, that is the best case for JIT compiler I have ever seen.

And a good argument for compiling to C or something that ultimately gets
you machine code. (Which I'm all for, just not as the main product of the
perl distribution)

> >Ripping through a few 100K strings'll kill any sort of benefits to keeping 
> >the optree small, though how often that happens is also up in the air. (I 
> >really want a CPU with three caches, I, D, & perl optree...)
> 
> Hey there may be $ilicon business in this perl stuff yet ;-)
> Did you remeber to patent that before you published it?

Ah, don't be silly. Though....

Got a pointer to the patent application stuff? I bet Larry wouldn't mind
having one in his portfolio. :)

                                        Dan