search for: compiler_rt_emulator

On 22 August 2014 01:48, Jim Grosbach <grosbach at apple.com> wrote: > No specific comments at the moment, but I do want to say that I very much believe this is worth pursuing. Better testing infrastructure for remote targets will be an absolutely fantastic improvement. Thank you and Dan both for pushing forward on the topic. +1 I remember Greg (cc'd) did some of that in

...r/compiler-rt/blob/master/test/asan/TestCases/atexit_stats.cc > > > and substituted '%run' with 'config.emulator' in the lit configuration file: > > https://github.com/llvm-mirror/compiler-rt/blob/master/test/lit.common.cfg > > > which is set via CMake option COMPILER_RT_EMULATOR: > > https://github.com/llvm-mirror/compiler-rt/blob/master/test/lit.common.configured.in > > > To configure the build to use QEMU (or adb, scp, etc): > > $ cmake -DCOMPILER_RT_EMULATOR=qemu-aarch64 > > If you need additional parameters, you can either add them to the &gt...

...t; In compiler-rt, I'd configure such a build with the following CMake variables: I'm not sure we're on the same page... Your example, and the way that lit is currently set up, assumes BUILD and HOST are the same machine. > LLVM_LIT=$BUILD/lit > CMAKE_C_COMPILER=$HOST/clang > COMPILER_RT_EMULATOR=$TARGET/qemu Let me give a concrete example: BUILD=i686-pc-linux-gnu HOST=i386-pc-win32 TARGET=arm-elf (on say, real hardware, or i686-pc-linux/bin/qemu-system-arm, or i386-pc-win32/bin/qemu-system-arm) Here I'd like to run lit on the linux machine such that test compilation happens on the...

On 9/8/14, 12:39 PM, Greg Fitzgerald wrote: > Hi Jon, > > Compiler-rt, libcxx, libcxxabi should all use the same > cross-compilation testing strategy. Compiler-rt already has a working > solution. If it is inadequate for libcxx or libcxxabi, can we start > by addressing those deficiencies? One issue to start with is that none of the libcxx/libcxxabi tests have RUN lines. All

...default blacklist tests. I had to move those into the clang test suite. As for cross-compilation and test ARM Linux, I needed to update all tests to include '%sim' before invoking cross-compiled executables. For x86, the variable is empty. For cross-compiling, it's a user-configured ${COMPILER_RT_EMULATOR}, which for ARM Linux, is QEMU. There are currently a handful of test failures. If you'd like, I can XFAIL them and commit this stuff sooner than later. Do you want these patches? -Greg On Fri, Apr 4, 2014 at 10:22 AM, Greg Fitzgerald <garious at gmail.com> wrote: >>>> i...

...bs and tools. > >> >> >> As for cross-compilation and test ARM Linux, I needed to update all >> tests to include '%sim' before invoking cross-compiled executables. >> For x86, the variable is empty. For cross-compiling, it's a >> user-configured ${COMPILER_RT_EMULATOR}, which for ARM Linux, is QEMU. >> There are currently a handful of test failures. If you'd like, I can >> XFAIL them and commit this stuff sooner than later. > > > This looks familiar to what Evgeniy did for running lit test suite on > Android. This is now possible &g...

On Thu, Apr 3, 2014 at 9:23 PM, Greg Fitzgerald <garious at gmail.com> wrote: > > I don't think it's a good idea to let user hijack > > the driver and stuff in custom version of > > ASan runtime instead the one installed/built > > with compiler :) > > I'm okay with it. This is open source. If someone wants to put the > sanitizers on a shorter