similar to: [LLVMdev] FYI: Changing RunSafely.sh to only track user time

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 numbers (independently), so

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

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

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

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.

Hi all, I would like to get some feedback on who in the community is using the LLVM test-suite repository, and in what ways. I am talking specifically about the "test-suite" SVN project, e.g.: http://llvm.org/svn/llvm-project/test-suite/trunk/ not about the "test (no-dash) suite" that is part of LLVM. If you are using the LLVM test-suite project directly (as opposed to via

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

On Sat, 11 Sep 2004 13:53:11 -0700 Reid Spencer <reid at x10sys.com> wrote: > On Sat, 2004-09-11 at 12:49, Jeff Cohen wrote: > > > > ===================== MultiSource/Applications/sgefa > > > sgefa is a known XFAIL. See the nightly test results over the last > several months. Actually, you should compare your test results with the > 1.3 release test results

On Fri, 4 Apr 2008, heisenbug wrote: >> point taken. thanks! > > > Whatever I try I get something like this: > > ggreif$ cd MultiSource/ > ggreif$ make > make[2]: *** No rule to make target `Output/be.bc', needed by `Output/ > burg.linked.rbc'. Stop. > make[1]: *** [Burg/.makeall] Error 2 > make: *** [Applications/.makeall] Error 2 This is the

On Thu, May 17, 2007 at 03:15:09PM -0700, Tanya M. Lattner wrote: > > Should configure also error out if perl isn't installed? > > Yes. Reid has changed this so that perl is now required. > > Thanks so much for reporting these! You're welcome! I'm still working on the "method four" testing that you requested. The "make check" is done, results

On Apr 4, 8:06 pm, heisenbug <ggr... at gmail.com> wrote: > On Apr 4, 7:51 pm, Török Edwin <edwinto... at gmail.com> wrote: > > > > > heisenbug wrote: > > > On Apr 3, 10:53 pm, Gabor Greif <ga... at mac.com> wrote: > > > ... > > > >>> 3) Make sure that make check and some reasonable subset of llvm-test > > >>>

On 11/07/2011 02:29 PM, Eli Friedman wrote: > On Mon, Nov 7, 2011 at 2:11 PM, reed kotler<rkotler at mips.com> wrote: >> We have a modified version of projects/test-suite that we can run cross >> using Qemu. >> >> We would like to put that back so that other people can test MIPS >> before putting back. >> Well, this would be easily modifiable for ARM

We have a modified version of projects/test-suite that we can run cross using Qemu. We would like to put that back so that other people can test MIPS before putting back. Well, 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,

On Mon, Nov 7, 2011 at 2:11 PM, reed kotler <rkotler at mips.com> wrote: > We have a modified version of projects/test-suite that we can run cross > using Qemu. > > We would like to put that back so that other people can test MIPS > before putting back. > Well, this would be easily modifiable for ARM and other targets that are > supported by QEMU. > > But in this

On Wed, Apr 11, 2012 at 7:59 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi all, > >  I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my > flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). > > --- > $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt > $ ~/mysandbox/bin/python ~/lnt/setup.py develop >

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'.

Hi all, I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). --- $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt $ ~/mysandbox/bin/python ~/lnt/setup.py develop $ cd mysandbox; source bin/activate $ $ lnt runtest nt \ --sandbox SANDBOX \ --cc

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.

Eric Christopher <echristo at apple.com> writes: > 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

On Sun, 3 Sep 2006, Tanya M. Lattner wrote: >> 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