Displaying 7 results from an estimated 7 matches for "findanalysisusag".
Did you mean:
findanalysisusage
2011 May 03
4
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
When migrating my project to 2.9, I've encountered a strange segfault
where if a ModulePass's getAnalysisUsage adds LoopInfo and
DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
segfault. What's odd is that if I rearrange this (add required for
DominatorTree before LoopInfo), it does not segfault. I realize that
LoopInfo requires and preserves DominatorTree, but this behavior is
strange. All my other passes migrated fine (after adding in code to do
the initializa...
2011 May 04
0
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
Hi Michael,
> When migrating my project to 2.9, I've encountered a strange segfault
> where if a ModulePass's getAnalysisUsage adds LoopInfo and
> DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
> segfault.
I suggest you build LLVM with assertions enabled - then you should get a
helpful error message rather than a segfault. I think you are not allowed
to use LoopInfo from a ModulePass, but I don't recall the details. This
came up several times already on the mailing list, s...
2011 May 04
2
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
...4, 2011 at 12:59 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Michael,
>
>> When migrating my project to 2.9, I've encountered a strange segfault
>> where if a ModulePass's getAnalysisUsage adds LoopInfo and
>> DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
>> segfault.
>
> I suggest you build LLVM with assertions enabled - then you should get a
> helpful error message rather than a segfault. I think you are not allowed
> to use LoopInfo from a ModulePass, but I don't recall the details. This
> came up several times al...
2011 May 04
0
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
...Duncan Sands<baldrick at free.fr> wrote:
>> Hi Michael,
>>
>>> When migrating my project to 2.9, I've encountered a strange segfault
>>> where if a ModulePass's getAnalysisUsage adds LoopInfo and
>>> DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
>>> segfault.
>>
>> I suggest you build LLVM with assertions enabled - then you should get a
>> helpful error message rather than a segfault. I think you are not allowed
>> to use LoopInfo from a ModulePass, but I don't recall the details. This
>>...
2011 May 04
1
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
....fr> wrote:
>>>
>>> Hi Michael,
>>>
>>>> When migrating my project to 2.9, I've encountered a strange segfault
>>>> where if a ModulePass's getAnalysisUsage adds LoopInfo and
>>>> DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
>>>> segfault.
>>>
>>> I suggest you build LLVM with assertions enabled - then you should get a
>>> helpful error message rather than a segfault. I think you are not
>>> allowed
>>> to use LoopInfo from a ModulePass, but I don't re...
2011 May 17
0
[LLVMdev] 2.9 segfault when requesting for both LoopInfo and DominatorTree analyses.
...Thanks,
Arushi
On Tue, May 3, 2011 at 6:18 PM, Michael Ilseman <michael at lunarg.com> wrote:
> When migrating my project to 2.9, I've encountered a strange segfault
> where if a ModulePass's getAnalysisUsage adds LoopInfo and
> DominatorTree, then llvm::PMTopLevelManager::findAnalysisUsage will
> segfault. What's odd is that if I rearrange this (add required for
> DominatorTree before LoopInfo), it does not segfault. I realize that
> LoopInfo requires and preserves DominatorTree, but this behavior is
> strange. All my other passes migrated fine (after adding in code...
2012 Mar 21
0
[LLVMdev] llvm seg fault when specifying addRequiredTransitive in module pass
...l,
I am using llvm to perform some static analysis with a module pass. In
getAnalysisUsage(), I specified some required passes by:
addRequiredTransitive<LoopInfo>();
When I run my pass using opt, it crashes with segmentation fault with
callstack:
#0 0x0877aebd in llvm::PMTopLevelManager::findAnalysisUsage
(this=0x8c10934, P=0xb15b988) at PassManager.cpp:573
#1 0x0877aa9b in llvm::PMTopLevelManager::setLastUser (this=0x8c10934,
AnalysisPasses=..., P=0xb121c18) at PassManager.cpp:512
#2 0x0877ee0f in llvm::MPPassManager::addLowerLevelRequiredPass
(this=0x8c102d8, P=0xb121c18, RequiredPass=0xb15b988...