Displaying 4 results from an estimated 4 matches for "addanalysisimplspair".
2010 May 18
2
[LLVMdev] Possible memory leak in LLVM 2.5
...ng on a game engine. Haven't updated to 2.7 yet, but I do intend to.
When checking for memory leaks I found that each time I was calling EE->runFunction after creating a stub function to execute an event, all the pass information was being repeatedly added to PMDataManager.
I have changed addAnalysisImplsPair to the following, which seems to have no side effects with what I am doing. Prior to that, AnalysisImpls contained thousands of entries and each time the vector gets realloced to accommodate more entries we lose a bigger chunk of memory.
void addAnalysisImplsPair(const PassInfo *PI, Pass *P) {...
2010 May 18
0
[LLVMdev] Possible memory leak in LLVM 2.5
...yet, but I do intend to.
>
>
>
> When checking for memory leaks I found that each time I was calling
> EE->runFunction after creating a stub function to execute an event, all the
> pass information was being repeatedly added to PMDataManager.
>
>
>
> I have changed addAnalysisImplsPair to the following, which seems to have no
> side effects with what I am doing. Prior to that, AnalysisImpls contained
> thousands of entries and each time the vector gets realloced to accommodate
> more entries we lose a bigger chunk of memory.
>
>
>
> void addAnalysisImplsPa...
2010 May 18
1
[LLVMdev] Possible memory leak in LLVM 2.5
...yet, but I do intend to.
>
>
>
> When checking for memory leaks I found that each time I was calling
> EE->runFunction after creating a stub function to execute an event, all the
> pass information was being repeatedly added to PMDataManager.
>
>
>
> I have changed addAnalysisImplsPair to the following, which seems to have no
> side effects with what I am doing. Prior to that, AnalysisImpls contained
> thousands of entries and each time the vector gets realloced to accommodate
> more entries we lose a bigger chunk of memory.
>
>
>
> void addAnalysisImplsPa...
2011 Mar 15
10
[LLVMdev] Prevent unbounded memory consuption of long lived JIT processes
This series of patches address several issues causing memory usage to grow
indefinetely on a long lived process.
These are not convenional leaks -- memory would have been freed when the LLVM
context or/and JIT engine is destroyed -- but for as long as they aren't the
memory is usage effectively ubounded.
The issues were found using valgrind with '--show-reachable=yes' option:
1.