search for: small_problem_size

...canf on that "numbers" file. > > Is my version of spec wrong ? What you say is true in the version I have. > If not, can we apply the attached patch ? I don't think it's ideal. There are 3 input sets, not 2, that's the root of the problem: ifndef RUN_TYPE ifdef SMALL_PROBLEM_SIZE RUN_TYPE := test else ifdef LARGE_PROBLEM_SIZE RUN_TYPE := ref else RUN_TYPE := train endif endif endif 100 is a fine value for "train". I think it's better to test both variables in the mesa Makefile. (IMO controlling a ternary variable with 2 booleans is not the right way to...

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 host. Personally, I just NFS mount m...

Hello folks, The makefile for 177.mesa says that for a small problem size, it will get 100 frames. But in the spec sources I have, the test folder only contains numbers for 10 frames: $ speccpu2000/benchspec/CFP2000/177.mesa/data $ wc -l test/input/numbers 10 test/input/numbers Generating 100 frames causes undefined behaviour because the program is doing unchecked fscanf on that

...unning: 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" 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...

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

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,

...rovements: 33. Anton and Reid are working to migrate from CVS to SVN in June: See http://llvm.org/SVNMigration.html This will allow us to host llvm-gcc and llvm in the same repository again! 34. Lauro contributed support to llvm-test for running on low-memory or slow machines (make SMALL_PROBLEM_SIZE=1). 35. Jeff contributed many portability fixes to the llvm-test testsuite, and has done a great job keeping llvm itself building with MS Visual Studio. In addition to the features above, this this release also includes hundreds of bug fixes, minor optimization improvements, compile-ti...

...er Improvements: x. Anton and Reid are working to migrate from CVS to SVN in June: See http://llvm.org/SVNMigration.html This will allow us to host llvm-gcc and llvm in the same repository again! x. Lauro contributed support to llvm-test for running on low-memory or slow machines (make SMALL_PROBLEM_SIZE=1). x. Jeff contributed many portability fixes to the llvm-test testsuite, and has done a great job keeping llvm itself building with MS Visual Studio. ... outro In addition to the features above, this this release also includes hundreds of bug fixes, minor optimization improvements, co...