On Wed, Aug 02, 2000 at 04:13:50PM -0400, [EMAIL PROTECTED] wrote: > I'd also like to teach PI (or whatever it becomes) to produce joined > opcodes. Ilya did some profiling of perl 5 code, and there were a bunch of > common op pairs. Joining them together (thus saving both dispatch time > *and* op setup/teardown) would get us a small win, but then saving 5 cycles > an op on ops that take 40 cycles is nothing to sneeze at... Absolutely. I'd expect this to happen for free if we can nail down a good architecture for the perl->C->native code translator. -- May the best description of competition prevail. (via, but not speaking for Deutsche Bank)
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: C# (.NET) has no interpreters Ken Fox
- Re: C# (.NET) has no interpreters Kevin Scott
- Re: C# (.NET) has no interpreters Dan Sugalski
- Re: C# (.NET) has no interpreters John Tobey
- Re: C# (.NET) has no interpreters Ken Fox
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: C# (.NET) has no interpreters John Tobey
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: Stuff in core (was Re: date interfa... Dan Sugalski
- Re: Stuff in core (was Re: date in... Joshua N Pritikin
- Re: Stuff in core (was Re: date in... Randy J. Ray
- opcodes (was Re: Stuff in core (wa... Bradley M. Kuhn
- Re: Stuff in core (was Re: date in... Ken Fox
- Papers and reference works Dan Sugalski
- Re: Stuff in core (was Re: date in... Larry Wall
- Re: Stuff in core (was Re: date interface, on language (... Piers Cawley