Re: pramgas as compile-time-only

[Nick Ing-Simmons]

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.

>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?

-- 
Nick Ing-Simmons