search for: llvmselectiondag

Hello, Chuck. You wrote Tuesday, May 16, 2006, 6:03:14 PM: C> /netrel/src/binutils-20050610-1/bfd/cofflink.c:1926 C> make[2]: *** I've tracked this assertion some more deep. The problem is in LLVMSelectionDAG.o file. If I run the next lines, I've got and assertion: ld -r -o LLVMSelectionDAG.o ScheduleDAGList.o ScheduleDAGRRList.o ld -o llc LLVMSelectionDAG.o If I remove one of the SheduleDAG* files from the full list of objects, LLVMSelectionDAG.o is built from, the assertion is not longer trigger...

...s would allow people to 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 LLVMAnal...

Dear llvmdev, I am new to LLVM , but have a task on writing a LLVM backend to generate some architecture specific assembly file. Here is my cygwin build setting: GCC 3.4.4 , BIN UTILITY 2.15 ,and all other packages of the right version listed on the LLVM Getting Started doc. I have successfully built Release 1.6 LLVM. All the tools has been installed there /usr/local/bin . But I

Hi, Tried to build the 1.6 release on Debian unstable, but ran into link problems for some utils ... Copying the messages when building llc, the same error occurs for lli, llvm-db and some of the examples. Is this a problem with the compiler version? LLVMSelectionDAG.o itself builds correctly. make[2]: Entering directory `/home/sameerds/data/llvm-1.6/tools/llc' llvm[2]: Linking Debug executable llc `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS_4TypeE' referenced in section `.rodata' of /home/sameerds/data/llvm-1.6/Debug/lib/LLVM...

Reid added some nice inter-library dependency 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 m...

...te: > Hi, > > Tried to build the 1.6 release on Debian unstable, but ran into link > problems for some utils ... > > Copying the messages when building llc, the same error occurs for lli, > llvm-db and some of the examples. Is this a problem with the compiler > version? LLVMSelectionDAG.o itself builds correctly. > > make[2]: Entering directory `/home/sameerds/data/llvm-1.6/tools/llc' > llvm[2]: Linking Debug executable llc > `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS_4TypeE' > referenced > in section `.rodata' of > /home/sam...

...Sel*, bool)' /home/neale/LLVM/llvm/tools/llc/Debug/llc.o: In function `ForceAsmWriterLinking': /home/neale/LLVM/llvm/include/llvm/CodeGen/LinkAllAsmWriterComponents.h:30: undefined reference to `llvm::linkOcamlGCPrinter()' collect2: ld returned 1 exit status So it appears to be missing LLVMSelectionDAG in the link specification. I've been trying to wade through the Makefile* files to see how the link specification is generated but am not getting anywhere. So my question is how/where is this generated? Neale On 4/7/09 6:16 PM, "Anton Korobeynikov" <anton at korobeynikov.info&gt...

...gt; Reid added some nice inter-library dependency 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 problemati...

...LLVMLinker, "lib\Linker\LLVMLinker.vcproj" LLVMMC, "lib\MC\LLVMMC.vcproj" LLVMMCParser, "lib\MC\MCParser\LLVMMCParser.vcproj" LLVMScalarOpts, "lib\Transforms\Scalar\LLVMScalarOpts.vcproj" LLVMSelectionDAG, "lib\CodeGen\SelectionDAG\LLVMSelectionDAG.vcproj" LLVMSupport, "lib\Support\LLVMSupport.vcproj" LLVMSystem, "lib\System\LLVMSystem.vcproj" LLVMTarget, "lib\Target\LLVMTarget.vcproj" LLVMTransfo...

...kh/llvm/obj/Debug/lib -L/usr/lib/gcc/i386-redhat-linux/3.4.3 -L/usr/lib/gcc/i386-redhat-linux/3.4.3 -L/usr/lib/gcc/i386-redhat-linux/3.4.3/../../.. /home/kh/llvm/obj/tools/llc/Debug/llc.o /home/kh/llvm/obj/Debug/lib/LLVMCBackend.o /home/kh/llvm/obj/Debug/lib/LLVMX86.o /home/kh/llvm/obj/Debug/lib/LLVMSelectionDAG.o /home/kh/llvm/obj/Debug/lib/LLVMCodeGen.o /home/kh/llvm/obj/Debug/lib/LLVMBCReader.o /home/kh/llvm/obj/Debug/lib/LLVMBCWriter.o /home/kh/llvm/obj/Debug/lib/LLVMCore.o /home/kh/llvm/obj/Debug/lib/LLVMbzip2.o --export-dynamic -lLLVMTarget -lLLVMipa -lLLVMTransforms -lLLVMScalarOpts -lLLVMAnalys...

Paul Melis wrote: > Hi, > > Óscar Fuentes wrote: >> Chuck Robey <chuckr at telenix.org> writes: >> >> >>>> Just checked that the makefiles generated by cmake work with `make' on >>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>>> missing. >>>> >>> They

...re generated on the past, and require a parameter to 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 th...

...Opts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis > /home/neale/LLVM/llvm/Debug/lib/LLVMCppBackend.o -lLLVMTarget -lLLVMCore > -lLLVMSupport -lLLVMSystem -lpthread -ldl -lm -lelf It seems, that you did not specify any single backend except C. Please do so. > So it appears to be missing LLVMSelectionDAG in the link specification. I've > been trying to wade through the Makefile* files to see how the link > specification is generated but am not getting anywhere. So my question is > how/where is this generated? List of libraries is generated via llvm-config script, which performs depende...

...ing 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 LLVMSupport.lib The binaries are vastly larger than the source code; for example, everything in...

Hi, Óscar Fuentes wrote: > Chuck Robey <chuckr at telenix.org> writes: > > >>> Just checked that the makefiles generated by cmake work with `make' on >>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>> missing. >>> >> They absolutely do work, even on FreeBSD-current( I run that here), >>

...ke command line. The manual update would consist on adding this lines to the above mentioned file: set(MSVC_LIB_DEPS_LLVMAVRAsmPrinter LLVMAsmPrinter LLVMCodeGen LLVMCore LLVMMC LLVMAVRInfo LLVMSupport LLVMSystem LLVMTarget) set(MSVC_LIB_DEPS_LLVMAVRCodeGen LLVMCodeGen LLVMCore LLVMMC LLVMAVRInfo LLVMSelectionDAG LLVMSupport LLVMSystem LLVMTarget) set(MSVC_LIB_DEPS_LLVMAVRInfo LLVMSupport) which uses MSP430 as a template and supposses that your target is named `AVR' (case sensitive). In case you use the automatic update, the first run of the build will fail because the new dependencies are still not e...

...tering directory `/home/sameerds/data/llvm-1.6/tools/llc' >> llvm[2]: Linking Debug executable llc >> `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS_4TypeE' >> referenced >> in section `.rodata' of >> /home/sameerds/data/llvm-1.6/Debug/lib/LLVMSelectionDAG >> .o: defined in discarded section >> `.gnu.linkonce.t._ZNK4llvm14TargetLowering12get >> ValueTypeEPKNS_4TypeE' of >> /home/sameerds/data/llvm-1.6/Debug/lib/LLVMSelectionDA >> G.o >> collect2: ld returned 1 exit status > > I believe this is a binuti...

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

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 kne...

...ansforms/Utils to somewhere 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...