search for: targets_to_build

...ried building LLVM 2.1 with no real target CPU backends enabled, just the C backend, by hacking the configure script slightly: --- /home/foad/llvm/llvm-2.1/configure 2007-09-17 22:37:52.000000000 +0100 +++ configure 2007-12-13 10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD" +TARGETS_TO_BUILD="CBackend" TARGETS_TO_BUILD=$TARGETS_TO_BUILD It didn't work. I get these link failures: make[2]: Entering directory `/home/foad/svn/antix/toolchain/trunk/toolchain/obj/llvm-obj/tools/llc' llvm[2]: Linking Debug ex...

...modified to register new target with LLVM infrastructure: ============================================================================= 1) llvm/configure 1.1) Rx-*) llvm_cv_target_arch="RX" ;; 1.2) Rx) TARGET_HAS_JIT=0 1.3) case "$enableval" in all) TARGETS_TO_BUILD="X86 Sparc PowerPC Alpha ARM Mips CellSPU XCore MSP430 SystemZ Blackfin CBackend CppBackend MBlaze PTX Rx" ;; 1.4) Rx) TARGETS_TO_BUILD="Rx $TARGETS_TO_BUILD" ;; 1.5) Rx) TARGETS_TO_BUILD="Rx $TARGETS_TO_BUILD" ;; 2) lib/Support/Triple.cpp 2.1) cas...

...g configuring: $ ../llvm/configure --enable-targets=x86,x86_64,coldfire ... ... ... checking whether byte ordering is bigendian... no configure: error: Unrecognized target coldfire configure: error: ../../../llvm/projects/sample/configure failed for projects/sample I've added ColdFire to : 1) TARGETS_TO_BUILD variable 2) 'case "$a_target" in' 3) 'case "$llvm_cv_target_arch" in' 4) 'case $target in' 5) to 'case $host in' but it looks like more changes are needed. Could someone, please, advise me? -- Regards, Vadim. -------------- next part -------...

