search for: nativecodegen

...#39;: > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/include/llvm/Support/TargetSelect.h:149: undefined reference to `LLVMInitializeX86AsmParser' > collect2: ld returned 1 exit status So I add back to lli/CMakeLists.txt: < set(LLVM_LINK_COMPONENTS mcjit jit interpreter nativecodegen bitreader asmparser selectiondag) > set(LLVM_LINK_COMPONENTS ${LLVM_TARGETS_TO_BUILD} mcjit jit interpreter nativecodegen bitreader asmparser selectiondag) lli/Makefile (a simple make invocation didnt seem to regenerate the Makefile): <LINK_COMPONENTS := mcjit jit interpreter nativecodegen...

...nt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/include/llvm/Support/TargetSelect.h:149: undefined reference to `LLVMInitializeX86AsmParser' >> collect2: ld returned 1 exit status > > So I add back to lli/CMakeLists.txt: > < set(LLVM_LINK_COMPONENTS mcjit jit interpreter nativecodegen bitreader asmparser selectiondag) >> set(LLVM_LINK_COMPONENTS ${LLVM_TARGETS_TO_BUILD} mcjit jit interpreter nativecodegen bitreader asmparser selectiondag) > > lli/Makefile (a simple make invocation didnt seem to regenerate the Makefile): > <LINK_COMPONENTS := mcjit jit interpre...

On 5/14/2012 10:28 AM, Jim Grosbach wrote: > > On May 14, 2012, at 10:21 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote: > >> On 5/14/2012 9:51 AM, Jim Grosbach wrote: >>> >>>>> >>>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT. >>>>>

Hi, Using the trunk of svn. I'm trying to get inline-asm working on X86. So I added call to: > InitializeNativeTargetAsmParser() during initialization. However, this causes a linking error: > llvm[2]: Linking Debug+Asserts executable lli > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function

Beckert Frey <beckert.frey at yahoo.com> writes: [snip] > Is InstCombine required for lli? Yes: $ llvm-config --libs mcjit jit interpreter nativecodegen bitreader asmparser selectiondag -lLLVMAsmParser -lLLVMBitReader -lLLVMX86CodeGen -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMMCParser -lLLVMInterpreter -lLLVMJIT -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLL...

...l InitializeAllAsmParsers (similarly for any other All*) - see the various AllTargetsAsmParsers and similar rules in cmake/modules/LLVM-Config.cmake * Some executables depend only on the native target support InitializeNativeTarget* functions - see the JIT tests and the "native" and "nativecodegen" rules in the above cmake file. So... - any ideas? Should we just give up some of this fine grained dependency control & say you can only depend on all targets? (or maybe "all targets or the native target" and I'll make two libraries - libLLVMAllTargets and libLLVMNativeTarg...

Hi, thanks for your answers. I did: cd workspace svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm cd llvm/ mkdir build cd build/ ../configure --enable-jit make                                                      # OK, everything went fine. cd ../lib/Transforms/InstCombine/            # Just to test vim InstCombineCalls.cpp                       # added `if (0 == 1) return 0;` at

Greetings, I am searching for an alternative to sun's java implementation - one that is not under gpl.. I've been reading the vmkit code for JNI.. And I notice that it is not completely filled out yet... That's fine though, I see there is filled in function like most of the non implemented functions.. Couple of questions: Is the entire llvm required for java/cli vmkit to run?

> Neither worked. =( Hmm. Something seems to have gone horribly wrong then. I've just reproduced Peter's suggestion on the autoconf build and it worked fine. Perhaps try a clean build out of tree: CMake: mkdir my_special_build_dir cd my_special_build_dir cmake $PATH_TO_LLVM_SOURCE make llc Autotools: mkdir my_special_build_dir cd my_special_build_dir $PATH_TO_LLVM_SOURCE/configure

...and print result std::string result = *(std::string*)p; std::cout << "Result: " << result << std::endl; // TODO: call std::string destructor return 0; } = Compile = g++ -o TestStructRet TestStructRet.cc `llvm-config --cxxflags --ldflags --libs jit interpreter nativecodegen bitreader ` == End ==

...;===------------------------------------------------------------------------===; [component_0] type = Tool name = opt parent = Tools required_libraries = AsmParser BitReader BitWriter CodeGen IRReader IPO Instrumentation Scalar ObjCARC Passes ExecutionEngine Interpreter MCJIT Native NativeCodeGen all-targets ``` On top of that I also added these lines to the beginning of main function in opt.cpp to force linking ExecutionEngine: ``` if(argc==-1){ EngineBuilder eb; ExecutionEngine* ee=eb.create(); delete ee; } ``` as well as force linking MCJIT and Interpreter by includi...

