search for: libllvmtarget

Hello Anton Thu, 3 Aug 2006 15:06:56 +0400 you wrote: > here it is in the attachment :) Ok. Could you also send LibDeps.txt file? It should be in /obj/tools/llvm-config directory -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello Anton Fri, 4 Aug 2006 21:45:19 +0400 you wrote: > Written by Mike Haertel and Paul Eggert. > I've updated llvm and llvm-gcc4 ant trying to build it again after > PR845 was resolved. According to Reid's letter this PR coud be the > reason of my problem. Anyway, "sort" call can cause large problems depending, where in your PATH cygwin directory is (before

> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at

I keep getting this error upon building: > Linking CXX executable ../../bin/opt > ../../lib/libLLVMTarget.so: error: undefined reference to > 'llvm::TargetInstrInfo::getNumMicroOps(llvm::InstrItineraryData > const*, llvm::MachineInstr const*) const' > ../../lib/libLLVMTarget.so: error: undefined reference to > 'llvm::TargetInstrInfo::getInstrLatency(llvm::InstrItineraryData...

Hello Anton Thu, 3 Aug 2006 12:38:54 +0400 you wrote: > I've updated it yesterday and rebuilt - llvm built fine. But when > building llvm-gcc4 (also updated yesterday from new /trunk > directory) it fails with the same error. You might easily get llvm-gcc4-mingw32 binaries from "prerelease" directory. Since stdcall, fastcall & dllimport stuff is unsupported right now,

On Jun 8, 2012, at 12:52 PM, Marc J. Driftmeyer <mjd at reanimality.com> wrote: > I keep getting this error upon building: > >> Linking CXX executable ../../bin/opt >> ../../lib/libLLVMTarget.so: error: undefined reference to 'llvm::TargetInstrInfo::getNumMicroOps(llvm::InstrItineraryData const*, llvm::MachineInstr const*) const' >> ../../lib/libLLVMTarget.so: error: undefined reference to 'llvm::TargetInstrInfo::getInstrLatency(llvm::InstrItineraryData const*, llvm::M...

...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 certainly nothing in the...

...thoughts I had attempting to find a possible solution: - I could not find an instance of classes under lib/Target/X86/ (or any other target for that matter) that are used or exposed by anything outside of lib/Target/ - The only things that seem exposed under lib/Target/ are a few files packed into libLLVMTarget.a and none of it is linked against source files under llvm/Target/<TARGET> - If ShadowCallStack is meant to be a pass that should eventually work for any target, at some point it could be pulled out from the X86 directory and also be included in libLLVMTarget.a, but I'm not sure how the C...

...libLLVMAsmParser.a: libLLVMSupport.a(IncludeFile::IncludeFile(void*) libLLVMCBackend.a: libLLVMAnalysis.a(llvm::LoopInfoLinkVar) libLLVMInstrumentation.a: libLLVMScalarOpts.a(llvm::DemoteRegisterToMemoryID) LLVMIA64.o: libLLVMCodeGen.a(vtable for llvm::DefaultIntrinsicLowering) libLLVMTarget.a: libLLVMCodeGen.a( llvm::MVT::getVectorType(llvm::MVT::ValueType, unsigned int)) The following dependencies is not a singleton, but they it just seemed dubious to me that "TransformUtils" would depend on ScalarOpts. libLLVMTransformUtils.a: libLLVMScalarOpts.a llvm::LowerS...

...AsmParser.a lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Desc.a lib/libLLVMX86Disassembler.a lib/libLLVMX86Info.a lib/libLLVMX86Utils.a lib/libLLVMBitReader.a lib/libLLVMBitWriter.a lib/libLLVMCore.a lib/libLLVMIRReader.a lib/libLLVMLTO.a lib/libLLVMMC.a lib/libLLVMObject.a lib/libLLVMSupport.a lib/libLLVMTarget.a -lpthread lib/libLLVMAsmPrinter.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Utils.a lib/libLLVMMCDisassembler.a lib/libLLVMObjCARCOpts.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMTarget.a lib/libLLVMipo.a...

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 means that certain linkers will ten...

...erPCInfo.a lib/libLLVMSparcInfo.a lib/libLLVMSystemZInfo.a lib/libLLVMWebAssemblyInfo.a lib/libLLVMX86Info.a lib/libLLVMXCoreInfo.a lib/libLLVMBitReader.a lib/libLLVMBitWriter.a lib/libLLVMCore.a lib/libLLVMIRReader.a lib/libLLVMLTO.a lib/libLLVMMC.a lib/libLLVMObject.a lib/libLLVMSupport.a lib/libLLVMTarget.a -lpthread lib/libLLVMAArch64Utils.a lib/libLLVMAMDGPUUtils.a lib/libLLVMMIRParser.a lib/libLLVMARMUtils.a lib/libLLVMHexagonAsmParser.a lib/libLLVMHexagonDesc.a lib/libLLVMHexagonInfo.a lib/libLLVMLanaiAsmParser.a lib/libLLVMLanaiDesc.a lib/libLLVMLanaiInfo.a lib/libLLVMMCDisassembler.a lib...

...solution: >> - I could not find an instance of classes under lib/Target/X86/ (or >> any other target for that matter) that are used or exposed by anything >> outside of lib/Target/ >> - The only things that seem exposed under lib/Target/ are a few files >> packed into libLLVMTarget.a and none of it is linked against source >> files under llvm/Target/<TARGET> >> - If ShadowCallStack is meant to be a pass that should eventually work >> for any target, at some point it could be pulled out from the X86 >> directory and also be included in libLLVMTarg...

Trying to run make to build llvm, I faced the following error: Linking CXX shared library ../../lib/libLTO.so collect2: error: ld returned 1 exit status make[2]: *** [lib/libLTO.so.3.8.0svn] Error 1 make[1]: *** [tools/lto/CMakeFiles/LTO.dir/all] Error 2 make: *** [all] Error 2 So, what's the problem here? Regards, Marwa Yusuf Teaching Assistant - Computer Engineering Department

...lure with recent LLD on x86 like: [...] lib/libLLVMCodeGen.a lib/libLLVMBitWriter.a lib/libLLVMScalarOpts.a lib/libLLVMAgg ressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMDebugInfoDWARF.a lib/lib LLVMMCDisassembler.a lib/libLLVMExecutionEngine.a lib/libLLVMTarget.a lib/libLLVMAnalysis.a lib/libLLVMProfil eData.a lib/libLLVMRuntimeDyld.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMDebugI nfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMBitReader.a lib/libLLVMCore.a lib/libLLVMRemarks.a lib/li bLLVMBitstreamReader.a lib...

...Printer.so.3.7 (0x00007f8a61647000) libLLVMX86Utils.so.3.7 => /lib64/libLLVMX86Utils.so.3.7 (0x00007f8a6143e000) libLLVMMCJIT.so.3.7 => /lib64/libLLVMMCJIT.so.3.7 (0x00007f8a61233000) libLLVMExecutionEngine.so.3.7 => /lib64/libLLVMExecutionEngine.so.3.7 (0x00007f8a61011000) libLLVMTarget.so.3.7 => /lib64/libLLVMTarget.so.3.7 (0x00007f8a60e02000) libLLVMAnalysis.so.3.7 => /lib64/libLLVMAnalysis.so.3.7 (0x00007f8a60a33000) libLLVMRuntimeDyld.so.3.7 => /lib64/libLLVMRuntimeDyld.so.3.7 (0x00007f8a607e4000) libLLVMObject.so.3.7 => /lib64/libLLVMObject.so.3.7 (0x0...

...y 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, &...

...OptionsCommandFlags.cpp.o tools/lld/Common/CMakeFiles/lldCommon.dir/Threads.cpp.o tools/lld/Common/CMakeFiles/lldCommon.dir/Version.cpp.o -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVMCodeGen.so.6.0.0svn lib/libLLVMMC.so.6.0.0svn lib/libLLVMOption.so.6.0.0svn lib/libLLVMSupport.so.6.0.0svn lib/libLLVMTarget.so.6.0.0svn && : /usr/bin/../lib/gcc/x86_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/thread:137: error: undefined reference to 'pthread_create' /usr/bin/../lib/gcc/x86_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/thread:137: error: undefined reference to 'pthread_create...

...d: warning llvm::OwningPtr<llvm::MemoryBuffer>::~OwningPtr()has different visibility (1) in /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in /usr/local/lib/libLLVMSupport.a(CommandLine.o) ld: warning llvm::APInt::isSingleWord() consthas different visibility (2) in /usr/local/lib/libLLVMTarget.a(TargetData.o) and (1) in /usr/local/lib/libLLVMSupport.a(APFloat.o) ld: warning llvm::APInt::isSingleWord() consthas different visibility (2) in /usr/local/lib/libLLVMCore.a(Instructions.o) and (1) in /usr/local/lib/libLLVMSupport.a(APFloat.o) ld: warning llvm::APInt::getNumWords() consthas di...

Simon Burton <simon at arrowtheory.com> writes: >> There are several possibilities here: either add1 is assigned a NULL >> pointer, or LLVM was unable to use the JIT and generates bytecode >> instead of native code, or invalid native code was generated >> (unlikely). > > Well, it's not NULL: > > (gdb) print add1 > $1 = (int (*)(int)) 0x83e43b8 >