Displaying 4 results from an estimated 4 matches for "islegaltocoalesc".
Did you mean:
islegaltocoalesce
2007 Aug 27
0
[LLVMdev] [patch] Pluggable Coalescers
...ce should be made by the
+ /// coalescer.
+ virtual bool okToCoalesce(const MachineInstr &inst) const {
+ return(true);
+ }
I think we discussed this early but please remind me. Why is this
necessary? Why isn't interfere() sufficient test? Also, I would prefer
a name like isLegalToCoalesce over okToCoalesce.
4. Is it necessary to separate class InterferenceData out from
RegisterCoalescer.h?
5.
+ /// Run the coalescer on this function, providing interference
+ /// data to query. Return whether we removed any copies.
+ virtual bool coalesceFunction(MachineFunction &m...
2007 Aug 27
2
[LLVMdev] [patch] Pluggable Coalescers
.../// coalescer.
> + virtual bool okToCoalesce(const MachineInstr &inst) const {
> + return(true);
> + }
>
> I think we discussed this early but please remind me. Why is this
> necessary? Why isn't interfere() sufficient test? Also, I would prefer
> a name like isLegalToCoalesce over okToCoalesce.
interfere() isn't sufficient because the allocation algorithm may place other
constraints on coalescing. George and Appel's iterated register coalescing
is a prime example. It wants to "freeze" copies that should not be coalesced
because doing so might cause...
2007 Aug 20
4
[LLVMdev] [patch] Pluggable Coalescers
Here's a proposed patch for reworking register coalescing to allow pluggable
coalescers. I think I've got the interfaces where I want them and am
reasonably sure I've squashed most of the bugs. I'm still doing some testing
and want to get through a whole regimen before committing.
As a reminder, this patch has several goals:
- Allow user-specified register coalescers, similar
2007 Aug 28
0
[LLVMdev] [patch] Pluggable Coalescers
...ol okToCoalesce(const MachineInstr &inst) const {
>> + return(true);
>> + }
>>
>> I think we discussed this early but please remind me. Why is this
>> necessary? Why isn't interfere() sufficient test? Also, I would
>> prefer
>> a name like isLegalToCoalesce over okToCoalesce.
>
> interfere() isn't sufficient because the allocation algorithm may
> place other
> constraints on coalescing. George and Appel's iterated register
> coalescing
> is a prime example. It wants to "freeze" copies that should not be
>...