search for: llvmanalysi

...ink it is conceptually accurate. - What is intrinsics_gen and why does pretty much everything depend on it? - The graph says that nothing except HowToUseJIT depends on LLVMCore. In fact, there are very few dependencies between different libraries.... for example, unlike the earlier graph, it says LLVMAnalysis, LLVMTransformUtils and LLVMScalarOpts DO NOT depend on each other. This is all wrong, right? I think the problem is that it's a graph of BUILD dependencies, not real dependencies: for example LLVMAnalysis and LLVMCore libraries can be BUILT independently, because LLVMAnalysis' doesn't...

...o link just the JIT or just the interpreter into their apps, instead of always having both or none. > I don't know enough about the codegen/target/analysis/ipa stuff to be > able to make any suggestions. Perhaps Chris can shed some light. >> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a >> libLLVMTransformUtils.a libLLVMipa.a Codegen and SelectionDAG can be merged, either physically in the source base or treated as one thing in your code. CodeGen should depend on Target, but not the other way around. LLVMIPA should depend on LLVMAnalysis, but certain...

On Mar 21, 2006, at 11:23 PM, Chris Lattner wrote: >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a >>> libLLVMTarget.a >>> libLLVMTransformUtils.a libLLVMipa.a > > CodeGen should depend on Target, but not the other way around. > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the > list should depend on LLVMIPA. If you knew what was pullin...

...where else, say just "Transforms. By doing this, we probably eliminate the cycle. I'm going to validate that shortly. Reid. On Wed, 2006-03-22 at 09:26 -0500, Eric Kidd wrote: > On Mar 21, 2006, at 11:23 PM, Chris Lattner wrote: > >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a > >>> libLLVMTarget.a > >>> libLLVMTransformUtils.a libLLVMipa.a > > > > CodeGen should depend on Target, but not the other way around. > > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the > > list should depend on LLVMIPA...

...ms. By doing this, we probably eliminate the cycle. > I'm going to validate that shortly. > > Reid. > > On Wed, 2006-03-22 at 09:26 -0500, Eric Kidd wrote: > > On Mar 21, 2006, at 11:23 PM, Chris Lattner wrote: > > >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a > > >>> libLLVMTarget.a > > >>> libLLVMTransformUtils.a libLLVMipa.a > > > > > > CodeGen should depend on Target, but not the other way around. > > > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the > > >...

...a patch, thanks! >> >> >> Still trying to hunt it down, but from what it seems so far, the file >> IVUsers.cpp does not seem to be compiled into any library, not >> compiled at all (using cmake).  I am not sure which library it is >> supposed to be compiled into, LLVMAnalysis?  If so then IVUsers.cpp >> needs to be added to the CMakeLists.txt in the lib/analysis/ >> directory.  And just checked, the IVStrideUse::deleter error is also >> defined in the IVUser.cpp file as well, so including that will >> probably fix it.  Going to resync to trunk a...

...eidoscope-Ch5, "examples\Kaleidoscope\Chapter5\Kaleidoscope-Ch5.vcproj" Kaleidoscope-Ch6, "examples\Kaleidoscope\Chapter6\Kaleidoscope-Ch6.vcproj" Kaleidoscope-Ch7, "examples\Kaleidoscope\Chapter7\Kaleidoscope-Ch7.vcproj" LLVMAnalysis, "lib\Analysis\LLVMAnalysis.vcproj" LLVMArchive, "lib\Archive\LLVMArchive.vcproj" LLVMAsmParser, "lib\AsmParser\LLVMAsmParser.vcproj" LLVMAsmPrinter, "lib\CodeGen\AsmPrinter\LLVMAsmPrinter.vcproj"...

David Piepgrass <dpiepgrass at mentoreng.com> writes: > One thing that helps me understand complex software is a dependency > graph. I found an LLVM dependency graph at > > https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies > > but it's really messy and hard to follow. From that graph I made a > cleaner graph by hand

...eidoscope-Ch5, "examples\Kaleidoscope\Chapter5\Kaleidoscope-Ch5.vcproj" Kaleidoscope-Ch6, "examples\Kaleidoscope\Chapter6\Kaleidoscope-Ch6.vcproj" Kaleidoscope-Ch7, "examples\Kaleidoscope\Chapter7\Kaleidoscope-Ch7.vcproj" LLVMAnalysis, "lib\Analysis\LLVMAnalysis.vcproj" LLVMArchive, "lib\Archive\LLVMArchive.vcproj" LLVMAsmParser, "lib\AsmParser\LLVMAsmParser.vcproj" LLVMAsmPrinter, "lib\CodeGen\AsmPrinter\LLVMAsmPrinter.vcproj"...

...be passed > to > the linker for including them on the final executable. I was linking with VMCore.lib support.lib System.lib Analysis.lib CodeGen.lib Target.lib Transforms.lib and I'm now linking with LLVMVMCore.lib LLVMScalarOpts.lib LLVMSelectionDAG.lib LLVMSupport.lib LLVMSystem.lib LLVMAnalysis.lib LLVMCodeGen.lib LLVMTarget.lib LLVMTransformUtils.lib LLVMAsmPrinter.lib > > In my opinion, we have to choose one way and remove the other one. If > > it helps, you can put in the win32 directory the result of CMake, > > On the release tarball? It seems a good idea (as far...

