Re: Optimization pipeline

2005-07-15 Thread Yuval Kogman
On Thu, Jul 14, 2005 at 18:06:24 -0700, Dave Whipp wrote: > Yuval Kogman wrote: > > > - optimizers stack on top of each other > > - the output of each one is executable > > - optimizers work in a coroutine, and are preemptable > > - optimizers are small > > - optimizers operate

Re: Optimization pipeline

2005-07-14 Thread Larry Wall
On Thu, Jul 14, 2005 at 06:06:24PM -0700, Dave Whipp wrote: : Yuval Kogman wrote: : : > - optimizers stack on top of each other : > - the output of each one is executable : > - optimizers work in a coroutine, and are preemptable : > - optimizers are small : > - optimizers opera

Re: Optimization pipeline

2005-07-14 Thread Larry Wall
There may be some tie-in with STM here too, where a particular optimization doesn't commit if the optimization gives up in the middle, or is preempted before it gets done. But maybe it's all done with cooperative multitasking. (But maybe STM is how they cooperate...) Just a half-baked thought.

Re: Optimization pipeline

2005-07-14 Thread Dave Whipp
Yuval Kogman wrote: - optimizers stack on top of each other - the output of each one is executable - optimizers work in a coroutine, and are preemptable - optimizers are small - optimizers operate with a certain section of code in mind > ... Optimizers