search for: worklistmap

Displaying 4 results from an estimated 4 matches for "worklistmap".

2018 Feb 25
3
Heap Exhaustion during 'DAGCombiner::Run'
Hi LLVM-Devs, I am in the process of updating our out-of-tree implementation from v5.0 to v6.0 RC3, and while it builds and mostly runs, I am having trouble with a small number of tests where the 'WorklistMap' in 'DAGCombiner::Run' never becomes empty. This is resulting in a runaway state of continuous heap allocation until the process exhausts all system memory. But I can't get a handle on why it is doing this, and it is not obvious to me that the changes between v5.0 and v6.0 RC3 inv...
2018 Mar 01
0
Heap Exhaustion during 'DAGCombiner::Run'
...J. O'Riordan via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi LLVM-Devs, > > I am in the process of updating our out-of-tree implementation from v5.0 to > v6.0 RC3, and while it builds and mostly runs, I am having trouble with a > small number of tests where the 'WorklistMap' in 'DAGCombiner::Run' never > becomes empty. This is resulting in a runaway state of continuous heap > allocation until the process exhausts all system memory. > > But I can't get a handle on why it is doing this, and it is not obvious to > me that the changes betwe...
2018 Mar 06
2
Heap Exhaustion during 'DAGCombiner::Run'
...ia llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > wrote: Hi LLVM-Devs, I am in the process of updating our out-of-tree implementation from v5.0 to v6.0 RC3, and while it builds and mostly runs, I am having trouble with a small number of tests where the 'WorklistMap' in 'DAGCombiner::Run' never becomes empty. This is resulting in a runaway state of continuous heap allocation until the process exhausts all system memory. But I can't get a handle on why it is doing this, and it is not obvious to me that the changes between v5.0 and v6.0 RC3 inv...
2018 Mar 06
0
Heap Exhaustion during 'DAGCombiner::Run'
...Riordan via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi LLVM-Devs, > > I am in the process of updating our out-of-tree implementation from v5.0 to > v6.0 RC3, and while it builds and mostly runs, I am having trouble with a > small number of tests where the 'WorklistMap' in 'DAGCombiner::Run' never > becomes empty. This is resulting in a runaway state of continuous heap > allocation until the process exhausts all system memory. > > But I can't get a handle on why it is doing this, and it is not obvious to > me that the changes betwe...