Displaying 5 results from an estimated 5 matches for "aggressiveregistercoalescer".
2007 Jul 18
4
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
...that publicly.
It's pretty straightforward code, though.
The RegisterCoalescer interface still exists because register allocators need
to be able to invoke the coalescer, sometimes repeatedly. PassManager can't
do that. The current SimpleRegisterCoalescer (which should really be named
AggressiveRegisterCoalescer -- another patch on the way) inherits from both
MachineFunctionPass and RegisterCoalescer. The former because it is run and
managed by PassManager and the latter because it needs to belong to the
RegisterAllocator AnalysisGroup, similar to how alias analysis works. We need
a way for register...
2007 Jul 18
0
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
...rd code, though.
Ok.
> The RegisterCoalescer interface still exists because register
> allocators need
> to be able to invoke the coalescer, sometimes repeatedly.
> PassManager can't
> do that. The current SimpleRegisterCoalescer (which should really
> be named
> AggressiveRegisterCoalescer -- another patch on the way) inherits
> from both
> MachineFunctionPass and RegisterCoalescer. The former because it
> is run and
> managed by PassManager and the latter because it needs to belong to
> the
> RegisterAllocator AnalysisGroup, similar to how alias analysis
&...
2007 Jul 18
0
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
...forward code, though.
>
> The RegisterCoalescer interface still exists because register
> allocators need
> to be able to invoke the coalescer, sometimes repeatedly.
> PassManager can't
> do that. The current SimpleRegisterCoalescer (which should really be
> named
> AggressiveRegisterCoalescer -- another patch on the way) inherits
> from both
> MachineFunctionPass and RegisterCoalescer. The former because it is
> run and
> managed by PassManager and the latter because it needs to belong to
> the
> RegisterAllocator AnalysisGroup, similar to how alias analysis works....
2007 Jul 17
0
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
On Tuesday 17 July 2007 13:06, Evan Cheng wrote:
> > These two requirements led to the abstract RegisterCoalescer
> > interface in the patch. This is the interface that register
> > allocators
> > know about. Likewise, coalescers need an abstract interface to
> > register allocators to ask questions and do other things.
>
> If the two modules need to share
2007 Jul 17
3
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
On Jul 17, 2007, at 8:40 AM, David Greene wrote:
> On Monday 16 July 2007 18:19, Evan Cheng wrote:
>
>> Sorry I should have replied earlier. I really don't like this dual
>> interface approach. To me, this muddles things without offering any
>> real useful new functionalities.
>
> Ok. See below for the rationale.
>
>> IMHO, if a register coalescer is