search for: llvmtarget

Hi, I am trying to make my pass compiling inside the LLVM tree or outside. It works when I include my pass inside the tools folder, however when I try to compile it outside the LLVM tree I get the following error: "add_library cannot create target "LLVMTarget" because an imported target with the same name already exists.” It happens when I’ve already compiled and installed my target from within LLVM. I was wondering if there is a way to ignore that and just overwrite the target. Thanks. Best, Simone

...le manually or run the build with MSYS passing -DLLVM_TARGETS_TO_BUILD=all on the cmake 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 automati...

...the kms_swrast_dri.so with dlopen(LAZY|GLOBAL). kms_swrast_dri.so is linked against a large bunch of LLVM libraries (see below). b) gbm discovers it can't do what it wants and dlcloses the library. At this point a bunch of the LLVM libraries drop out of the map, pretty much everything down to LLVMTarget. Everything from LLVMTarget onwards remains loaded and I've no idea how to discover why. c) later X tries to load kms_swrast_dri.so for GLX usage, and it brings back in all the LLVM libraries that got dropped out, however as LLVMObject has never been cleaned up, it has all the command line opt...

...b\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" LLVMTransformUtils, "lib\Transforms\Utils\LLVMTransformUtils.vcproj" LLVMX86AsmParser, "lib\Target\X86\AsmParser\LLVMX86AsmParser.vcproj" LLVMX86AsmPrinter, "lib\Target\X86\AsmPrinter\...

...on. I've tried to use the MSP430 and other targets as references so I'm not sure what changes I did would cause a problem on this line? AVRTargetMachine::AVRTargetMachine(const Target &T, const std::string &TT, const std::string &FS) : LLVMTargetMachine(T, TT), Subtarget(TT, FS), DataLayout("e-p:16:8:8-i8:8:8-i16:8:8-i32:8:8"), InstrInfo(Subtarget), TLInfo(*this), FrameInfo(TargetFrameInfo::StackGrowsDown, 1, 0) { } Linking CXX executable ../../bin/llvm-mc cd /home/john/src/llvm_build/tools/llvm-mc &&am...

...r 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 as someone > volunteers to d...

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

...TOOL_LTO_BUILD:BOOL=ON >> LTO_LIB_DEPENDS:STATIC=general;LLVMX86CodeGen;general;LLVMX86AsmPrinter;general;LLVMX86AsmParser;general;LLVMX86Desc;general;LLVMX86Info;general;LLVMX86Disassembler;general;LLVMCore;general;LLVMLTO;general;LLVMMC;general;LLVMMCDisassembler;general;LLVMSupport;general;LLVMTarget; >> COMPILER_RT_HAS_FNO_LTO_FLAG:INTERNAL=1 >> LLVM_TOOL_LLVM_LTO_BUILD-ADVANCED:INTERNAL=1 >> LLVM_TOOL_LTO_BUILD-ADVANCED:INTERNAL=1 >> [ /OUTPUT ] >> >> But is no more documented in >> <http://llvm.org/releases/3.8.0/docs/CMake.html> or >> &l...

.... Name: llvm-gcc-4.2-solaris.patch Type: application/octet-stream Size: 949 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080530/4457449f/attachment-0003.obj> -------------- next part -------------- [0] e.g. ../llvm-gcc-4.2/configure --enable-llvm=${LLVMTARGET} -- disable-shared --with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu- ld --with-ld=/usr/ccs/bin/ld --enable-languages=c,c++ [1] There seems to be an unrelated issue preventing llvm-gcc-4.2 compilation on SPARC, but LLVM itself builds without problems.

...b\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" LLVMTransformUtils, "lib\Transforms\Utils\LLVMTransformUtils.vcproj" LLVMX86AsmParser, "lib\Target\X86\AsmParser\LLVMX86AsmParser.vcproj" LLVMX86AsmPrinter, "lib\Target\X86\AsmPrinter\...

