similar to: [LLVMdev] Queries of an invalidated AA ModulePass

On Jun 29, 2010, at 9:59 AM, Will Dietz wrote: > Hi all, > > While working on a loadable Alias Analysis module pass, I'm running > into the following issue: > > I'm finding my pass queried for results after it has had > 'releaseMemory' called on it and its dependencies, but before > runOnModule is called again (on my pass or its deps). As you might >

On Tue, Jun 29, 2010 at 1:41 PM, Dan Gohman <gohman at apple.com> wrote: > My best guess is that the problem is that loopsimplify (Canonicalize > natural loops) doesn't preserve DSAA. It preserves AliasAnalysis, but as > docs/AliasAnalysis.html now mentions, this doesn't actually do anything. > And DSAA clobbers loopsimplify, because the pass manager can't > keep a

HI guys. I'm trying to build the poolalloc on llvm-2.0 but there exist some errors. Can you tell me which version of llvm is known to make the poolalloc build and install successful? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070710/4ab5e155/attachment.html>

Hello, I got a strange result when I used alias analysis DSAA, can you tell what is wrong? 1. The following is the primary body of my pass "fps.cpp": AliasAnalysis *AA = &getAnalysis<AliasAnalysis>(); AliasSetTracker AST(*AA); for (Module::iterator fi = M.begin(), fe = M.end(); fi != fe; ++fi ) for (Function::iterator bi = fi->begin(), be = fi->end(); bi

I can use the interfaces of AliasAnalysis in my pass, but how to specify the underlaying pass of AliasAnalysis is DSAA? Thanks. Xia ______________________________________ ע������30��������䣨 http://mail.sina.com.cn/chooseMode.html �� =================================================================== 15��HPѸ�۱ʼDZ���ǧԪ,����ǧԪ������� (http://ad4.sina.com.cn/wx/ads/hpzhui823.html)

Hi, I have problems to estimate the loop exit count of a simple loop with the ScalarEvolution class. simple loop: ...... int a = 0; for(int i; i < 10; ++i){ a = a + 1; }; ...... For the loop analyzation I use the ScalarEvolution class with the following initialization: ...... void analysis(Function* func) DominatorTree DT = DominatorTree(); DT.recalculate(*func);

On Nov 16, 2011, at 2:43 AM, Pankaj Gode wrote: > In order to detect whether CallSite is present in innermost loop, do I need to insert logic from LoopInfo pass for collecting loops, within a CallGraphSCC pass? > > Is there any other approach for this? > PassManager not only schedules passes, it also - manages memory - ensures that analysis info is valid at the point of use -

On Wed, Jan 2, 2019 at 1:34 AM Markus Lavin <markus.lavin at ericsson.com> wrote: > To be more specific I am trying to use LVI from inside BasicAA to improve > some cases that turned out to be relevant for our downstream target. > > > > The code is in https://reviews.llvm.org/D55107 and I have problems with a > failing assert in the LazyValueInfoWrapperPass destructor

On Sun, 3 Apr 2005, Sameer D. Sahasrabuddhe wrote: > On Sat, Apr 02, 2005 at 11:35:30AM -0600, Chris Lattner wrote: > >> On Sat, 2 Apr 2005, Sameer D. Sahasrabuddhe wrote: >>> I want to create a simple map from a Value to the instruction that >>> defines it. Such a map is present inside SchedGraph, but I need it in >>> a much simpler context. >>

Dear All, I'm currently upgrading SAFECode to the LLVM 2.7 API. I'm getting some strange errors in LLVM Passes that use analysis groups and multiple inheritance. To create analysis groups in LLVM 2.6, I would first create a base class for the analysis group and then another class that inherited from both ModulePass and the analysis group base class. That worked in LLVM 2.6, but

Hi, I am going to write a module pass (say, P) that uses function level analysis (say, A). Suppose, I analyze two different functions during the P pass: bool P::runOnModule(Module &M) { ... A &X = getAnalysis<A>(F1); ... A &Y = getAnalysis<A>(F2); ... } Will X and Y reference the same object here? It's not a problem for me, as I don't need results of

On Wed, Aug 27, 2008 at 11:35 PM, Chris Lattner <clattner at apple.com> wrote: > > On Aug 27, 2008, at 3:04 PM, Prakash Prabhu wrote: > >> Hi Chris, >> >> Thanks for the reply. I am actually interested in using the Intervals >> Analysis mainly to be able to do Region based analysis. In fact, I >> found that the way Intervals are defined mirror exactly

Hello, I have a patch to DSA you may be interested in. I thought I'd post this to llvmdev so it will be archived and googeable in case others need it, even if you decide to not merge this into mainline :-) Here are the highlights: * I refactored StdLibDataStructures::processFunction into processFunction and processCallSite to remove a lot of copy/pasted code. I also moved the libAction

On Aug 27, 2008, at 3:04 PM, Prakash Prabhu wrote: > Hi Chris, > > Thanks for the reply. I am actually interested in using the Intervals > Analysis mainly to be able to do Region based analysis. In fact, I > found that the way Intervals are defined mirror exactly the definition > of a Region in the second edition of the Dragon Book (Section 9.7 on > Region-Based Analysis),

Hi, There are two relevant hooks for you immutable pass: 1) releaseMemory() 2) doFinalization() Are you looking at the first one? I think you should act on the second instead and it should solve your issue. — Mehdi > On Dec 8, 2016, at 10:58 AM, Maxime Chevalier-Boisvert via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > We have our own subtarget, with its own pipeline

Hi. I had some problems with MI too. See bug 6251. g Am 25.03.2010 um 16:18 schrieb John Criswell <criswell at uiuc.edu>: > Dear All, > > I'm currently upgrading SAFECode to the LLVM 2.7 API. I'm getting > some > strange errors in LLVM Passes that use analysis groups and multiple > inheritance. > > To create analysis groups in LLVM 2.6, I would first

Oh, your meaning is pointers in a aliasset have equal address logically? But I think that two pointers are alias means they point to a same memory object, so if pointers "p" and "q" are alias, it seem as p = q, not &p = &q. Another question is about "forwarding". "AliasSet[XXXX, 0] may alias, Mod/Ref forwarding to YYYY" (XXXX != YYYY) means the

Hi, Looking at the output of e.g. llc -mtriple=x86_64-unknown-linux-gnu test/CodeGen/X86/pre-coalesce.ll -debug-pass=Executions Why is it that 'Basic Alias Analysis (stateless AA impl)' is freed much earlier than 'Function Alias Analysis Results' even though the latter depends on the former (at least AFAICT by looking at lib/Analysis/AliasAnalysis.cpp)? Thanks! -Markus

The management of passes in the legacy PM is ... highly confusing. Do you have a specific problem you're trying to solve or a specific question? On Thu, Dec 27, 2018 at 6:47 AM Markus Lavin via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > > Looking at the output of e.g. > > > llc -mtriple=x86_64-unknown-linux-gnu test/CodeGen/X86/pre-coalesce.ll >

Hi Andrew, > This should really be in the FAQ. But sufice to say if you make > your pass a function pass, you will be fine. > Andrew Thx for you reply. I think I can squeeze everything into a function pass, but I'd like to run this by you, just in the case I mixed-up something: (Chris, I'd also appreciate you wise thoughts on this. I'm sure that other users are banging