search for: callgraphuptodate

...ove calls, and that should not impact the CFG, right? But it will impact the CallGraph. I believe that when the FunctionPass Manager is used from within the Call Graph SCC Pass Manager, then the CGPassManager will check the modification status from the FPManager and call RefreshCallGraph() (or set CallGraphUpToDate=false;) in case modification had been done. Thus, it seems to be legit for a FunctionPass (and thereby also the FunctionPassManager) to not always preserve the CallGraph. And I think this is handled within the CGPassManager, but not when FPManager is executed directly from the MPManager Currently...

...he CFG, right? But it will impact > the CallGraph. > > > > I believe that when the FunctionPass Manager is used from within the Call > Graph SCC Pass Manager, then the CGPassManager will check the modification > status from the FPManager and call RefreshCallGraph() (or set > CallGraphUpToDate=false;) in case modification had been done. Thus, it seems > to be legit for a FunctionPass (and thereby also the FunctionPassManager) to > not always preserve the CallGraph. And I think this is handled within the > CGPassManager, but not when FPManager is executed directly from the > M...

...he CallGraph. > > > > > > > > I believe that when the FunctionPass Manager is used from within the Call > > Graph SCC Pass Manager, then the CGPassManager will check the > modification > > status from the FPManager and call RefreshCallGraph() (or set > > CallGraphUpToDate=false;) in case modification had been done. Thus, it > seems > > to be legit for a FunctionPass (and thereby also the FunctionPassManager) > to > > not always preserve the CallGraph. And I think this is handled within the > > CGPassManager, but not when FPManager is executed...

...gt; > > > > > I believe that when the FunctionPass Manager is used from within the > Call > > > Graph SCC Pass Manager, then the CGPassManager will check the > > modification > > > status from the FPManager and call RefreshCallGraph() (or set > > > CallGraphUpToDate=false;) in case modification had been done. Thus, it > > seems > > > to be legit for a FunctionPass (and thereby also the > FunctionPassManager) > > to > > > not always preserve the CallGraph. And I think this is handled within > the > > > CGPassManager,...

.../llvm/lib/VMCore/Function.cpp:188 #11 0x0000000000598107 in llvm::Inliner::runOnSCC (this=0x10e9780, SCC=...) at /home/xchen/llvm/lib/Transforms/IPO/Inliner.cpp:487 #12 0x000000000079a828 in (anonymous namespace)::CGPassManager::RunPassOnSCC (this=0x10e9f80, P=0x10e9780, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fffffffd0af, DevirtualizedCall=@0x7fffffffd1f7) at /home/xchen/llvm/lib/Analysis/IPA/CallGraphSCCPass.cpp:121 #13 0x000000000079ac71 in (anonymous namespace)::CGPassManager::RunAllPassesOnSCC (this=0x10e9f80, CurSCC=..., CG=..., DevirtualizedCall=@0x7fffffffd1f7) at /home/xchen/llvm...

...at /home/kharris/llvm30/llvm-3.0rc4.src/lib/Analysis/LoopPass.cpp:241 #17 0x00007ffff6008881 in runOnFunction (this=0x691630, F=...) at /home/kharris/llvm30/llvm-3.0rc4.src/lib/VMCore/PassManager.cpp:1512 #18 0x00007ffff5d43a11 in RunPassOnSCC (this=0x695e10, P=0x691630, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fff73a6338e, DevirtualizedCall=@0x7fff73a63453) at /home/kharris/llvm30/llvm-3.0rc4.src/lib/Analysis/IPA/CallGraphSCCPass.cpp:145 #19 0x00007ffff5d43392 in RunAllPassesOnSCC (this=0x695e10, CurSCC=..., CG=..., DevirtualizedCall=@0x7fff73a63453) at /home/kharris/llvm30/llvm-3.0rc4.sr...

...904 #16 0x00000000054d10fd in llvm::FPPassManager::runOnFunction (this=0x9102260, F=...) at /home/andy/downloads/llvm-project/llvm/lib/IR/LegacyPassManager.cpp:1514 #17 0x0000000004f2a375 in (anonymous namespace)::CGPassManager::RunPassOnSCC (this=0x9100f00, P=0x9102260, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fffffffbc2f: true, DevirtualizedCall=@0x7fffffffbccf: false) at /home/andy/downloads/llvm-project/llvm/lib/Analysis/CallGraphSCCPass.cpp:149 #18 0x0000000004f2b349 in (anonymous namespace)::CGPassManager::RunAllPassesOnSCC ( this=0x9100f00, CurSCC=..., CG=..., DevirtualizedCall=@0x7...

...nFunction >> (this=0x9102260, F=...) >> at /home/andy/downloads/llvm-project/llvm/lib/IR/LegacyPassMana >> ger.cpp:1514 >> #17 0x0000000004f2a375 in (anonymous namespace)::CGPassManager::RunPassOnSCC >> (this=0x9100f00, >> P=0x9102260, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fffffffbc2f: >> true, >> DevirtualizedCall=@0x7fffffffbccf: false) >> at /home/andy/downloads/llvm-project/llvm/lib/Analysis/CallGrap >> hSCCPass.cpp:149 >> #18 0x0000000004f2b349 in (anonymous namespace)::CGPassManager::RunAllPassesOnSCC >> ( >&gt...

.....) >>>> at >>>> /home/andy/downloads/llvm-project/llvm/lib/IR/LegacyPassManager.cpp:1514 >>>> #17 0x0000000004f2a375 in (anonymous >>>> namespace)::CGPassManager::RunPassOnSCC (this=0x9100f00, >>>> P=0x9102260, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fffffffbc2f: >>>> true, >>>> DevirtualizedCall=@0x7fffffffbccf: false) >>>> at >>>> /home/andy/downloads/llvm-project/llvm/lib/Analysis/CallGraphSCCPass.cpp:149 >>>> #18 0x0000000004f2b349 in (anonymous >>>> namespa...

...gt; at /home/andy/downloads/llvm-project/llvm/lib/IR/LegacyPassMana >>>>> ger.cpp:1514 >>>>> #17 0x0000000004f2a375 in (anonymous namespace)::CGPassManager::RunPassOnSCC >>>>> (this=0x9100f00, >>>>> P=0x9102260, CurSCC=..., CG=..., CallGraphUpToDate=@0x7fffffffbc2f: >>>>> true, >>>>> DevirtualizedCall=@0x7fffffffbccf: false) >>>>> at /home/andy/downloads/llvm-project/llvm/lib/Analysis/CallGrap >>>>> hSCCPass.cpp:149 >>>>> #18 0x0000000004f2b349 in (anonymous nam...