...MObjCARCOpts [ 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 LLVMX86AsmParser [ 36%] Built target LLVMX86CodeGen [ 36%] Built target LLVMX86Disassembler [ 36%] Built target LLVMX86AsmPrinter [ 37%] Built target LLVMX86Desc [ 37%] Built target LLVMX86Info [ 37%] Built target LLVMX86Utils [ 37%] Built t...

I am trying to write a MachineFunction pass and build it as a loadable module. I want the pass to run after prolog/epilog emmiter. So far, I have been using MachineFunctionPass, but by inserting it to lib/Codegen and hacking the LLVMTargetMachine file, and Pass.h files. I have created a directory "lib/Transforms/MyPass", and inside I have the code of the pass (which is just a placeholder for now): ----------------------- #define DEBUG_TYPE "mypass" #include "llvm/Pass.h" #include "llvm/CodeGen/Mac...

...MObjCARCOpts [ 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 LLVMX86AsmParser [ 36%] Built target LLVMX86CodeGen [ 36%] Built target LLVMX86Disassembler [ 36%] Built target LLVMX86AsmPrinter [ 37%] Built target LLVMX86Desc [ 37%] Built target LLVMX86Info [ 37%] Built target LLVMX86Utils [ 37%] Built t...

...s/llvm-build/llvmbuild/main.py that creates 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 f...

...ild 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 Studio?! I tried that path b...

...MObjCARCOpts [ 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 LLVMX86AsmParser [ 36%] Built target LLVMX86CodeGen [ 36%] Built target LLVMX86Disassembler [ 36%] Built target LLVMX86AsmPrinter [ 37%] Built target LLVMX86Desc [ 37%] Built target LLVMX86Info [ 37%] Built target LLVMX86Utils [ 37%] Built t...

...Built target X86CodeGenTable_gen [ 62%] Built target LLVMX86CodeGen [ 63%] Built target LLVMX86Info [ 63%] Built target LLVMX86AsmPrinter [ 63%] Built target LLVMX86AsmParser [ 63%] Built target LLVMExecutionEngine [ 64%] Built target LLVMInterpreter [ 64%] Built target LLVMJIT [ 67%] Built target LLVMTarget [ 67%] Built target LLVMAsmParser [ 68%] Built target LLVMDebugger [ 68%] Built target LLVMArchive Linking CXX executable ..\..\bin\opt.exe ..\..\lib\libLLVMSystem.a(RWMutex.cpp.obj):RWMutex.cpp:(.text+0x25): undefined r eference to `_imp__pthread_rwlockattr_init' ..\..\lib\libLLVMSystem.a(RWMu...

...code)? Look through llvm/tools/Makefile.JIT -- it adds JIT support libraries to the USEDLIBS variable, so for x86, for example: LLVMJIT LLVMCodeGen LLVMExecutionEngine LLVMX86 LLVMSelectionDAG LLVMInterpreter LLVMScalarOpts LLVMAnalysis.a LLVMTransformUtils.a LLVMBCReader LLVMCore LLVMSupport.a LLVMTarget.a LLVMSystem.a For the ones without an extension, append .o, for the ones with .a, prepend 'lib' and look in llvm/lib/Release . > Where are these (I would like the list of all the lib*.{a,so} and all > headers <*.h> in /usr/local/ on my Linux/Debian/Sid/x86 system)? The heade...

...=ON LLVM_TOOL_LTO_BUILD:BOOL=ON LTO_LIB_DEPENDS:STATIC=general;LLVMX86CodeGen;general;LLVMX86AsmPrinter;general;LLVMX86AsmParser;general;LLVMX86Desc;general;LLVMX86Info;general;LLVMX86Disassembler;general;LLVMCore;general;LLVMLTO;general;LLVMMC;general;LLVMMCDisassembler;general;LLVMSupport;general;LLVMTarget; COMPILER_RT_HAS_FNO_LTO_FLAG:INTERNAL=1 LLVM_TOOL_LLVM_LTO_BUILD-ADVANCED:INTERNAL=1 LLVM_TOOL_LTO_BUILD-ADVANCED:INTERNAL=1 [ /OUTPUT ] But is no more documented in <http://llvm.org/releases/3.8.0/docs/CMake.html> or <http://llvm.org/docs/CMake.html>. I have seen LLVM_ENALBLE_LTO=On...

Le Sun, Nov 07, 2004 at 04:14:19PM -0600, Misha Brukman écrivait/wrote: > On Sun, Nov 07, 2004 at 11:04:58PM +0100, Basile STARYNKEVITCH wrote: Basile>> First, I am extremely confused by the terminology. IMHO, the runtime Basile>> libraries would include (from my JIT only perspective) Basile>> 1. all the LLVM libraries required to JIT-generate machine code, and