search for: optimizationlist

...,12 @@ #include "llvm/LinkAllVMCore.h" #include <memory> #include <algorithm> + +#include "dsa/DSGraph.h" +#include "dsa/DataStructure.h" +#include "poolalloc/RunTimeAssociate.h" +#include "LinkDSA.h" + using namespace llvm; // The OptimizationList is automatically populated with registered Passes by the Index: tools/opt/Makefile =================================================================== --- tools/opt/Makefile (revision 97995) +++ tools/opt/Makefile (working copy) @@ -12,3 +12,8 @@ LINK_COMPONENTS := bitreader bitwriter asmparser...

.../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-internalize")); > > -static cl::list<std::string&g...

...gt; #include <memory> > #include <algorithm> > + > +#include "dsa/DSGraph.h" > +#include "dsa/DataStructure.h" > +#include "poolalloc/RunTimeAssociate.h" > +#include "LinkDSA.h" > + > using namespace llvm; > > // The OptimizationList is automatically populated with registered > Passes by the > Index: tools/opt/Makefile > =================================================================== > --- tools/opt/Makefile (revision 97995) > +++ tools/opt/Makefile (working copy) > @@ -12,3 +12,8 @@ > LINK_COMPONENTS :...

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

Dear Patrick and Antron, I've modified the Makefiles in the poolalloc module so that they do not build shared libraries on MingW or Cygwin. Patrick, if you do an "svn up" you should be able to compile the poolalloc project now. -- John T.

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 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 uses Andersens analysis algorithm implementation. - Devang

...gt; where as > > $ opt -anders-aa -licm foo.bc -disable-output -debug-pass=Structure > > uses Andersens analysis algorithm implementation. Heh. opt was a particularly bad choice for an example on my part. It has special code to provide options for all of the optimizations: // The OptimizationList is automatically populated with registered Passes by // the PassNameParser. // static cl::list<const PassInfo*, bool, PassNameParser> PassList(cl::desc("Optimizations available:")); A better question to ask is, how do I do this with llvm-gcc? My perusal of the code doesn...

...nclude <algorithm> >> + >> +#include "dsa/DSGraph.h" >> +#include "dsa/DataStructure.h" >> +#include "poolalloc/RunTimeAssociate.h" >> +#include "LinkDSA.h" >> + >> using namespace llvm; >> >> // The OptimizationList is automatically populated with registered >> Passes by the >> Index: tools/opt/Makefile >> =================================================================== >> --- tools/opt/Makefile (revision 97995) >> +++ tools/opt/Makefile (working copy) >> @@ -12,3 +12,8 @...

Anton Korobeynikov wrote: >> Thanks Bob and John for the response. I am having problems building >> poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc >> directory results in a bunch of "undefined reference to ..." link errors >> building Release/lib/LLVMDataStructure.dll. I looked at the command line for >> > Hrm... John, is

Thanks a lot for the reply guys. So, does that mean that I cant write my own passes if I work on Windows side of the LLVM? Is there any other way to use a new pass. How are windows users supposed to work? Thanks again. On Sun, Apr 18, 2010 at 7:16 AM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > > If you compile llvm, the Hello library will be compiled too. It's

> If you compile llvm, the Hello library will be compiled too. It's not > installed but it's in build_directory/Debug/lib/LLVMHello.so (or in > build_directory/Release/lib/LLVMHello.so) Loadable passes are not supported on windows due to lack of OS dynamic linking support (and I doubt they will be supported ever). -- With best regards, Anton Korobeynikov Faculty of Mathematics