search for: host_arch

Hi, > LLVM :: ExecutionEngine/test-shift.ll > > Any ideas? Those tests are for the old JIT, and shouldn't be run at all on PowerPC. The host_arch field in your lit.site.cfg (somewhere in the build directory) is probably being set incorrectly. I've seen this when LLVM is cross-compiled with CMake before. I had to set CMAKE_SYSTEM_PROCESSOR in my toolchain file (in your case to "PowerPC"). But your situation could be completely...

Hi, I got multiple failures on PowerPC64, crashes are the same: [ 1346s] 0 lli 0x00000000107bca00 [ 1346s] 1 lli 0x00000000107bcd14 [ 1346s] 2 lli 0x00000000107bcfb8 [ 1346s] 3 linux-vdso64.so.1 0x00000fff850f0418 __kernel_sigtramp_rt64 + 0 [ 1346s] 4 lli 0x00000000100bdc98 [ 1346s] 5 lli 0x00000000102f40d0 [ 1346s] 6

Hi Renato, As far as I understand, such issues should be caught by the tests in compiler-rt/test/xray/TestCases/Linux. I found the following lines in compiler-rt/test/xray/lit.cfg that seem to disable the tests for non-64-bit targets: if config.host_os not in ['Linux'] or config.host_arch.find('64') == -1: config.unsupported = True @Serge: You will need to change this condition to enable the tests for ARM. Oleg ________________________________________ From: Renato Golin <renato.golin at linaro.org> Sent: Monday, January 9, 2017 11:50 PM To: Serge Rogatch Cc: Dean...

...ar as I understand, such issues should be caught by the tests in compiler-rt/test/xray/TestCases/Linux. >> I found the following lines in compiler-rt/test/xray/lit.cfg that seem to disable the tests for non-64-bit targets: >> >> if config.host_os not in ['Linux'] or config.host_arch.find('64') == -1: >> config.unsupported = True >> >> @Serge: You will need to change this condition to enable the tests for ARM. >> >> Oleg >> >> ________________________________________ >> From: Renato Golin <renato.golin at linaro.org&gt...

Sharing with the mailing list... Please, see below. On 9 January 2017 at 23:45, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hi Dean, > > I have seen that you removed the following code from ARMAsmPrinter.cpp in > revision 290858: > // Emit the XRay table for this function. > EmitXRayTable(); > > Was this done by mistake or on purpose? > > Without

...-b usb_linux.c usb_linux.c.patch > > cd ../../.. > > make adb > build/core/product_config.mk:261: WARNING: adding test OTA key ============================================ TARGET_PRODUCT=generic TARGET_BUILD_VARIANT=eng TARGET_SIMULATOR= TARGET_BUILD_TYPE=release TARGET_ARCH=arm HOST_ARCH=x86 HOST_OS=linux HOST_BUILD_TYPE=release BUILD_ID= ============================================ /bin/bash: line 0: cd: dalvik/libcore//mnt/home/ganci/download/android//dalvik/libcore:/ No such file or directory /bin/bash: line 0: cd: dalvik/libcore//mnt/home/ganci/download/android//dalvik/libco...

...GINFO_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") diff --git a/test_debuginfo.pl b/test_debuginfo.pl...

...g.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.c...

...uot; > +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 <http://lit.cfg.py/...

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure