search for: linkallvmcore

...ple enough to extend to all of poolalloc by adding more classes to LinkDSA.h. Andrew Index: tools/opt/opt.cpp =================================================================== --- tools/opt/opt.cpp (revision 97995) +++ tools/opt/opt.cpp (working copy) @@ -38,6 +38,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 populat...

I've completed a survey of llvm for unnecessary dependencies on libstdc++, and on conflicts with the upcoming C++0X standard, and am recommending several changes in the enclosed patch (created with svn diff). Here is a summary of the patch: --- #include <cstdlib> added to LinkAllVMCore.h and LinkAllCodegenComponents.h to declare std::getenv. Changed next(...) to llvm::next(...) in many places. I only changed those instances which were actually required to avoid ambiguity. I left other calls to next() unqualified. I do not have strong feelings about how this particular situati...

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

...dding more classes to > LinkDSA.h. > > Andrew > > Index: tools/opt/opt.cpp > =================================================================== > --- tools/opt/opt.cpp (revision 97995) > +++ tools/opt/opt.cpp (working copy) > @@ -38,6 +38,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; > &g...

...nclosed patch (created with svn > diff). Thanks, applied here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20091130/092102.html I fixed a few lines to stay in 80 cols. -Chris > > Here is a summary of the patch: > > --- > > #include <cstdlib> added to LinkAllVMCore.h and > LinkAllCodegenComponents.h to declare std::getenv. > > Changed next(...) to llvm::next(...) in many places. I only changed > those instances which were actually required to avoid ambiguity. I > left other calls to next() unqualified. I do not have strong > feeli...

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.

....h. >> >> Andrew >> >> Index: tools/opt/opt.cpp >> =================================================================== >> --- tools/opt/opt.cpp (revision 97995) >> +++ tools/opt/opt.cpp (working copy) >> @@ -38,6 +38,12 @@ >> #include "llvm/LinkAllVMCore.h" >> #include <memory> >> #include <algorithm> >> + >> +#include "dsa/DSGraph.h" >> +#include "dsa/DataStructure.h" >> +#include "poolalloc/RunTimeAssociate.h" >> +#include "LinkDSA.h" >> + &gt...

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

...alysisSupport.h TypeSymbolTable.h AutoUpgrade.h DerivedTypes.h Instructions.h LLVMContext.h PassManager.h Use.h BasicBlock.h ExecutionEngine/ IntrinsicInst.h LinkAllPasses.h PassManagers.h User.h Bitcode/ Function.h Intrinsics.gen LinkAllVMCore.h PassRegistry.h Value.h CMakeLists.txt GVMaterializer.h Intrinsics.h Linker.h PassSupport.h ValueSymbolTable.h CallGraphSCCPass.h GlobalAlias.h Intrinsics.td MC/ Support/ aarumug at aarumgxp /cygdrive/c/llvm-2.8/include/llvm $ cd ....

...talling: /usr/local/llvm-2.8/include/llvm/IntrinsicsX86.td -- Installing: /usr/local/llvm-2.8/include/llvm/IntrinsicsXCore.td -- Installing: /usr/local/llvm-2.8/include/llvm/LLVMContext.h -- Installing: /usr/local/llvm-2.8/include/llvm/LinkAllPasses.h -- Installing: /usr/local/llvm-2.8/include/llvm/LinkAllVMCore.h -- Installing: /usr/local/llvm-2.8/include/llvm/Linker.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC -- Installing: /usr/local/llvm-2.8/include/llvm/MC/EDInstInfo.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/ELFObjectWriter.h -- Installing: /usr/local/llvm-2.8/include/llvm/MC/MCAsm...

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel