On Tue, 08 Aug 2000 11:33:06 -0400, Dan Sugalski wrote: >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. >Ripping through a few 100K strings'll kill any sort of benefits to keeping >the optree small Time for subroutine threading, isntead of op threading? That would definitely make the "compiled" code at least twice as big. Er, I should shut up, because I haven't got a clue how Perl is (or would be) implemented. I suspect it's similar to P-code. -- Bart.
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Larry Wall
- Re: pramgas as compile-time-only Chaim Frenkel
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Chaim Frenkel
- Re: pramgas as compile-time-only Graham Barr
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Uri Guttman
- Re: pramgas as compile-time-only Nick Ing-Simmons
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Bart Lateur
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Bart Lateur
- Re: pramgas as compile-time-only Nick Ing-Simmons
- Re: pramgas as compile-time-only Ken Fox
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Chaim Frenkel
- Re: pramgas as compile-time-only Nathan Torkington
- Re: pramgas as compile-time-only Dan Sugalski
- Re: pramgas as compile-time-only Nick Ing-Simmons
- Re: pramgas as compile-time-only Dan Sugalski