Displaying 3 results from an estimated 3 matches for "ldndate".
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
...tition Construction
Custom Pass
Preliminary module verification
Dominator Tree Construction
Module Verifier
Interval Size: 0
Interval Size: 1
Interval Size: 2
Function: lresurrect
Interval Size: 3
Interval Size: 4
Interval Size: 5
Interval Size: 6
Interval Size: 7
Function: ldndate
As seen above, the intervals computed for lresurrect are still present
in the intervals vector, when function ldndate is accessed. Is this
expected ? Or maybe I am missing something here ?
(Actually I tried to lift the IntervalPartition::destroy() function
from private to public access and call i...
2008 Aug 27
0
[LLVMdev] IntervalPartition and Intervals per function
...tition:
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 ldndate is accessed. Is this
> expected ? Or maybe I am missing something here ?
I wouldn't be surprised if interval analysis was totally broken. Are
you interested in tracking it down and fixing the problem?
Alternatively, maybe we should remove the code from LLVM.
-Chris
2008 Aug 27
2
[LLVMdev] IntervalPartition and Intervals per function
...ke 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 ldndate is accessed. Is this
>> expected ? Or maybe I am missing something here ?
>
> I wouldn't be surprised if interval analysis was totally broken. Are
> you interested in tracking it down and fixing the problem?
> Alternatively, maybe we should remove the code from LLVM.
>
>...