Displaying 3 results from an estimated 3 matches for "addintervaltopartition".
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
...const std::vector<Interval*>& intervals = iPart.getIntervals();
...
}
However when i access the intervals vector for a particular call of
runOnFunction, it seems that alll intervals computed for the earlier
functions are still in the
vector. To verify this, I added some debug in addIntervalToPartition:
void IntervalPartition::addIntervalToPartition(Interval *I)
{
DOUT << "Interval Size: " << Intervals.size() << "\n";
...
}
I get the following debug output:
Pass Arguments: -intervals -custom -preverify -domtree -verify
Target Data Layout
ModulePass M...
2008 Aug 27
0
[LLVMdev] IntervalPartition and Intervals per function
...in
> order to obtain the set of intervals for every function:
>
> However when i access the intervals vector for a particular call of
> runOnFunction, it seems that alll intervals computed for the earlier
> functions are still in the
> vector. To verify this, I added some debug in addIntervalToPartition:
Sounds like a bug. Interval analysis is some of the oldest code in
LLVM and was never widely used (once I implemented the first dominator
info, it became unneeded).
> As seen above, the intervals computed for lresurrect are still present
> in the intervals vector, when function ldndat...
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
...ain the set of intervals for every function:
>>
>> However when i access the intervals vector for a particular call of
>> runOnFunction, it seems that alll intervals computed for the earlier
>> functions are still in the
>> vector. To verify this, I added some debug in addIntervalToPartition:
>
> Sounds like a bug. Interval analysis is some of the oldest code in
> LLVM and was never widely used (once I implemented the first dominator
> info, it became unneeded).
>
>> As seen above, the intervals computed for lresurrect are still present
>> in the intervals v...