Displaying 3 results from an estimated 3 matches for "mach_inst".
Did you mean:
match_inst
2007 Dec 16
3
[LLVMdev] Question about coalescing
...in SimpleRegisterCoalescing (LLVM 2.1),
but I do not want to call this analysis, as I have my own.
basically, I can determine that two virtuals do not overlap, and I
know that it is safe to join them. In the old v1.9, I simply had to do
this:
this->interval_analysis_->JoinCopy(mach_inst, use_eg, def_reg);
best,
Fernando
2007 Dec 17
0
[LLVMdev] Question about coalescing
...> 2.1),
> but I do not want to call this analysis, as I have my own.
>
> basically, I can determine that two virtuals do not overlap, and I
> know that it is safe to join them. In the old v1.9, I simply had to do
> this:
>
> this->interval_analysis_->JoinCopy(mach_inst, use_eg, def_reg);
SimpleRegisterCoalescing::JoinCopy hasn't fundamentally changed from
the old JoinCopy. It still does the same sort of analysis. The only
change really is the interface.
Evan
>
>
> best,
>
> Fernando
> _______________________________________________
&g...
2007 Dec 17
2
[LLVMdev] Question about coalescing
...do not want to call this analysis, as I have my own.
>>
>> basically, I can determine that two virtuals do not overlap, and I
>> know that it is safe to join them. In the old v1.9, I simply had to do
>> this:
>>
>> this->interval_analysis_->JoinCopy(mach_inst, use_eg, def_reg);
>
> SimpleRegisterCoalescing::JoinCopy hasn't fundamentally changed from
> the old JoinCopy. It still does the same sort of analysis. The only
> change really is the interface.
>
> Evan
>
>>
>>
>> best,
>>
>> Fernando
>>...