Displaying 4 results from an estimated 4 matches for "bu_ls_rr_sort".
2010 May 25
2
[LLVMdev] MSVC iterator debugging exception and RegReductionPriorityQueue V2.6
...e DAG.
Call Stack:
SelectionDAGISel::runOnMachineFunction:339
SelectionDAGISel::SelectAllBasicBlocks:401
SelectionDAGISel::CodeGenAndEmitDAG:603
ScheduleDAGSDNodes::Run:36
ScheduleDAG::Run:61
ScheduleDAGRRList::Schedule::185
ScheduleDAGRRList::ListScheduleBottomUp:736
RegReductionPriorityQueue<bu_ls_rr_sort>::pop:1061 <-- exception here
I haven't reported this as a bug because first I want to find out that in LLVM's usage of the std::priority_queue, could the relative priorities get changed after they are inserted in the queue thus causing the order to change?
Has this been fixed in 2....
2009 Dec 06
1
[LLVMdev] PR5382
Hello,
This patch fixes PR5382. The problem is that
"bu_ls_rr_sort::operator()" and "td_ls_rr_sort::operator()" call
getHeight() and getDepth() methods on SUnit, which can recompute
values, what invalidates heap (SPQ). This patch guarantees that height
and depth values won't be recomputed. The other solution would be to
reheapify SPQ eve...
2010 May 26
0
[LLVMdev] MSVC iterator debugging exception and RegReductionPriorityQueue V2.6
...el::runOnMachineFunction:339
> SelectionDAGISel::SelectAllBasicBlocks:401
> SelectionDAGISel::CodeGenAndEmitDAG:603
> ScheduleDAGSDNodes::Run:36
> ScheduleDAG::Run:61
> ScheduleDAGRRList::Schedule::185
> ScheduleDAGRRList::ListScheduleBottomUp:736
> RegReductionPriorityQueue<bu_ls_rr_sort>::pop:1061 <-- exception here
>
> I haven’t reported this as a bug because first I want to find out that in LLVM’s usage of the std::priority_queue, could the relative priorities get changed after they are inserted in the queue thus causing the order to change?
I believe that's p...
2010 May 26
1
[LLVMdev] MSVC iterator debugging exception and RegReductionPriorityQueue V2.6
...>> SelectionDAGISel::SelectAllBasicBlocks:401
>> SelectionDAGISel::CodeGenAndEmitDAG:603
>> ScheduleDAGSDNodes::Run:36
>> ScheduleDAG::Run:61
>> ScheduleDAGRRList::Schedule::185
>> ScheduleDAGRRList::ListScheduleBottomUp:736
>> RegReductionPriorityQueue<bu_ls_rr_sort>::pop:1061 <-- exception here
>>
>> I haven’t reported this as a bug because first I want to find out that in LLVM’s usage of the std::priority_queue, could the relative priorities get changed after they are inserted in the queue thus causing the order to change?
>
> I be...