Displaying 4 results from an estimated 4 matches for "trivialrewriter".
2009 Jun 04
0
[LLVMdev] Removing SimpleRewriter (formerly SimpleSpiller)
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 want to play with
it you can invoke it with the magical combination of
"-join-liveintervals=false -new-spill-fra...
2009 Jun 04
2
[LLVMdev] Removing SimpleRewriter (formerly SimpleSpiller)
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 produces awful code. If you want to play with
> it you can invoke it with the magical combination of
> "-join-liveinter...
2009 Jun 04
2
[LLVMdev] Removing SimpleRewriter (formerly SimpleSpiller)
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 that it's
2009 Jun 05
0
[LLVMdev] Removing SimpleRewriter (formerly SimpleSpiller)
...ages 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 now, but it produces awful code. If you want to play with
>> it you can invoke it with the magical combination of
>> &...