search for: llvm_target

...LVM_ASM_PRINTER(PIC16) LLVM_ASM_PRINTER(CellSPU) LLVM_ASM_PRINTER(Mips) LLVM_ASM_PRINTER(ARM) LLVM_ASM_PRINTER(Alpha) LLVM_ASM_PRINTER(PowerPC) LLVM_ASM_PRINTER(Sparc) LLVM_ASM_PRINTER(X86) ' LLVM_ENUM_DISASSEMBLERS='LLVM_DISASSEMBLER(ARM) LLVM_DISASSEMBLER(X86) ' LLVM_ENUM_TARGETS='LLVM_TARGET(MBlaze) LLVM_TARGET(CppBackend) LLVM_TARGET(CBackend) LLVM_TARGET(Blackfin) LLVM_TARGET(SystemZ) LLVM_TARGET(MSP430) LLVM_TARGET(XCore) LLVM_TARGET(PIC16) LLVM_TARGET(CellSPU) LLVM_TARGET(Mips) LLVM_TARGET(ARM) LLVM_TARGET(Alpha) LLVM_TARGET(PowerPC) LLVM_TARGET(Sparc) LLVM_TARGET(X86) ' LLVM_E...

...LVM_ASM_PRINTER(PIC16) LLVM_ASM_PRINTER(CellSPU) LLVM_ASM_PRINTER(Mips) LLVM_ASM_PRINTER(ARM) LLVM_ASM_PRINTER(Alpha) LLVM_ASM_PRINTER(PowerPC) LLVM_ASM_PRINTER(Sparc) LLVM_ASM_PRINTER(X86) ' LLVM_ENUM_DISASSEMBLERS='LLVM_DISASSEMBLER(ARM) LLVM_DISASSEMBLER(X86) ' LLVM_ENUM_TARGETS='LLVM_TARGET(MBlaze) LLVM_TARGET(CppBackend) LLVM_TARGET(CBackend) LLVM_TARGET(Blackfin) LLVM_TARGET(SystemZ) LLVM_TARGET(MSP430) LLVM_TARGET(XCore) LLVM_TARGET(PIC16) LLVM_TARGET(CellSPU) LLVM_TARGET(Mips) LLVM_TARGET(ARM) LLVM_TARGET(Alpha) LLVM_TARGET(PowerPC) LLVM_TARGET(Sparc) LLVM_TARGET(X86) ' LLVM_E...

...ble option? I think it shouldn't be required for release binaries, and it wouldn't be required for most developers. I think it may be off by default. * What is the name of environment variable? I suggest the name itself could be configurable. If I would introduce the envvar name as "LLVM_TARGET", clang users would complain why clang didn't have like "CLANG_TARGET". $ cmake -DLLVM_DEFAULT_TARGET_ENVVAR_NAME=LLVM_TARGET $ LLVM_TARGET=i686-win32 bin/llvm-lit path/to/tests This feature may be disabled if LLVM_DEFAULT_TARGET_ENVVAR_NAME is blank. I wonder the name LLVM...

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

...found that the my target AsmPrinter is not being registered properly. This conclusion was derived from following observation. I have configured LLVM with only two targets- X86 and ASD (my target) When I checked for targets build/include/llvm/Config/Targets.def, I see my target details.   #ifndef LLVM_TARGET   #  error Please define the macro LLVM_TARGET(TargetName)   #endif   LLVM_TARGET(DRE) LLVM_TARGET(X86)   #undef LLVM_TARGET But when I check for the ASMPrinter for my target in build/include/llvm/Config/AsmPrinters.def, I see only X86 #ifndef LLVM_ASM_PRINTER #  error Please define the macro...