...c 4.8.5 to compile LLVM ~8.0.1-rc2 on CentOS 7 AMD64 not long ago, > which worked ok. That was using cmake, with these specific options (in case > that's useful): I’ve installed it successfully on both x86 and ARM. It’s only on POWER9 (ppc641e) that it fails. That one is not in your TARGETS_TO_BUILD list, alas. Thanks, Marty > > $ mkdir $HOME/local/source > $ cd $HOME/local/source > $ git clone -b release/8.x https://github.com/llvm/llvm-project <https://github.com/llvm/llvm-project> > $ mkdir build > $ cd build > > $ cmake \ > -G Ninja \ > -...

I am trying to build cross compiler for custom processor (say XYZ) but on compilation it is giving error llvm-build: error: invalid native target: XYZ (not in project) I have tried configuring like these 1. ./configure --target=XYZ 2. ./configure --target=XYZ --enable-targets=XYZ 3. ./configure --enable-targets=XYZ But every time it is not recognising the XYZ processor. What could be the

You need to add your target to autoconf/configure.ac. Here are the directions from http://llvm.org/docs/WritingAnLLVMBackend.html To get LLVM to actually build and link your target, you need to add it to the TARGETS_TO_BUILD variable. To do this, you modify the configure script to know about your target when parsing the --enable-targets option. Search the configure script for TARGETS_TO_BUILD, add your target to the lists there (some creativity required), and then reconfigure. Alternatively, you can change autotools/co...

...ts=x86,x86_64,coldfire > ... > ... > ... > checking whether byte ordering is bigendian... no > configure: error: Unrecognized target coldfire > configure: error: ../../../llvm/projects/sample/configure failed for > projects/sample > > I've added ColdFire to : > 1) TARGETS_TO_BUILD variable > 2) 'case "$a_target" in' > 3) 'case "$llvm_cv_target_arch" in' > 4) 'case $target in' > 5) to 'case $host in' > > but it looks like more changes are needed. > > Could someone, please, advise me? > Did yo...

I'm experimenting with a new backend, hoping to build a cross compiler, and reading "Writing an LLVM Compiler Backend". Early on, in "Preliminaries", it suggests editing my configure script to add my new target to the TARGETS_TO_BUILD variable, suggesting some creativity may be required. I'm perhaps not creative enough, 'cause I can't get it to work. I tried a couple of variations (one seemed straightforward; in the other, I went through looking for every example of Sparc to see how they did it and making the approp...

...;> ... >> ... >> checking whether byte ordering is bigendian... no >> configure: error: Unrecognized target coldfire >> configure: error: ../../../llvm/projects/sample/configure failed for >> projects/sample >> >> I've added ColdFire to : >> 1) TARGETS_TO_BUILD variable >> 2) 'case "$a_target" in' >> 3) 'case "$llvm_cv_target_arch" in' >> 4) 'case $target in' >> 5) to 'case $host in' >> >> but it looks like more changes are needed. >> >> Could someone, pl...

Hello, I have tried a lot fix this error but am not able to can you please find me a solution am trying to compile the SAFECode in Cygwin Environment to work for windows. used make -j4 command to make the files in cygwin i have got this error make[5]: Leaving directory '/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include' /usr/bin/cp: cannot stat

...I assume copying files from that directory is a good starting point. I have tried a trivial build of a new target based on ARM by copying all the ARM target files to a new directory and changing names of files in the code to create a "new" target. After adding the new target to the TARGETS_TO_BUILD list in "configure", I was able to "make" a new build that included the new target. Of course it is just a copy of the ARM target at this stage but it confirms I have grasped the basics of the LLVM tree and build process. My concern is that, if there is a new release of LLV...

...--enable-proc-self-exe. Use "yes" or "no"]) ;; +esac +AC_DEFINE_UNQUOTED([ENABLE_PROC_SELF_EXE],$ENABLE_PROC_SELF_EXE, + [Define if reading of the "/proc/self/exe" link is allowed]) + dnl Allow specific targets to be specified for building (or not) TARGETS_TO_BUILD="" AC_ARG_ENABLE([targets],AS_HELP_STRING([--enable-targets], I'll commit after a LGTM. However before tweaking lib/Support/Unix/Path.inc I have to add a cmake modification, which can be simply <always on>. Hints how to do this are welcome, but I guess I'll figure it out...

..."yes" or "no"]) ;; > +esac > +AC_DEFINE_UNQUOTED([ENABLE_PROC_SELF_EXE],$ENABLE_PROC_SELF_EXE, > + [Define if reading of the "/proc/self/exe" link is allowed]) > + > dnl Allow specific targets to be specified for building (or not) > TARGETS_TO_BUILD="" > AC_ARG_ENABLE([targets],AS_HELP_STRING([--enable-targets], > > > I'll commit after a LGTM. > > However before tweaking lib/Support/Unix/Path.inc I have to add a cmake > modification, which can be simply <always on>. Hints how to do this are > welc...

...t;>I registered my target through >>RegisterTarget<XccTargetMachine> X("xcc", "XCC"); >>in XccTargetMachine.cpp. Your response: Make sure that the library is being linked into your tool. This requires adding code to llvm/autoconf/configure.ac (search for TARGETS_TO_BUILD, add yours). Then regenerate configure, then rerun configure, then rebuild llc.

Le 16 déc. 2009 à 10:54, Mark Muir a écrit : > Hi all, > > I'm developing a custom back-end for an odd-ball architecture (but one that is still describable by LLVMTargetMachine). The toolchain that it will fit into doesn't have a linker as such, so I want to use assembly as the default output. I've got to the point of emitting working custom assembly for very simple C

...N: llc %t.ll -O0 -march=x86 -o %t.s // RUN: FileCheck < %t.s %s // CHECK: fct unsigned int fct(unsigned int n) { if(n>0) return fct(n-1)*n; else return 1; } /* end example.c */ /* lit.local.cfg */ config.suffixes = ['.c', '.cpp', '.ll'] targets = set(config.root.targets_to_build.split()) if not 'VPU' in targets: config.unsupported = True /* end lit.local.cfg */ 2012/8/28 Changcheng Wang <changcheng at multicorewareinc.com>: > hi,yang: > thanks for your help! > my net is so poor that i can not donwload your attachment. > would you like to pas...

> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 08 July 2015 19:01 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); Eric Christopher > (echristo at gmail.com); Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 8 July 2015 at 17:43, Daniel Sanders

...nsigned int n) { >> if(n>0) return fct(n-1)*n; >> else return 1; >> } >> /* end example.c */ >> >> >> /* lit.local.cfg */ >> config.suffixes = ['.c', '.cpp', '.ll'] >> >> targets = set(config.root.targets_to_build.split()) >> if not 'VPU' in targets: >> config.unsupported = True >> /* end lit.local.cfg */ >> >> >> 2012/8/28 Changcheng Wang <changcheng at multicorewareinc.com>: >>> hi,yang: >>> thanks for your help! >>> my net is...

...lvm 2.5' PACKAGE_TARNAME='-llvm-' PACKAGE_VERSION='2.5' PATH_SEPARATOR=':' PERL='' POD2HTML='' POD2MAN='' RANLIB='' RM='' RUNTEST='' SED='' SHELL='/bin/sh' SHLIBEXT='' STRIP='' TAR='' TARGETS_TO_BUILD='' TARGET_HAS_JIT='' TCLSH='' USE_UDIS86='' YACC='' YFLAGS='' ZIP='' ac_ct_CC='gcc' ac_ct_CXX='' ac_ct_F77='' bindir='${exec_prefix}/bin' build='powerpc-apple-darwin8.11.0' build_alias='' build_c...