On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote: I keep seeing "this is a layering violation" comments on the lists. > While there are a few llvm.org pages that mention layers in passing, > there is nothing (that I've found) actually specifying the layers. > Trying to infer the layering from the code is tedious and

I keep seeing "this is a layering violation" comments on the lists. While there are a few llvm.org pages that mention layers in passing, there is nothing (that I've found) actually specifying the layers. Trying to infer the layering from the code is tedious and error-prone (or we wouldn't see so many violations in code reviews, eh?). Now, I understand that Google has some sort

Hey: I spent sometime debugging this, it seems like editing ``llvm/tools/opt.cpp`` and move ``cl::ParseCommandLineOptions(argc, argv, "llvm .bc -> .bc modular optimizer and analysis printer\n");`` to the beginning of main() solved it for me. I'm not sure if this is a bug on LLVM side Zhang ------------------ Original ------------------ From: "Viktor Was BSc via

...argetAsmPrinter(); Since "all" doesn't work anymore for some reason, I've managed to (through trial and error, guessing at different names shown from llvm-config --components) end up with this set of libnames: llvm_map_components_to_libnames(llvm_libs core executionengine support nativecodegen) That left me with 2 link errors referring to llvm::raw_ostream and llvm::raw_pwrite_stream. After much more digging through similar complaints on the internet.. the last fix turned out to be adding this to CMakeLists.txt: set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-rtti") I am a litt...

...DummyClangFuzzer.cpp and ClangFuzzer.cpp getting compiled - is that indendet? then i want to add some tests to the Fibonacci example and added IRReader to llvm\examples\Fibonacci\CMakeLists.txt set(LLVM_LINK_COMPONENTS    Core    ExecutionEngine    Interpreter    MC    MCJIT    Support    nativecodegen    IRReader # <-- new    ) and then build the Fibonacci example but the build will fail with this log - even git revert on the llvm root does not get me back to an buildable state, i tried to build the Fibonacci project and the solution the projects ZERO_CHECK and Fibonacci giving these er...

...et.a libLLVMMC.a libLLVMCore.a libLLVMSupport.a libLLVMSystem.a bash-3.2$ /sw/lib/llvm/bin/llvm-config --components all analysis archive asmparser asmprinter backend bitreader bitwriter codegen core engine executionengine instcombine instrumentation interpreter ipa ipo jit linker mc mcparser native nativecodegen scalaropts selectiondag support system target transformutils x86 x86asmparser x86asmprinter x86codegen x86disassembler x86info bash-3.2$ /sw/lib/llvm/bin/llvm-config --targets-built x86 bash-3.2$ /sw/lib/llvm/bin/llvm-config --host-target x86_64-apple-darwin10.3.0 bash-3.2$ /sw/lib/llvm/bin/llvm-co...

On Fri, May 15, 2020 at 6:53 PM Neil Nelson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Rarrum, > > Kubuntu 20.04 LTS is available. You may be able to upgrade to 19.10, and > then to 20.04 without reinstalling. It can be done on Xubuntu. A direct > upgrade to 20.04 should become available. LLVM 10 then installs from the > distribution packages. I put all this on a