...;only" 3.39 MB, but this is still 85% larger than the binary to which I was thinking of adding LLVM. The top ten LLVM libraries (Win32 *.lib) are pretty huge: Release Bld Debug Bld Name 24,510,490 71,038,240 LLVMCodeGen.lib 21,084,666 56,724,338 LLVMCore.lib 14,624,218 37,070,488 LLVMAnalysis.lib 11,987,202 30,711,450 LLVMScalarOpts.lib 8,600,668 23,837,478 LLVMSelectionDAG.lib 8,634,324 23,802,952 LLVMTransformUtils.lib 8,347,134 20,840,744 LLVMipo.lib 5,061,702 11,028,744 LLVMX86CodeGen.lib 3,857,612 9,270,012 LLVMInstCombine.lib 3,330,608 7,820,760 LLVMS...

...> their apps, instead of always having both or none. FWIW, this is now in CVS. >> I don't know enough about the codegen/target/analysis/ipa stuff to be >> able to make any suggestions. Perhaps Chris can shed some light. > >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a >>> libLLVMTransformUtils.a libLLVMipa.a > > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the list > should depend on LLVMIPA. If you knew what was pulling in IPA that would > probably be an easy tie to sever. To diagnose and fix thi...

Mondada Gabriele <g.mondada at etel.ch> writes: > I just moved to the CMake solution. By the way, the generated libs > haven't the same names. Which ones? The only difference is that we now generate .lib files where .obj were generated on the past, and require a parameter to be passed to the linker for including them on the final executable. > In my opinion, we have to choose

Does not seem to be a straight error with LLVM itself, but rather the tools, linking issues, here are the errors: Opt: 30> Creating library R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.lib and object R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.exp 30>LLVMScalarOpts.lib(IndVarSimplify.obj) : error LNK2019: unresolved external symbol "public: bool __thiscall

...ve a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols: "llvm::FindUsedTypes ... ld: symbol(s) not found" I tried following link options: LLVMLIBS = LLVMAnalysis.a LINK_COMPONENTS = analysis LINK_COMPONENTS = all But nothing solved my problem (in fact the last made some other problems with code I never touched). I would be very appreciated for any idea. Thanks a lot Nico PS: output from "make VERBOSE=1" llvm[2]: Linking Release executable l...

...sted on the polyhedron.com benchmarks) ------------------------------------------------------------------------ For us it would be useful to have the RegionPass interface in LLVM mainline. Here what I found at the first glance: * cmake/modules/LLVMLibDeps.cmake: > set(MSVC_LIB_DEPS_LLVMipa LLVMAnalysis LLVMCore LLVMSupport > LLVMSystem) > +set(MSVC_LIB_DEPS_LLVMregion LLVMAnalysis LLVMCore LLVMSupport > LLVMSystem) Call the library LLVMRegion instead of LLVMregion? * docs/Passes.html: > -<tr><td><a href="#constprop">-constprop</a></td>&l...

...39;t know how to solve it: > The target machine uses 'FindUsedTypes' pass and when I try to use my > target machine in the tool I got "Undefined symbols: > "llvm::FindUsedTypes ... ld: symbol(s) not found" > > I tried following link options: > LLVMLIBS = LLVMAnalysis.a > LINK_COMPONENTS = analysis > LINK_COMPONENTS = all > But nothing solved my problem (in fact the last made some other > problems with code I never touched). > > I would be very appreciated for any idea. > > Thanks a lot > Nico > > PS: output from "make VE...

...doing a cmake: cmake -DLLVM_ENABLE_DOXYGEN=ON -DLLVM_ENABLE_WERROR=OFF -DLLVM_TARGETS_TO_BUILD="X86" ../llvm and followed by make: [ 22%] Built target LLVMVectorize [ 25%] Built target LLVMScalarOpts [ 25%] Built target LLVMObjCARCOpts [ 25%] Built target LLVMLinker [ 29%] Built target LLVMAnalysis [ 30%] Built target LLVMMCParser [ 30%] Built target LLVMMCDisassembler [ 32%] Built target LLVMMC [ 32%] Built target LLVMOption [ 34%] Built target LLVMObject [ 34%] Built target LLVMDebugInfoCodeView [ 34%] Built target LLVMTarget [ 35%] Built target X86CommonTableGen [ 35%] Built target LLVMX8...

...now. The following adds libraries for Cygwin and also for MinGW (not tested) where Linux's g++ ld finds these from a path using a weird command line which does not work on Cygwin or MinGW. lib/Transofrms/Helol/Makefile :- +ifeq ($(OS), $(filter $(OS), Cygwin MingW)) + USEDLIBS = LLVMAnalysis.a LLVMCore.a LLVMInstrumentation.a LLVMScalarOpts.a LLVMSupport.a LLVMSystem.a LLVMTransformUtils.a LLVMipa.a LLVMipo.a +else + USEDLIBS = +endif Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachm...

On Jul 23, 2010, at 10:24 AM, David Piepgrass wrote: > The top ten LLVM libraries (Win32 *.lib) are pretty huge: > > Release Bld Debug Bld Name > 24,510,490 71,038,240 LLVMCodeGen.lib > 21,084,666 56,724,338 LLVMCore.lib > 14,624,218 37,070,488 LLVMAnalysis.lib > 11,987,202 30,711,450 LLVMScalarOpts.lib > 8,600,668 23,837,478 LLVMSelectionDAG.lib > 8,634,324 23,802,952 LLVMTransformUtils.lib > 8,347,134 20,840,744 LLVMipo.lib > 5,061,702 11,028,744 LLVMX86CodeGen.lib > 3,857,612 9,270,012 LLVMInstCombine.lib...