search for: target_has_jit

...to add remote execution >support to the tests. That explains why MCJIT test executable (build/unittests/ExecutionEngine/MCJIT/MCJITTests) was an X86 binary in my case. It appears to me that these tests will always fail for cross-compilation unless modified for remote execution. I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to exclude MCJIT and JIT tests when not set? This will be a simpler change than modifying the macro. Thanks, Jyotsna

On 2013-03-13 3:15 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote: > >I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to >exclude MCJIT and JIT tests when not set? This will be a simpler change >than >modifying the macro. > >Thanks, >Jyotsna TARGET_HAS_JIT seems to be an autoconf thing (also, not really sure how it works) and has no equivalent...

On Thu, 2004-12-23 at 12:35, Markus F.X.J. Oberhumer wrote: > Yes, but "TARGET_HAS_JIT" seems to be unused, so what is this for ? projects/llvm-test/Makefile.programs:175:ifdef TARGET_HAS_JIT projects/llvm-test/Makefile.programs:182:endif#TARGET_HAS_JIT projects/llvm-test/LLVMSource/Makefile:22:ifdef TARGET_HAS_JIT projects/llvm-test/SingleSource/CustomChecked/Makefile:27:ifdef...

...can't commit this because it will break the LLVM makefile system. > fi > > dnl --enable-jit: check whether they want to enable the jit > @@ -180,9 +181,9 @@ > AC_SUBST(JIT,[[]]) > else > case "$llvm_cv_target_arch" in > - x86) AC_SUBST(JIT,[[TARGET_HAS_JIT=1]]) ;; > - Sparc) AC_SUBST(JIT,[[TARGET_HAS_JIT=1]]) ;; > - PowerPC) AC_SUBST(JIT,[[TARGET_HAS_JIT=1]]) ;; > + x86) AC_SUBST(JIT,[[1]]) ;; > + Sparc) AC_SUBST(JIT,[[1]]) ;; > + PowerPC) AC_SUBST(JIT,[[1]]) ;; I can't make these changes for the same reason...

...9;ed somewhere ? We use it like this: @ENABLE_OPTIMZED@ in a makefile so it expands to a line of: ENABLE_OPTIMIZED=1 Weird, I know, but it works. The point is, we don't want the makefile variable even defined if it has no value so this strategy works. > Again, this expands to "JIT=TARGET_HAS_JIT=1", and I've grepped over > the llvm source tree and found that "TARGET_HAS_JIT" is never used ?? Same usage in the makefiles as described above. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature...

...x/ --enable-languages=c,c++ make make install File(s) that I have 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=&quo...

On 2013-03-12 1:28 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote: >Thanks Dan! > >The ArchSupportMCJIT() functions in >unittests/ExecutionEngine/MCJIT/MCJITTestBase.h uses "Host Triple" to >check >for compatibility. Since we cross-compile on X86, "Host Triple" for us >will >be "X86" which is a supported architecture. I

Thanks Dan! The ArchSupportMCJIT() functions in unittests/ExecutionEngine/MCJIT/MCJITTestBase.h uses "Host Triple" to check for compatibility. Since we cross-compile on X86, "Host Triple" for us will be "X86" which is a supported architecture. I tried removing it from the supported arch list but didn't see any effect. I was just wondering if these tests are

...='-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_cpu='powerpc' build...

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,

...> # > #VERBOSE = 1 > > # When ENABLE_PURIFY is set to 1, the LLVM tools are linked with purify (which > # must be locally installed) to allow for some automated memory error debugging. > # > #ENABLE_PURIFY = 1 > > > # > # Enable JIT for this platform > # > TARGET_HAS_JIT=1 > > # > # Disable LLC diffs for testing. > # > > > ########################################################################### > # Directory Configuration > # This section of the Makefile determines what is where. To be > # specific, there are several locations t...

...39;:' > 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' > b...

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

> > 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