search for: llvmipa

...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 certainly nothing in the list should depend on LLVMIPA. If you knew wha...

...ow 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 this, I need to know the specific symbol in libipa that is getting refer...

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 pulling in IPA > that would probably be an easy tie to sever. > > Ideally, none...

...g 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. If you knew what was pulling in IPA > > that would probably be an easy tie to sever....

...eid. > > 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. If you knew what was pulling in IPA > > > that would probably...

Hi all, I create a folder containing my new alias analysis pass in the lib/Analysis folder of the source tree. I mimic the way IPA did to create a LLVMipa.a library. That is, I write a Makefile to create my library and I change the Makefile correspondingly in the Analysis folder. However, when I want to use my new alias analysis in the Codegen. The compiler will complain "undefined error" during the link phase. Could anyone point me out w...

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in...

...vcproj" LLVMX86CodeGen, "lib\Target\X86\LLVMX86CodeGen.vcproj" LLVMX86Disassembler, "lib\Target\X86\Disassembler\LLVMX86Disassembler.vcproj" LLVMX86Info, "lib\Target\X86\TargetInfo\LLVMX86Info.vcproj" LLVMipa, "lib\Analysis\IPA\LLVMipa.vcproj" LLVMipo, "lib\Transforms\IPO\LLVMipo.vcproj" ModuleMaker, "examples\ModuleMaker\ModuleMaker.vcproj" X86CodeGenTable_gen, "lib\Target\X86\X86CodeGenTable_gen.vcproj"...

...f the header file/declaration. It is not like the definition in a subdirectory. Sorry my fault. Is there an overview where classes and link options are mapped to each other? Kind regards, Nico On Jan 4, 2009, at 4:07 PM, John Criswell wrote: > Dear Nico, > > I believe you need to add LLVMipa to the list of libraries to link > into > your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. > > I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if > you > added it to LINK_COMPONENTS. > > -- John T. > > Nico wrote: >> Hi, >&gt...

...t; On Dec 4, 2015, at 1:37 PM, Alex S via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > > > Hi all, > > > > I create a folder containing my new alias analysis pass in the > lib/Analysis folder of the source tree. > > I mimic the way IPA did to create a LLVMipa.a library. That is, I write > a Makefile to create my library > > and I change the Makefile correspondingly in the Analysis folder. > > > > However, when I want to use my new alias analysis in the Codegen. The > compiler will complain > > "undefined error" du...

Hi, I tried to implement an 'llc'-like tool in my project to manage different passes and a target machine. I use given llvm project structure to avoid problems but I have 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:

...ps.txt. > > There are three sets of circular dependencies between LLVM libraries. > If you use any library from one of these sets, you may need to pull > in the rest: > > LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a > libLLVMTransformUtils.a libLLVMipa.a > > LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o > LLVMSparcV9RegAlloc.o > > LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o > > The first set is the most problematic: It includes four *.a files, > which means that certain linkers will ten...

...y data to utils/llvm- config/LibDeps.txt. There are three sets of circular dependencies between LLVM libraries. If you use any library from one of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o LLVMSparcV9RegAlloc.o LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o The first set is the most problematic: It includes four *.a files, which means that certain linkers will tend to get confused unless you repeat ...

...vcproj" LLVMX86CodeGen, "lib\Target\X86\LLVMX86CodeGen.vcproj" LLVMX86Disassembler, "lib\Target\X86\Disassembler\LLVMX86Disassembler.vcproj" LLVMX86Info, "lib\Target\X86\TargetInfo\LLVMX86Info.vcproj" LLVMipa, "lib\Analysis\IPA\LLVMipa.vcproj" LLVMipo, "lib\Transforms\IPO\LLVMipo.vcproj" ModuleMaker, "examples\ModuleMaker\ModuleMaker.vcproj" X86CodeGenTable_gen, "lib\Target\X86\X86CodeGenTable_gen.vcproj"...

...e 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/attachments/20090309/3bdef8ef/attachment.html> -------------- next part -------------- A non-text attachment was...

...a LLVMBuild.cmake file in the build dir specifying the link time dependences on a lib: for example, ./LLVMBuild.cmake:set_property(GLOBAL PROPERTY LLVMBUILD_LIB_DEPS_LLVMipo LLVMAnalysis LLVMCore LLVMInstCombine LLVMObjCARCOpts LLVMScalarOpts LLVMSupport LLVMTarget LLVMTransformUtils LLVMVectorize LLVMipa) The dependences set by the LLVMBuild.txt infrastructure are redundant with the dependences specified in the CMakeLists.txt using add_dependencies as in: add_dependencies(LLVMipo intrinsics_gen) That also means that a conditional cmake dependence of the form: if (WITH_POLLY AND NOT POLLY_BUILD_...

...ection of my CMake build script for the final executable: ${PLATFORM_LIBS} #LLVMX86Disassembler #LLVMX86AsmParser LLVMX86AsmPrinter LLVMX86CodeGen LLVMX86Utils LLVMX86Desc LLVMX86Info LLVMSelectionDAG LLVMAsmPrinter #LLVMJIT #LLVMExecutionEngine LLVMCodeGen LLVMScalarOpts LLVMTransformUtils #LLVMipa LLVMAnalysis LLVMTarget LLVMMCParser LLVMMC LLVMCore LLVMSupport It took me a little while to get the ordering right the first time, but it has been pretty stable since then. On Fri, May 25, 2012 at 6:24 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > So you are using Visual Studi...

...VMAnalysis [ 26%] Built target LLVMAsmPrinter [ 29%] Built target LLVMSelectionDAG [ 30%] Built target LLVMBitReader [ 31%] Built target LLVMBitWriter [ 32%] Built target LLVMInstrumentation [ 36%] Built target LLVMipo [ 36%] Built target LLVMHello [ 36%] Built target LLVMLinker [ 36%] Built target LLVMipa [ 38%] Built target LLVMMC [ 38%] Built target FileCheck [ 40%] Built target ARMCodeGenTable_gen [ 44%] Built target LLVMARMCodeGen [ 45%] Built target LLVMARMInfo [ 45%] Built target LLVMARMAsmPrinter [ 45%] Built target LLVMCBackend [ 45%] Built target LLVMCBackendInfo [ 45%] Built target LLVMCpp...

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron