search for: target_cc

...nts on the following command: make -k TEST=simple ARCH=ARM TARGET_FLAGS="-arch armv7 -isysroot path-to-sdk -ccc-install-dir path-to-binutils" USE_REFERENCE_OUTPUT=1 REMOTE_HOST=localhost REMOTE_USER=root REMOTE_CLIENT=ssh REMOTE_PORT=10022 DISABLE_JIT=1 DISABLE_CBE=1 SMALL_PROBLEM_SIZE=1 TARGET_CC=path-to-clang TARGET_CXX=path-to-clang++ report That assumes key-based ssh authentication (so you don't get password prompted for every execution) and that the test suite directory is is mounted on the target at the same pathname as it is on the host. Personally, I just NFS mount my home direc...

The issues seems to be this line in the tools Makefile timeit-target: timeit.c $(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS) $(TARGET_FLAGS) -O3 It should not add target flags if we are simulating the target on the host. On 06/06/2013 06:59 PM, reed kotler wrote: > I want to get lnt to use qemu for the execution. > > In that case, RHOST= is not set. > > But I

Hi all, I'm working in a company to port LLVM on their own processor. I'm trying to run the test-suite, but it seems that it is usually run directly on the processor which is tested. In my case, I cannot run it on the processor, but I have a simulator on which I would like to run the test-suite. Also, it seems to me that the test-suite start by compiling some tools that have to be run

I want to get lnt to use qemu for the execution. In that case, RHOST= is not set. But I change the Arch because I am going to run in cross mode. Then I'm setting RUNUNDER to be a script which runs qemu. In this case it builds timeit-target as a Mips which fails because this is running on x86. ~/mysandbox/bin/lnt runtest nt --sandbox ~/mysandbox --cc /local/llvmpb_a/install/bin/clang

...6_64 CC_UNDER_TEST_IS_CLANG=1 CC_UNDER_TEST_TARGET_IS_X86_64=1 DISABLE_CBE=1 DISABLE_JIT=1 ENABLE_HASHED_PROGRAM_OUTPUT=1 ENABLE_OPTIMIZED=1 LD_ENV_OVERRIDES="env DYLD_LIBRARY_PATH=/path/to/your/build/Release+Asserts/lib" LLC_OPTFLAGS=-O3 LLI_OPTFLAGS=-O3 OPTFLAGS=-O3 SMALL_PROBLEM_SIZE=1 TARGET_CC="" TARGET_CXX="" TARGET_FLAGS="-arch x86_64" TARGET_LLVMGCC=/path/to/your/build/Release+Asserts/bin/clang TARGET_LLVMGXX=/path/to/your/build/Release+Asserts/bin/clang++ TEST=simple USE_REFERENCE_OUTPUT=1 report ***Note the ENABLE_OPTIMIZED=1 flag requires that you run...

> > 1. I checked out and built llvm, clang, and test-suite from svn tip. > When I > > run llvm/test *without* my changes on x86, I see 3 failures. Is it > expected? > > I was expecting svn tip on x86 to be clean. Is there a nightly > regression > > result available somewhere that I can check for broken tests. Here is > the > > report from my log: > >

Hi Raul, I've successfully run them over ssh using LNT without too much difficulty. There is documentation on getting started with the LNT system here: http://llvm.org/docs/lnt/quickstart.html. It doesn't specifically mention remote execution, but if you give the lnt command a "--help" option then there are a few reasonably self-explanatory options described (--remote,

...l and only copies the reference_output to the out-nat file. if you look at the first line of your log 2013-03-12 15:19:41: running: "make" "-k" "TARGET_LLVMGCC=/home/rengolin/devel/llvm/build/bin/clang" "TARGET_CXX=None" "LLI_OPTFLAGS=-O3" "TARGET_CC=None" "TARGET_LLVMGXX=/home/rengolin/devel/llvm/build/bin/clang++" "TEST=simple" "CC_UNDER_TEST_IS_CLANG=1" "ENABLE_PARALLEL_REPORT=1" "TARGET_FLAGS=" "USE_REFERENCE_OUTPUT=1" "CC_UNDER_TEST_TARGET_IS_X86_64=1" "OPTF...

On 12 March 2013 16:21, Duncan Sands <baldrick at free.fr> wrote: > IIRC the reference output is not used by default. You have to put > USE_REFERENCE_OUTPUT := 1 > in the Makefile in order to make use of the reference output. As > BenchmarkGame doesn't have this, are you sure the reference output > is causing the problem? > That was my initial assumption, too. But

Hello, is there any option to run LLVM unit tests on ARM from your desktop? I mean, the code is properly cross-compiled on your desktop and you want to run the unit tests automatically on an ARM board. Chrood might work, but I am looking for some option like <runremote.sh --host XXX --user ....>. I have seen something related to it in projects/test-suite/Makefile.programs (REMOTE_HOST,