search for: simplerewriter

On Jun 3, 2009, at 5:51 PM, Evan Cheng wrote: > I vote for execution of SimpleRewriter. Yeah, go ahead and axe it: Off with its head! -Chris > > > Evan > > On Jun 3, 2009, at 1:34 PM, Lang Hames wrote: > >> Hi all, >> >> Is anyone still using SimpleRewriter (formerly known as >> SimpleSpiller)? A quick check with the test suite suggests th...

Hi all, Is anyone still using SimpleRewriter (formerly known as SimpleSpiller)? A quick check with the test suite suggests that it's badly broken. If it's not being used I'd like to remove it as part of my tidy-up of the register allocator. - Lang.

I vote for execution of SimpleRewriter. Evan On Jun 3, 2009, at 1:34 PM, Lang Hames wrote: > Hi all, > > Is anyone still using SimpleRewriter (formerly known as > SimpleSpiller)? A quick check with the test suite suggests that it's > badly broken. If it's not being used I'd like to remove it as part of >...

R.I.P. SimpleRewriter. If anyone needs it resurrected let me know. This leaves LocalRewriter (the default) and the new TrivialRewriter, which is for use only with the new in-place spilling framework. This framework appears (if you squint just right) to be basically functional now, but it produces awful code. If you wan...

On Thursday 04 June 2009 13:57, Lang Hames wrote: > R.I.P. SimpleRewriter. If anyone needs it resurrected let me know. > > This leaves LocalRewriter (the default) and the new TrivialRewriter, > which is for use only with the new in-place spilling framework. This > framework appears (if you squint just right) to be basically > functional now, but it produce...

...keeps more state in the MachineFunction, rather than in book-keeping structures like VirtRegMap. The work is in the very early stages though. - Lang. On Thu, Jun 4, 2009 at 1:46 PM, David Greene <dag at cray.com> wrote: > On Thursday 04 June 2009 13:57, Lang Hames wrote: >> R.I.P. SimpleRewriter. If anyone needs it resurrected let me know. >> >> This leaves LocalRewriter (the default) and the new TrivialRewriter, >> which is for use only with the new in-place spilling framework. This >> framework appears (if you squint just right) to be basically >> functional...

On Thursday 04 June 2009 19:03, Lang Hames wrote: > The new spilling framework inserts spill code in-place (during > register allocation) rather than deferring it using > VirtRegMap/VirtRegRewriter. The goal is to enable techniques like > iterative splitting to be implemented. It should also be a bit tidier > as it keeps more state in the MachineFunction, rather than in >