search for: runsafely

If you look at http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html then you see that all program test have '*' in run time columns. I think problem in using plain 'time' command in RunSafely.sh At FreeBSD 'time <program> <args>' call generate output in format " 0,00 real 0,00 user 0,00 sys" for *.time files instead expected "real %e user %U sys %S " And later failed at '-grep "^real" Output/$*.out-nat.time >&gt...

Hello everyone, I am working to run the LLVM Nightly Testsuite on embedded arm devices. Not all of these devices can mount NFS to share a common directory tree. To mitigate this I have patched test-suite/RunSafely.sh (attached) to create a temporary directory, run the test remotely, collect the output, and cleanup after itself. The patch breaks compatibility with the current remote device model in the following ways: 1. uses scp/rcp to copy files from the host running test-suite instead of assuming an ident...

I am going to change the LLVM test-suite RunSafely.sh to only track 'user' time, instead of reporting 'user' + 'sys' time as it currently does. This will probably cause a spike in nightly test numbers, although hopefully it will be limited to the smaller tests. The eventual goal is to report all numbers (independently), so...

Daniel Dunbar wrote: > I am going to change the LLVM test-suite RunSafely.sh to only track > 'user' time, instead of reporting 'user' + 'sys' time as it currently > does. This will probably cause a spike in nightly test numbers, > although hopefully it will be limited to the smaller tests. > > The eventual goal is to report all numb...

On Apr 18, 2010, at 11:08 PM, John Criswell wrote: > Second, why are you only interested in user time? The reason why we had > RunSafely.sh measure user + system time is that it gives a more accurate > depiction of how well an optimization works. If a program spends most > of its time in the OS, increasing speed in user-space doesn't gain us > much. If a transform decreases user time but increases system time, &gt...

Dear All, Is the lack of virtual memory limits for Darwin in RunSafely.sh intentional or accidential? What about Cygwin? It seems to me that some of the limits should be applied for all operating system targets. -- John T.

...home/greened/src/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vector' make[5]: Entering directory `/home/greened/src/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vector/SSE' /home/greened/src/llvm-30-rc3/build/projects/llvm-test/../../../llvm/projects/llvm-test/RunSafely.sh 500 0 /dev/null Output/sse.expandfft.llvm.o.compil e \ -I/home/greened/src/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vec...

...P0=7894.33, Q0=1592.81 > > --- > > > TR=0.79, TI=0.16, P0=7894.32, Q0=1592.81 > > This works on Linux (it did last night) so not sure why FreeBSD gives > these rounding errors. Can you investigate? Does the test use fpcmp? It does: /usr/home/llvm/obj/../test/Programs/RunSafely.sh 500 /dev/null Output/power.out-llc Output/power.llc /usr/home/llvm/obj/../test/Programs/DiffOutput.sh "/usr/home/llvm/obj/tools/Debug/fpcmp -r 0.00001" llc power /usr/home/llvm/obj/../test/Programs/RunSafely.sh 500 /dev/null Output/power.out-cbe Output/power.cbe /usr/home/llvm/obj/...

...eck" is done, results are here: http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt Summary: Native configuration is i386-unknown-freebsd6.2 # of expected passes 1988 # of expected failures 3 -=- I'm currently stuck on the nightly report, at this point: /usr/home/emil/llvm-test/RunSafely.sh 500 0 /dev/null Output/tramp3d-v4.out-nat Output/tramp3d-v4.native --cartvis 1.0 0.0 --rhomin 1e-8 -n 25 Ctrl-T tells me that tramp3d-v4.native has by now consumed 50,000 seconds of CPU time. Somehow I don't think it's going to stop anytime soon -- what can I do to break out of this cl...

On Nov 8, 2011, at 7:20 PM, David A. Greene wrote: > I couldn't figure out how to run the test-suite. Are there up-to-date > instructions somewhere? llvm-gcc doesn't exist anymore... Easiest is to check out the test-suite branch into projects and then after you configure and build from the top level, go into build/projects/test-suite and do a 'make TEST=simple report'.

...marray.cbe.c:210: error: incompatible types in assignment Output/sumarray.cbe.c:216: error: incompatible types in assignment Output/sumarray.cbe.c:161: warning: return type of 'main' is not 'int' make[3]: [Output/sumarray.cbe] Error 1 (ignored) /home/jo/Delta/llvm/projects/llvm-test/RunSafely.sh 500 0 /dev/null Output/multiplies.out-llc Output/multiplies.llc /home/jo/Delta/llvm/projects/llvm-test/DiffOutput.sh "/home/jo/Delta/llvm/Release/bin/fpcmp " llc multiplies gcc-4.2 -m32 Output/simple.llc.s -o Output/simple.llc -lm -Wl,-melf_i386 -Wl,-melf_i386 /home/jo/Delta/llvm/pr...

