search for: target_triple

...had a test case failure in test/LTO/X86/current-section.ll, which has module asm, but no target triple. However, it does have a "REQUIRES: default_triple". Mehdi, looks like you added this as part of D12660. I found that this is set to true in test/lit.cfg, and when I print out the config.target_triple there it is x86_64-unknown-linux-gnu. But when I print out the target triple on the Module in CollectAsmUndefinedRefs it is null. How is the config.target_triple supposed to propagate into the test - I assume that is the intention of requiring a default_triple? Thanks, Teresa -- Teresa Johnson |...

...ader in windows with "Visual Studio 12" generator. My cmake configuration goes like >> Set path, include and lib environment variables to point to zlib headers and libraries. Cmake version is 2.8.12.2 cmake -G "Visual Studio 12" -D LLVM_TARGETS_TO_BUILD:STRING=%TARG% -D TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_DEFAULT_TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_TARGET_ARCH:STRING=%TRIPLE% -D LLVM_ENABLE_PIC:BOOL=ON -D LLVM_ENABLE_ASSERTIONS:BOOL=ON -D CMAKE_INSTALL_PREFIX=%win_top_install_dir% -D CMAKE_BUILD_TYPE=%BLDMODE% -DLLVM_APPEND_VC_REV:BOOL=ON -D LLVM_VENDOR_NAME:STRING=%NAME% -...

Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

Is there a simple way to override the target triple used in when running the generic codegen tests? I would expect that passing a value for TARGET_TRIPLE to make, as below, would do it but none of the tests appear to use the target_triplet variable generated in site.exp. > make TESTSUITE=CodeGen/Generic TARGET_TRIPLE=msp430-none-none check -Ken

720beaedce6f19c81156fe20168f85989a8db53d CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index bb70f15..e327427 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -249,7 +249,7 @@ set(LLVM_DEFAULT_TARGET_TRIPLE "${LLVM_HOST_TRIPLE}" CACHE STRING set(TARGET_TRIPLE "${LLVM_DEFAULT_TARGET_TRIPLE}") include(HandleLLVMOptions) - +set(Python_ADDITIONAL_VERSIONS 2.7 2.6 2.5 2.4) # Verify that we can find a Python interpreter, include(FindPythonInterp) if( NOT PYTHONINTERP_FOUND ) --...

...hat they are not setting LLVMGCCDIR and instead relying on finding llvm-gcc on the PATH. Or, perhaps they are setting LLVMGCCDIR to the prefix directory and the script's attempt to invoke "$LLVMGCCDIR/llvm-gcc" fails in a non-fatal way (it appears to be used only to set "target_triple" in the results). Anyway, here's my proposed patch. -------------- next part -------------- A non-text attachment was scrubbed... Name: nightlytest.patch Type: application/octet-stream Size: 419 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/200903...

Still no complete go, doing the tests on i386 failed with some weird sed error: [...] Making Unit/lit.site.cfg for Clang extra tools... sed: lit.tmp: No such file or directory Makefile:61: recipe for target 'Unit/lit.site.cfg' failed gmake[2]: *** [Unit/lit.site.cfg] Error 1 Strangely enough, this does not happen on amd64. Maybe it is some sort of race condition? Did anybody see this

Dear all, Recently I've considering using LIT for my benchmark testing framework, and the only reference for LLVM-LIT is the man page and some READMEs. I don't find any documentations on config, which seems to be quite important to the tool. If I use lit outside LLVM source tree and use on my own test files, LIT marks them as 'unresolved'. So are there any documentations I can

...test should run because they could produce unexpected successful result. Up to me, we should deprecate XTARGET, if XFAIL accepts <condition>. * We can extend declarative language to define variables. In this case $each_target could be a test variable instead of a pre-defined placeholder. * target_triple is actually the host_triple. Shell we rename it? Thanks Galina

...i', lli ) ) +config.substitutions.append( ('%filter-txt-comments', + 'sed \'s/^;.*$//\'') ) + # Similarly, have a macro to use llc with DWARF even when the host is win32. llc_dwarf = 'llc' if re.search(r'win32', config.target_triple): ... ] > (I didn't include this in my recent FileCheck Follies lightning talk, +1 viewcount. > because testing FileCheck itself is kind of an obscure corner of the > LLVM world and I was already bumping up against the 5-minute time limit.) > --paulr > > >> -----Origi...

