search for: disable_jit

...ects > subdirectory, checked out test-suite. Then reran the top-level > configure. Then went into the projects/test-suite subdirectory and ran: > make TEST=nightly report report.html (as suggested on the web page). And > this is what happened. What should I be doing? Pass DISABLE_CBE=1 DISABLE_JIT=1 to the make line. More generally, you should really be using TEST=simple rather than TEST=nightly. It more accurately recreates an end-user's compiler flow, and doesn't try to test known-broken things like the CBE. --Owen

I use variants 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 h...

On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote: > On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > I'm just setting up the test suite, and I'm seeing a lot of failures > > from main() not returning int, etc. in some of the tests. Is this > > normal? > > > > For example: > >

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

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

...being used? >> >> Very possible the documentation needs updating. > > I see. Do you run projects/test-suite with clang? > >From your build/project/test-suite directory, try running: make ARCH=x86_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" TAR...

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

Hello, I'm trying to add some tests from PARSEC to MultiSource, and I can't figure out how to disable the lli and cbe backends. Because the code uses inline assembly, only the llc backend works. Does anyone know how to do this? Thanks, --Patrick -- If I'm not here, I've gone out to find myself. If I get back before I return, please keep me here.

If you disable them at configure time, they won't be run. You probably want: --enable-targets=host --disable-jit Reid On Sat, Jul 10, 2010 at 8:56 PM, Patrick Simmons <simmon12 at illinois.edu> wrote: > Hello, > > I'm trying to add some tests from PARSEC to MultiSource, and I can't > figure out how to disable the lli and cbe backends.  Because the code > uses

I'm sorry; I should have been more clear. I mean, for instance, run a test but only with, say, llc, not with lli or cbackend. Thanks, --Patrick Dale Johannesen wrote: > > On Jul 25, 2010, at 2:37 AMPDT, Patrick Simmons wrote: > >> Thanks, Dale, that really helps. >> >> What about disabling only one backend of a specific test? >> >> Thanks, >>

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,

...t;ENABLE_PARALLEL_REPORT=1" "TARGET_FLAGS=" "USE_REFERENCE_OUTPUT=1" "CC_UNDER_TEST_TARGET_IS_X86_64=1" "OPTFLAGS=-O3" "LLC_OPTFLAGS=-O3" "ENABLE_OPTIMIZED=1" "ARCH=x86_64" "ENABLE_HASHED_PROGRAM_OUTPUT=1" "DISABLE_JIT=1" "-C" "SingleSource/Benchmarks/BenchmarkGame" "-j" "8" "report" "report.simple.csv" then you see that it forces USE_REFERENCE_OUTPUT=1. Maybe LNT does that? Ciao, Duncan. > > I then copied a "good" output to the...

> BTW, how can I run all tests only on LLC to reduce the amount of time to > wait until tests are finished, if it's possible? In my previous reply to your question, I suggested you look at TEST.llc.Makefile and TEST.llc.report in the test directory. Modifying those makefile/report files to use your register allocator will do what you want. -Tanya

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

Hi again! I've managed to run the llvm-test with the options Fernando told. What I did was the following: I changed llc regalloc option in TEST.llc.makefile to my allocator. I changed LLCBETAOPTION in makefile.programs file for all architechtures to use my allocator. I run make TEST=nightly report.html and got all tests under LLCBETA failed ('*' symbol). Though I know that my

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,

...Modifying > those makefile/report files to use your register allocator will do what > you want. Tanya's right, if you want full control over what is being run, you should write your own test script. If you really really want to use the nightly tester script, you can pass DISABLE_CBE=1 DISABLE_JIT=1 on the make command line to disable those runs. If the test output claims that llc-beta fails, then your register allocator is producing incorrect code. In a multisource directory, if you use 'make bugpoint-llc-beta' in some failing test directory, bugpoint will automatically reduce...