Displaying 3 results from an estimated 3 matches for "allocatablercregs_".
2011 Sep 12
3
[LLVMdev] Possible bug in SimpleRegisterCoalescing
...a problem in SimpleRegisterCoalescing::runOnMachineFunction where the allocatable registers for each register class are initialised for the function, i.e. the lines:
for (TargetRegisterInfo::regclass_iterator I = tri_->regclass_begin(),
E = tri_->regclass_end(); I != E; ++I)
allocatableRCRegs_.insert(std::make_pair(*I,
tri_->getAllocatableSet(fn, *I)));
If the allocatable registers are dependent on the function, such as might occur when a frame pointer isn't required, then it seems that every function will use the same allocatable set...
2011 Sep 13
0
[LLVMdev] Possible bug in SimpleRegisterCoalescing
...pleRegisterCoalescing::runOnMachineFunction where the allocatable registers for each register class are initialised for the function, i.e. the lines:
>
> for (TargetRegisterInfo::regclass_iterator I = tri_->regclass_begin(),
> E = tri_->regclass_end(); I != E; ++I)
> allocatableRCRegs_.insert(std::make_pair(*I,
> tri_->getAllocatableSet(fn, *I)));
>
> If the allocatable registers are dependent on the function, such as might occur when a frame pointer isn't required, then it seems that every function will use the same al...
2011 Sep 19
1
[LLVMdev] Possible bug in SimpleRegisterCoalescing
...alescing::runOnMachineFunction where the allocatable registers for each register class are initialised for the function, i.e. the lines:
>>
>> for (TargetRegisterInfo::regclass_iterator I = tri_->regclass_begin(),
>> E = tri_->regclass_end(); I != E; ++I)
>> allocatableRCRegs_.insert(std::make_pair(*I,
>> tri_->getAllocatableSet(fn, *I)));
>>
>> If the allocatable registers are dependent on the function, such as might occur when a frame pointer isn't required, then it seems that every function will use...