On Jan 4, 2008, at 3:34 PM, Chris Lattner wrote: > > On Jan 4, 2008, at 3:15 PM, Dale Johannesen wrote: > >> On Jan 4, 2008, at 3:04 PM, Owen Anderson wrote: >>> Could we add a test for this to the LLVM regression tests? I think >>> most people check them before committing things. >>> >>> --Owen >> >> Yes, but I don't think it's the right idea, in general, for problems >> that are llvm-gcc problems (not llvm problems). >> We'll wind up copying the whole gcc testsuite into llvm. IMO a >> better approach is to set up a regression tester for llvm-gcc. >> > > How long does it take to run the GCC regression tests? I think the > right answer is to run them from the nightly tester script, instead of > adding yet another tester.
Seems reasonable, but we might want to keep the separation of llvm and llvm-gcc clean. Last night's run was around 4.5 hours on a 2.16GHz Core 2 Duo. However, there are currently 31 failures that hang (e.g. builtin_setjmp does this) and they go until the dejagnu timeout kicks in at 5 minutes wall clock. Fixing those would speed it up a lot. _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
