search for: analysisgroups

On Thursday 09 August 2007 16:29, Devang Patel wrote: > On Aug 9, 2007, at 2:22 PM, David Greene wrote: > > A better question to ask is, how do I do this with llvm-gcc? My > > perusal of > > the code doesn't turn up any obvious places for options for alias > > analysis > > are registered. > > As you've figured out, not all options are exposed by

On Thu, 9 Aug 2007, David Greene wrote: >> As you've figured out, not all options are exposed by llvm-gcc. You'll >> have to update llvm-gcc. > > So what's the right way to do this? There's the regalloc way, which invents > a whole new class just to register register allocators and provide an option > for picking one. But alias analysis already uses

On Thursday 09 August 2007 17:27, Chris Lattner wrote: > > So what's the right way to do this? There's the regalloc way, which > > invents a whole new class just to register register allocators and > > provide an option for picking one. But alias analysis already uses > > AnalysisGroup so a new class to register alias analysis passes isn't > >

...ting BasicAA, not the pass you just wrote and stuck in > the optz'n list at some point. If you insert an AA pass at some point then > the pass manager will return that one until it's invalidated, but will > create BasicAA next time. > > Nick > So the trouble is in the way AnalysisGroups are handled, then? Is there a desire or plan to change it so that the pass continues to exist even when it's invalidated and needs to be recomputed?

On Thu, 9 Aug 2007, David Greene wrote: >> intentionally does not publish all of the llvm options through cc1. We >> can add new options, but that has to be an explicit design decision. We >> do allow you to use some options through -mllvm -foo, but that won't help >> in this case. > Alias analysis is just the closest example of what I really need to do: >

On Tue, Jan 3, 2012 at 4:55 PM, Chris Lattner <clattner at apple.com> wrote: > On Jan 3, 2012, at 1:53 PM, Jianzhou Zhao wrote: >> I see. I asked the question because LLVM provides several alias >> analysis, and I was wondering how to decide which one should be used >> for compiling most programs. >> >> I think the basicaa is the default one, but by looking

On Wed, Jan 4, 2012 at 12:10 PM, David Gardner <daveg at xmos.com> wrote: > Jianzhou Zhao <jianzhou <at> seas.upenn.edu> writes: >> The documents say that all the aa analysis are chained, and give an >> example like opt -basicaa -ds-aa -licm. In this case, does ds-aa >> automatically call basicaa for the case when ds-aa can only return >> MayAlias? This

Kenneth Uildriks wrote: > On Wed, Nov 24, 2010 at 2:50 PM, Nick Lewycky<nicholas at mxc.ca> wrote: > >> The AA that you specify will be created when you specify it and live >> until that pass is invalidated (not explicitly preserved by a pass that >> runs). The next time a pass requires AA, the pass manager will create >> the default AA (BasicAA) and not the

On Aug 21, 2008, at 1:37 AM, Wojciech Matyjewicz wrote: > I am investigating what changes are necessary to add support for > first-class structs and arrays and will prepare a version to check > in as > a LLVM project if there still is interest. We want to model this as an analysis and make following changes. - Rename LoopMemDepAnalysis as DataDependenceAnalysis. Various

Jianzhou Zhao <jianzhou <at> seas.upenn.edu> writes: > The documents say that all the aa analysis are chained, and give an > example like opt -basicaa -ds-aa -licm. In this case, does ds-aa > automatically call basicaa for the case when ds-aa can only return > MayAlias? This looks magic to me. Is this handled by AnalysisGroup > magically? As I understand it, the

On Wed, Nov 24, 2010 at 2:50 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > The AA that you specify will be created when you specify it and live > until that pass is invalidated (not explicitly preserved by a pass that > runs). The next time a pass requires AA, the pass manager will create > the default AA (BasicAA) and not the one you put on the command line. > I thought

On Dec 5, 2013, at 3:19 PM, Dan Gohman <dan433584 at gmail.com> wrote: > > > > On Mon, Dec 2, 2013 at 4:25 PM, Andrew Trick <atrick at apple.com> wrote: > > On Nov 25, 2013, at 4:40 PM, Dan Gohman <dan433584 at gmail.com> wrote: > > > Hello llvm-dev, > > > > Following up on the "CodeGen Context" discussion that was started,

On Tue, 21 Mar 2006, Michael McCracken wrote: > opt: /home/mmccrack/lens/obj-llvm-darcslocal/../llvm-darcslocal/llvm/lib/VMCore/PassManagerT.h:426: > void llvm::PassManagerT<UnitType>::markPassUsed(const llvm::PassInfo*, > llvm::Pass*) [with UnitType = llvm::Module]: Assertion > `getAnalysisOrNullUp(P) && > dynamic_cast<ImmutablePass*>(getAnalysisOrNullUp(P))

On Thu, Dec 5, 2013 at 4:16 PM, Andrew Trick <atrick at apple.com> wrote: > We currently have something that looks like: > > IR Transform > (links with) -> TargetTransformInfo > (dynamic call) -> X86TTI > (links with) -> X86Subtarget > > I was thinking of directly replacing X86Subtarget as such: > > IR Transform > (links with) ->

Thanks, John. This sounds reasonable that the analysis group just provides an interface to its implementors (pass). Then I have another question, is it allowed to specify multiple pass in the same analysis group in the command line for opt? If yes, which pass will be used for the call of getAnaysis<AnalysisGroup>()? -Thomson On Mon, Jun 25, 2012 at 10:34 PM, John Criswell <criswell at

Hi Kenneth, > So the trouble is in the way AnalysisGroups are handled, then?  Is > there a desire or plan to change it so that the pass continues to > exist even when it's invalidated and needs to be recomputed? This is definitely a bug which needs to be fixed. Noone just expressed the willingness to fix it :) -- With best regards, Anton Korob...

Ok, here's a potentialy stupid question: how do I choose the various flavors of alias analysis on the command line? I followed the alias analysis design in its use of AnalysisGroup when I did the register coalescing refactoring and alternative implentations. But I can't figure out how to actually invoke the different versions. There's no cl_opt for the various alias analysis flavors

On Thursday 09 August 2007 15:56, Devang Patel wrote: > On Aug 9, 2007, at 1:52 PM, David Greene wrote: > > So how do I get opt to use Andersens instead of basicaa, for example? > > Following uses basic alias analysis > > $ opt -licm foo.bc -disable-output -debug-pass=Structure > > where as > > $ opt -anders-aa -licm foo.bc -disable-output -debug-pass=Structure

On Aug 9, 2007, at 2:22 PM, David Greene wrote: > A better question to ask is, how do I do this with llvm-gcc? My > perusal of > the code doesn't turn up any obvious places for options for alias > analysis > are registered. As you've figured out, not all options are exposed by llvm-gcc. You'll have to update llvm-gcc. - Devang

Hi, On Fri, 2008-08-29 at 09:24 -0700, Devang Patel wrote: [...] > - Put various tests, DeltaTest, in lib/Analysis folder. The > transformation pass does not need to see these details. I believe some low-level tests should actually not be implemented as a separate Analysis but placed into Support. For instance, DeltaTest would use GCD or other tests on a different set of indexes once