Ken Fox writes: > pipeline stalls, cache misses and a whole bunch of interesting things. One > of the reasons Perl performed well is that it spent a lot of time in what > they called native code, i.e. not decoding and dispatching ops. One thing we could do is look at the op paths produced by perl5 code and work out which sequences of ops occur so often that they deserve to be encapsulated in their own op. This might give us new ideas on how to design the ops. Nat
- Stuff in core (was Re: date interface, on language (was ... Simon Cozens
- Re: Stuff in core (was Re: date interface, on langu... Dan Sugalski
- Re: Stuff in core (was Re: date interface, on l... Simon Cozens
- Re: Stuff in core (was Re: date interface, ... Dan Sugalski
- Re: Stuff in core (was Re: date interface, on l... Tim Bunce
- Re: Stuff in core (was Re: date interface, ... Tim Bunce
- Re: Stuff in core (was Re: date interfa... Dan Sugalski
- Re: Stuff in core (was Re: date in... Tim Bunce
- Re: Stuff in core (was Re: dat... Graham Barr
- Re: Stuff in core (was Re: date in... Ken Fox
- Re: Stuff in core (was Re: dat... Nathan Torkington
- Re: Stuff in core (was Re:... Tim Bunce
- Re: C# (.NET) has no inter... Joshua N Pritikin
- Re: C# (.NET) has no inter... Ken Fox
- Re: C# (.NET) has no inter... Kevin Scott
- Re: C# (.NET) has no inter... Dan Sugalski
- Re: C# (.NET) has no inter... John Tobey
- Re: C# (.NET) has no inter... Ken Fox
- Re: C# (.NET) has no inter... Joshua N Pritikin
- Re: C# (.NET) has no inter... John Tobey
- Re: C# (.NET) has no inter... Joshua N Pritikin