...see invocation) makefile:33: recipe for target 'main' failed make: *** [main] Error 1 2) To get clang_rt.builtins-armv6m.a or libc, libm, I tried to build LLVM/Clang (compiler_rt) from LLVM/Clang source following this - http://llvm.org/docs/HowToCrossCompileLLVM.html but I got this error, TARGET_TRIPLE=arm-none-eabi MYHOSTBIN=${HOME}/clang/source/build_x64/bin MYGNUARM_ROOT=${HOME}/opt/gcc-arm-none-eabi-6-2017-q2-update MYCFLAGS="--specs=nosys.specs -mcpu=cortex-m4 -mthumb -mfloat-abi=softfp -mfpu=fpv4-sp-d16" cmake -G "Ninja" \ -DCMAKE_CROSSCOMPILING=True \...

...titutions.append( ('%filter-txt-comments', > + 'sed \'s/^;.*$//\'') ) > + > # Similarly, have a macro to use llc with DWARF even when the host is > win32. > llc_dwarf = 'llc' > if re.search(r'win32', config.target_triple): > ... > ] > > > (I didn't include this in my recent FileCheck Follies lightning talk, > > +1 viewcount. > > > because testing FileCheck itself is kind of an obscure corner of the > > LLVM world and I was already bumping up against the 5-minute time >...

It is $target dependent. I’m curious what makes you think it is $host dependent. Thanks, Taewook On 3/3/17, 5:10 PM, "Jonathan Roelofs" <jonathan at codesourcery.com> wrote: On 3/3/17 12:23 PM, Taewook Oh wrote: > Thanks Jon. Actually I tried “x86_64-linux”, but it makes the test “Unsupported” from my linux machine, and it was because my test is under

Please send patches to llvm-commits not llvm-dev. Writing FileCheck tests has pitfalls. A test along these lines: bla0 CHECK:bla1 will actually pass, because the CHECK pattern is also part of the input so it will readily match itself. You want the CHECK lines not to match themselves, which you can easily do by introducing {{}} into the (middle of the) pattern. That is: bla0 CHECK:{{bla1}}

...t; I would love to do this, but there’s a bug in the backend which causes a few of the Generic CodeGen tests to fail. To work around this, I leave X86 as the default target for now. I’m definitely planning on updating this once I’ve fixed the bug. > > This usually happens when LLVM_DEFAULT_TARGET_TRIPLE is not explicitely set and you end up with your host machine as default while not building the x86 target. If you set LLVM_DEFAULT_TARGET_TRIPLE to some AVR ones the failure should go away (otherwise complain and file bugs). - Matthias -------------- next part -------------- An HTML attachment wa...

...quot; +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") +config.host_triple = "@LLVM_HOST_TRIPLE@" +config.target_triple = "@TARGET_TRIPLE@" +config.host_arch = "@HOST_ARCH@" + +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" + + at LIT_SITE_CFG_IN_FOOTER@ + +# Let the main config do the real work. +lit_config.load_config(config, "@DEBUGINFO_TESTS_SOURCE_DIR@/lit.cfg.py") di...

...ot = "@DEBUGINFO_TESTS_BINARY_DIR@" >> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" >> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") >> +config.host_triple = "@LLVM_HOST_TRIPLE@" >> +config.target_triple = "@TARGET_TRIPLE@" >> +config.host_arch = "@HOST_ARCH@" >> + >> +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" >> + >> + at LIT_SITE_CFG_IN_FOOTER@ >> + >> +# Let the main config do the real work. >> +lit_config.loa...

...nfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" > +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" > +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") > +config.host_triple = "@LLVM_HOST_TRIPLE@" > +config.target_triple = "@TARGET_TRIPLE@" > +config.host_arch = "@HOST_ARCH@" > + > +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" > + > + at LIT_SITE_CFG_IN_FOOTER@ > + > +# Let the main config do the real work. > +lit_config.load_config(config, "@DEBUGINF...

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,

Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently in lit you can set a global timeout for all of the tests but