...; ====================================================================== > --- llvm/trunk/test/Bindings/Ocaml/executionengine.ml (original) > +++ llvm/trunk/test/Bindings/Ocaml/executionengine.ml Wed Oct 22 > 07:41:54 2008 > @@ -1,4 +1,4 @@ > -(* RUN: %ocamlc -warn-error A llvm.cma llvm_target.cma > llvm_executionengine.cma %s -o %t > +(* RUN: %ocamlc -warn-error A llvm.cma llvm_target.cma > llvm_executionengine.cma %s -o %t 2> /dev/null > * RUN: ./%t %t.bc > *) > > > Modified: llvm/trunk/test/Bindings/Ocaml/scalar_opts.ml > URL: http://llvm.org/viewvc...

.../test/Bindings/Ocaml/ bitwriter.ml -o bitwriter.ml.tmp 2> /dev/null child process exited abnormally FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/executionengine.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home/ang/build/llvm/Debug/lib/ocaml - warn-error A llvm.cma llvm_target.cma llvm_executionengine.cma /home/ang/svn/llv m/test/Bindings/Ocaml/executionengine.ml -o executionengine.ml.tmp 2> /dev/null child process exited abnormally FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/scalar_opts.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home...

...rror when it starts to build the ocaml docs. llvm[1]: Installing HTML documentation llvm[1]: Building ocamldoc documentation llvm[3]: Documenting llvm.odoc llvm[3]: Documenting llvm_bitreader.odoc llvm[3]: Documenting llvm_bitwriter.odoc llvm[3]: Documenting llvm_analysis.odoc llvm[3]: Documenting llvm_target.odoc llvm[3]: Documenting llvm_executionengine.odoc llvm[4]: Documenting llvm_scalar_opts.odoc Fatal error: exception Failure("There are two interfaces of module Llvm_analysis.") make[1]: *** [regen-ocamldoc] Error 2 make: *** [install] Error 1 This error does not happen when I install i...

...er, I'm not sure how to create my plugin any differently. I'm using cmake's 'add_library(name SHARED ...)' to create the plugin like so: add_library(reflector SHARED ${REFLECT_SOURCES} ${COMMON_HEADERS} ${REFLECT_HEADERS}) target_link_libraries(reflector linker_common ${LLVM_TARGET} ${LLVM_CORE} ${LLVM_SUPPORT} ${LLVM_SYSTEM} ) Any advice on this? -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110127/349a59f5/attachment.html>

Hi Jean-Daniel, My fault, I'm sure, but I don't see the problem yet. Is it possible your version of llvm/Config/AsmPrinters.def has X86 listed twice? - Daniel On Mon, Aug 2, 2010 at 12:43 AM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > Hello, > > After I try making a clean build and got the following error: > > llvm[3]: Compiling EDDisassembler.cpp for

Hello, After I try making a clean build and got the following error: llvm[3]: Compiling EDDisassembler.cpp for Release build In file included from /llvm/include/llvm/Target/TargetSelect.h:38, from /llvm/lib/MC/MCDisassembler/EDDisassembler.cpp:37: /llvm/stage1/include/llvm/Config/AsmPrinters.def: In function ‘void LLVMInitializeX86TargetAsmPrinter()’:

...ker when creating an executable. The UsedComponents variable originates in this case from bindings/ocaml/executionengine/Makefile: LEVEL := ../../.. LIBRARYNAME := llvm_executionengine DONT_BUILD_RELINKED := 1 UsedComponents := executionengine jit interpreter native UsedOcamlInterfaces := llvm llvm_target include ../Makefile.ocaml I don't see anything obviously wrong here; it seems that llvm-config - ldflags executionengine jit interpreter native should be invoked, which should give you the -cclib -lffi you seek. make VERBOSE=1 and/or TOO_VERBOSE=1 should show you the full ocaml command l...

...my plugin any differently. I'm using > cmake's 'add_library(name SHARED ...)' to create the plugin like so: > > add_library(reflector SHARED ${REFLECT_SOURCES} ${COMMON_HEADERS} > ${REFLECT_HEADERS}) > target_link_libraries(reflector > linker_common > ${LLVM_TARGET} > ${LLVM_CORE} > ${LLVM_SUPPORT} > ${LLVM_SYSTEM} > ) > > > Any advice on this? > Still trying to puzzle this one out...what I think I need is to link my plugin such that it doesn't include the LLVM libs in the plugin, but only refer to them as external...

I have an issue with the OCaml build system and the ExecutionEngine. PR2128 has a patch to change the Interpreter to use libffi. This breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't try to link with libffi, even though llvm-config knows that we should: $ Debug/bin/llvm-config --ldflags interpreter -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm

...tree (ie move the source into my own subtree), I run into problems. When I try to build (ocamlbuild toy.byte) after moving the llvm_* .cma, .cmo. .cmx .cmxa and .a into the local directory, I get the following error. + /usr/local/bin/ocamlc.opt llvm.cma llvm_analysis.cma llvm_executionengine.cma llvm_target.cma llvm_scalar_opts.cma -cc clang++ ast.cmo token.cmo parser.cmo codegen.cmo lexer.cmo toplevel.cmo toy.cmo bindings.o -o toy.byte clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated ld: library not found for -lllvm_scalar_opts clang: error: li...

...as in this: /opt/local/bin/ocamlopt -cc g++ -pp camlp4of -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/Release+Asserts/lib/ocaml llvm.cmxa llvm_analysis.cmxa llvm_executionengine.cmxa llvm_target.cmxa llvm_scalar_opts.cmxa -o /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts/OCaml-Kaleidoscope-Ch7 /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts/ast.cmx /Users/erickt/Projects/llvm/gc...

On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to