search for: filteredpassnameparser

...haps an easier way is to just expose the -simple-register-coalescing > and -conservative-register-coalescing options to the user, but I don't know > how to do that on an individual pass bases. opt just jams then all in with > PassNameParser. PassNameParser.h makes reference to a > FilteredPassNameParser that sounds closer to what I want but I can't find > the code for that anywhere. I found a fairly elegant way to do this. I implemented what I imagine FilteredPassNameParser would be. If all goes well I'll post a patch for discussion....

...s to just expose the -simple-register-coalescing > > and -conservative-register-coalescing options to the user, but I don't > > know how to do that on an individual pass bases. opt just jams then all > > in with PassNameParser. PassNameParser.h makes reference to a > > FilteredPassNameParser that sounds closer to what I want but I can't find > > the code for that anywhere. > > I found a fairly elegant way to do this. I implemented what I imagine > FilteredPassNameParser would be. If all goes well I'll post a patch for > discussion. And here it is. It seems...

...roup interface. Perhaps an easier way is to just expose the -simple-register-coalescing and -conservative-register-coalescing options to the user, but I don't know how to do that on an individual pass bases. opt just jams then all in with PassNameParser. PassNameParser.h makes reference to a FilteredPassNameParser that sounds closer to what I want but I can't find the code for that anywhere. -Dave

Hi - I wanted to make a pass available for use with llc, and found that even though there is a PassInfo::LLC value, it isn't currently used. If you compare analyze.cpp and opt.cpp to llc.cpp, the first two find appropriate pass names with a FilteredPassNameParser and create them, but llc does not - it just gets all the passes it wants through the TargetMachine. Is there a particular reason not to create general Passes from llc? Thanks, mike -- Michael McCracken UCSD CSE PhD Candidate research: http://www.cse.ucsd.edu/~mmccrack/ misc: http://michael-mccr...

...escing >>> and -conservative-register-coalescing options to the user, but I >>> don't >>> know how to do that on an individual pass bases. opt just jams >>> then all >>> in with PassNameParser. PassNameParser.h makes reference to a >>> FilteredPassNameParser that sounds closer to what I want but I >>> can't find >>> the code for that anywhere. >> >> I found a fairly elegant way to do this. I implemented what I >> imagine >> FilteredPassNameParser would be. If all goes well I'll post a >> p...

...ichael McCracken wrote: > Hi - I wanted to make a pass available for use with llc, and found > that even though there is a PassInfo::LLC value, it isn't currently > used. > > If you compare analyze.cpp and opt.cpp to llc.cpp, the first two find > appropriate pass names with a FilteredPassNameParser and create them, > but llc does not - it just gets all the passes it wants through the > TargetMachine. > > Is there a particular reason not to create general Passes from llc? > > Thanks, > mike > -------------- next part -------------- A non-text attachment was scrubbed....

...> Hi - I wanted to make a pass available for use with llc, and found > > that even though there is a PassInfo::LLC value, it isn't currently > > used. > > > > If you compare analyze.cpp and opt.cpp to llc.cpp, the first two find > > appropriate pass names with a FilteredPassNameParser and create them, > > but llc does not - it just gets all the passes it wants through the > > TargetMachine. > > > > Is there a particular reason not to create general Passes from llc? > > > > Thanks, > > mike > > > > > -----BEGIN PGP SIGNAT...

...e "llvm/Transforms/Scalar.h" > +#include "llvm/Support/PassNameParser.h" > +#include "llvm/Support/PluginLoader.h" > using namespace llvm; > > +// Pass Name Options (cf. opt) > + > +static cl::list<const PassInfo*, bool, > + FilteredPassNameParser<PassInfo::Optimization> > > +OptimizationList(cl::desc("Optimizations available:")); > + > // Optimization Options > > enum OptimizationLevels { > @@ -72,9 +80,10 @@ > cl::aliasopt(DisableInternalize), > cl::desc("Alias for -disable-internal...

On Aug 10, 2007, at 10:15 AM, David Greene wrote: > However, what happens when alias analysis information gets > invalidated? > Is Andersen's still "available" in the sense analysis groups use it? > > If not, it seems it would be tough to make sure Andersen's is always > used everywhere that AliasAnalysis is asked for because there are > passes > llvm

On Thursday 09 August 2007 19:21, Chris Lattner wrote: > Interesting question, I don't have an answer to this. To make things more > complicated, you can have multiple instances of an analysis group and may > want different things at different times: > > -basicaa -licm -something_that_invalidates_aa -andersaa -licm -whatever Some questions about that: How does this

Hi, Reid Spencer wrote: >> That's interesting! So, one only needs to add a 2-arg function called >> RunOptimizations to the module (can't check it right now)? >> > > That is correct. That function and only that function will be called. > What happens in that function is up to you :) > So, I tried this the last two days, but to no avail. I first