On Thu, Apr 17, 2014 at 09:57:32AM -0400, Tom Stellard wrote: > On Fri, Apr 11, 2014 at 03:02:21PM -0700, Tom Stellard wrote: > > Hi, > > > > I have just tagged the first release candidate for the > > 3.4.1 release, so testers may begin testing. Please refer to > > http://llvm.org/docs/ReleaseProcess.html for information on how to > > validate a release.

...c/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vector' > make[5]: Entering directory > `/home/greened/src/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vector/SSE' > /home/greened/src/llvm-30-rc3/build/projects/llvm-test/../../../llvm/projects/llvm-test/RunSafely.sh > 500 0 /dev/null Output/sse.expandfft.llvm.o.compil > e \ > > -I/home/greened/src/llvm-30-rc3/build/projects/llvm-test/SingleSource/UnitTests/Vector/SSE > -I/home/greened/src/llvm-30-rc3/test-suite-3.0rc3 > .src/SingleSource/UnitTests/Vector/SSE > -I/home/greened/src/llvm-3...

On Sat, 2004-09-11 at 12:49, Jeff Cohen wrote: > For the heck of it I tried upgrading to gcc 3.4.2 (from 3.3.3). It > didn't make a difference. So here are the failures for llvm-test. All > diffs are against the "native" output. > > ===================== MultiSource/Applications/sgefa > > cbe failed differently from jit/llc. First cbe: > > 84c84

...u/resources/llvm/llvm2/llvm/projects/llvm-test/External/SPEC/Sandbox.sh llc-train Output/256.bzip2.out-llc /home/snir/jingyu/resources/llvm/build2/projects/llvm-test/External/speccpu2000/benchspec/CINT2000/256.bzip2/data/train/input/ \ /home/snir/jingyu/resources/llvm/llvm2/llvm/projects/llvm-test/RunSafely.sh 500 /dev/null input.compressed.out \ ../256.bzip2.llc `cat /home/snir/jingyu/resources/llvm/build2/projects/llvm-test/External/speccpu2000/benchspec/CINT2000/256.bzip2/data/train/input/control` Running: /home/snir/jingyu/resources/llvm/llvm2/llvm/projects/llvm-test/RunSafely.sh...

...this would be easily modifiable for ARM and other targets that are > supported by QEMU. > > But in this case, we would need to check in a version of QEMU and also > the needed pieces of a MIPS tool chain for assembly, linking, etc. > > Any thoughts on this? If you need changes to RunSafely.sh etc. to tell the scripts to use application-level emulation via qemu, in addition to the existing options, that seems fine. We aren't going to put QEMU or binutils into the LLVM repository, though. If you want to make sure people don't break MIPS, I would suggest setting up a buildbot...

...ble for ARM and other targets that are >> supported by QEMU. >> >> But in this case, we would need to check in a version of QEMU and also >> the needed pieces of a MIPS tool chain for assembly, linking, etc. >> >> Any thoughts on this? > If you need changes to RunSafely.sh etc. to tell the scripts to use > application-level emulation via qemu, in addition to the existing > options, that seems fine. We aren't going to put QEMU or binutils > into the LLVM repository, though. If you want to make sure people > don't break MIPS, I would suggest se...

...tdc++.so.6.0.17) ==5926== by 0x6D4101B: llvm::sys::Path::Path(llvm::StringRef) (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x4F4788C: ??? (in /usr/lib/libclang.so.1) ==5926== by 0x4F39080: ??? (in /usr/lib/libclang.so.1) ==5926== by 0x6D32DDE: llvm::CrashRecoveryContext::RunSafely(void (*)(void*), void*) (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x6D32E13: ??? (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x6D583CC: ??? (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x7610E99: start_thread (pthread_create.c:308) ==5926==...

Dan/Daniel/Eric, I'm testing a bare-metal ARM toolchain, and I've hacked up my local copy of lit to get it to run libcxx tests on qemu. I wanted to pick your collective brains to see if there was a better way of doing this. What I have implemented is here (don't take this as a formal review request, we can do that later once we figure out the best direction to go): lit part:

...ild.llvm.official/Release/bin/fpcmp: FP Comparison failed, not a numeric difference between 'e' and 'f' [i686-off-opt]: ******************** TEST (llc) 'sse.stepfft' **************************** ========================= [i686-off-opt]: ./llvm.official/projects/llvm-test/RunSafely.sh 500 1 /dev/null Output/2007-04-25-weak.out-nat Output/2007-04-25-weak.native [i686-off-opt]: TEST Output/2007-04-25-weak.native FAILED: EXIT != 0 [i686-off-opt]: make[2]: [Output/2007-04-25-weak.out-nat] Error 250 (ignored) ========================= [i686-off-opt]: gcc -std=c99 Output/ctor...