similar to: [LLVMdev] 2 experimental projects

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] 2 experimental projects"

2008 Mar 19
0
[LLVMdev] 2 experimental projects
>> In case of the llvm tests the situation is somewhat more >> complicated, since dejagnu is driving the process, and >> dejagnu hinders us in a direct $(MAKE) invocation, so >> it falls back to -j1. My approach is thus using dejagnu >> to build up makefiles in test/.../Output/... and when >> these makefiles are executed by $(MAKE) we will >> get the
2009 Oct 19
0
[LLVMdev] RFC: Dropping DejaGNU
On Oct 18, 2009, at 7:49 PM, Daniel Dunbar wrote: > Hi all, > > As you may or may not have noticed, I have gradually been replacing > the testing infrastructure in LLVM. Most of this work is moving LLVM > and Clang to share a single testing tool, 'lit'. See: > http://llvm.org/cmds/lit.html > for documentation on the tool itself. > > If you haven't already
2009 Oct 19
7
[LLVMdev] RFC: Dropping DejaGNU
Hi all, As you may or may not have noticed, I have gradually been replacing the testing infrastructure in LLVM. Most of this work is moving LLVM and Clang to share a single testing tool, 'lit'. See: http://llvm.org/cmds/lit.html for documentation on the tool itself. If you haven't already tried it, please consider switch to 'make check-lit' as an alternative to 'make
2004 Nov 29
1
[LLVMdev] QMTest vs. Dejagnu
> > Cons of QMTest: > > 1) You have to use the gui to add directories. > > I think you're wrong. Manually creating a directory would work, as QMTest does > not place anything special in directories. I may have worded this poorly, but I think you have to use the gui to add new directories or tests, or specific tests. Otherwise, it does not know what to do with those
2008 Jan 31
0
[LLVMdev] [llvm-testresults] OldGrawp-O0-PIC i386 nightly tester results
It's me. Our ISD::LABEL implementation has issues... Evan On Jan 30, 2008, at 9:34 PM, Dale Johannesen wrote: > > On Jan 30, 2008, at 9:12 PM, Apache wrote: > >> http://llvm.org/nightlytest/test.php?machine=231&night=4754 >> Name: il0102a-dhcp80.apple.com >> Nickname: OldGrawp-O0-PIC >> Buildstatus: OK >> >> New Test Passes: >>
2005 Mar 10
3
[LLVMdev] new llvm-testresults mailing list
On Thu, 10 Mar 2005, Vladimir Merzliakov wrote: >> Do to popular request, I just set up a new mailing list to capture the >> nightly tester output from the various testers running 'round the world. >> The new list is available here: >> http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults >> >> If you're running a nightly tester, please update
2008 Feb 16
2
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote: > But I am using llvm-gcc-4.2. Any idea why it's failing? > > Evan All the failing testers are using gcc-4.0 according to the web pages they point at. > On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > >> On Feb 16, 2008, at 7:06 AM, Apache wrote: >>> New Test Failures: >>>
2008 Feb 16
3
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
On Feb 16, 2008, at 7:06 AM, Apache wrote: > New Test Failures: > test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] This test doesn't work with gcc-4.0, which caused it to fail on a number of testers overnight. I can fix that in 4.0, but as I understand it we're going to drop support for it next release, so how about now?
2005 Jan 09
1
[LLVMdev] make check fails on mingw
Can any one, who has dejagnu and expect installed and working, send me an output when running '(g)make check' from llvm. Thanks. Henrik. ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= 'Nothing is impossible; The impossible
2008 Jan 31
2
[LLVMdev] [llvm-testresults] OldGrawp-O0-PIC i386 nightly tester results
On Jan 30, 2008, at 9:12 PM, Apache wrote: > http://llvm.org/nightlytest/test.php?machine=231&night=4754 > Name: il0102a-dhcp80.apple.com > Nickname: OldGrawp-O0-PIC > Buildstatus: OK > > New Test Passes: > test/CFrontend/2008-01-28-PragmaMark.c [DEJAGNU] > > > New Test Failures: > Benchmarks/Shootout-C++/except [LLC compile, ] >
2005 Mar 10
0
[LLVMdev] new llvm-testresults mailing list
> Do to popular request, I just set up a new mailing list to capture the > nightly tester output from the various testers running 'round the world. > The new list is available here: > http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults > > If you're running a nightly tester, please update your crontab to send > mail to the llvm-testresults at cs.uiuc.edu list
2005 Feb 17
0
[LLVMdev] LLVM built on VS C++ 2005
On Wed, 2005-02-16 at 19:52, Aaron Gray wrote: > Hi Reid, > > I'll send a complete report tommorow, its getting late. Great! > > It looks like there is alot of work to do to get the MS VC version in line > with the Unix release. I am very willing to help out with porting. Yes, there are several well known issues remaining. The bugpoint tool and the debugger use unix
2009 Feb 25
0
[LLVMdev] [PATCH] Parallelized make check
On Wed, Feb 25, 2009 at 10:26:02AM -0800, Chris Lattner wrote: > > On Feb 24, 2009, at 10:03 PM, Julien Lerouge wrote: > > > On Tue, Feb 24, 2009 at 06:24:17PM -0800, Julien Lerouge wrote: > >> I haven't tested with objdir != srcdir. > > > > Ok, that was broken. Attached is a smaller diff that should work in > > all > > cases. > > This
2009 Feb 26
1
[LLVMdev] [PATCH] Parallelized make check
On Wed, Feb 25, 2009 at 12:02:18PM -0800, Julien Lerouge wrote: > For 2), I think the NewNightlyTest.pl script would require some small > changes, to invoke the jcheck target instead of check, pass the desired > -j flag, and also parse the log. I'll take a look. In any case, the > changes would only apply to the DejaGNU tests (llvm-test already works > fine with -jX). Here is
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
llvm itself is built with gcc-4.0, but the run line is: // RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 | grep {i32 1} | count 2 According the log: FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+ +Frontend/2008-02-13-sret.cpp Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /
2005 Mar 09
3
[LLVMdev] new llvm-testresults mailing list
Hi All, Do to popular request, I just set up a new mailing list to capture the nightly tester output from the various testers running 'round the world. The new list is available here: http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults If you're running a nightly tester, please update your crontab to send mail to the llvm-testresults at cs.uiuc.edu list (potentially in addition
2008 Feb 16
0
[LLVMdev] [llvm-testresults] Grawp-PIC i386 nightly tester results
But I am using llvm-gcc-4.2. Any idea why it's failing? Evan On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > On Feb 16, 2008, at 7:06 AM, Apache wrote: >> New Test Failures: >> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] > > This test doesn't work with gcc-4.0, which caused it to fail on a > number of testers overnight. I can fix that in 4.0, but as I
2004 Nov 29
0
[LLVMdev] QMTest vs. Dejagnu
Tanya Lattner wrote: > I've finished adding the -rundejagnu option to the nightly tester script, > which was the last step to fully support Dejagnu. I think now is the > appropriate time to discuss keeping QMTest or switching to Dejagnu. A lot > of work went into using QMTest, so I think we should make this decision > carefully and before the 1.4 release. > > Here are the
2009 Oct 19
3
[LLVMdev] RFC: Dropping DejaGNU
On Mon, Oct 19, 2009 at 2:03 PM, Eric Christopher <echristo at apple.com> wrote: > On Oct 18, 2009, at 7:49 PM, Daniel Dunbar wrote: >> If you haven't already tried it, please consider switch to 'make >> check-lit' as an alternative to 'make check'. If it doesn't work for >> you, or you find it doesn't do something DejaGNU did and you like,
2005 Jan 09
0
[LLVMdev] make check fails on mingw
On Sun, 9 Jan 2005, Henrik Bach wrote: > I found that it was runtest.exp which referenced to the internal exp_debug > function. For testing purposes I disabled the reference and ran a new: Hi Henrik, Unfortunately, none of us has access to a MinGW setup, so we cannot debug this problem. If you're hacking on dejagnu or expect itself (because it has not yet been ported to MinGW