I've uploaded the 2.0 pre-release to this location: http://llvm.org/prereleases/2.0/ If you have free time and would like to help test this release, please download the appropriate tarballs from the website. Here are a few ways you can help test this release: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. It would also be helpful for someone to compile/test with objdir != srcdir. The 2.0 release defaults to a Release build, but you are welcome to test with a Debug build as well. When reporting your results, please email the list and mention what platform, which option you chose (1, 2, 3, or 4), and if you made any configure changes (objdir != srcdir, or Debug build). Include the dejagnu test log or the nightly test report. Thanks, Tanya Lattner
I forgot to mention that all testing should be completed by May 20th 5pm PDT. -Tanya On Tue, 15 May 2007, Tanya M. Lattner wrote:> > I've uploaded the 2.0 pre-release to this location: > http://llvm.org/prereleases/2.0/ > > If you have free time and would like to help test this release, please > download the appropriate tarballs from the website. > > Here are a few ways you can help test this release: > > 1) Download llvm-gcc4 binary and llvm. Compile and run make check. > > 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make > check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. > > 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. > > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != srcdir. > The 2.0 release defaults to a Release build, but you are welcome > to test with a Debug build as well. > > When reporting your results, please email the list and mention what > platform, which option you chose (1, 2, 3, or 4), and if you made any > configure changes (objdir != srcdir, or Debug build). Include the dejagnu > test log or the nightly test report. > > Thanks, > Tanya Lattner > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Tanya, I have done make check and nightly report tests on LLVM on the GCC 4.2.0 release, on Linux x86 32 bit. On make check the bit intrinsics test is still failing but it works from the command line, strange ? What files do you want from the nightly report, as I am not familiar with it ? I will be doing Cygwin tests next. Aaron ----- Original Message ----- From: "Tanya M. Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 15, 2007 9:23 AM Subject: [LLVMdev] 2.0 Pre-release tarballs online> > I've uploaded the 2.0 pre-release to this location: > http://llvm.org/prereleases/2.0/ > > If you have free time and would like to help test this release, please > download the appropriate tarballs from the website. > > Here are a few ways you can help test this release: > > 1) Download llvm-gcc4 binary and llvm. Compile and run make check. > > 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make > check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. > > 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. > > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != > srcdir. > The 2.0 release defaults to a Release build, but you are welcome > to test with a Debug build as well. > > When reporting your results, please email the list and mention what > platform, which option you chose (1, 2, 3, or 4), and if you made any > configure changes (objdir != srcdir, or Debug build). Include the dejagnu > test log or the nightly test report. > > Thanks, > Tanya Lattner > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.467 / Virus Database: 269.7.1/805 - Release Date: 15/05/2007 > 10:47 >
Aaron, On Thu, 2007-05-17 at 22:54 +0100, Aaron Gray wrote:> Tanya, > > I have done make check and nightly report tests on LLVM on the GCC 4.2.0 > release, on Linux x86 32 bit. > > On make check the bit intrinsics test is still failing but it works from the > command line, strange ?Can you be a bit more specific about which test is failing? Reid.> > What files do you want from the nightly report, as I am not familiar with it > ? > > I will be doing Cygwin tests next. > > Aaron > > ----- Original Message ----- > From: "Tanya M. Lattner" <tonic at nondot.org> > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Tuesday, May 15, 2007 9:23 AM > Subject: [LLVMdev] 2.0 Pre-release tarballs online > > > > > > I've uploaded the 2.0 pre-release to this location: > > http://llvm.org/prereleases/2.0/ > > > > If you have free time and would like to help test this release, please > > download the appropriate tarballs from the website. > > > > Here are a few ways you can help test this release: > > > > 1) Download llvm-gcc4 binary and llvm. Compile and run make check. > > > > 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make > > check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. > > > > 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. > > > > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > > > It would also be helpful for someone to compile/test with objdir != > > srcdir. > > The 2.0 release defaults to a Release build, but you are welcome > > to test with a Debug build as well. > > > > When reporting your results, please email the list and mention what > > platform, which option you chose (1, 2, 3, or 4), and if you made any > > configure changes (objdir != srcdir, or Debug build). Include the dejagnu > > test log or the nightly test report. > > > > Thanks, > > Tanya Lattner > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.5.467 / Virus Database: 269.7.1/805 - Release Date: 15/05/2007 > > 10:47 > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote:> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != srcdir.This is on FreeBSD 6.2-RELEASE, on i386. Both llvm and llvm-gcc were compiled with objdir != srcdir. Release, not Debug build of LLVM. http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-report.nightly.txt --Emil
> On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. >> >> It would also be helpful for someone to compile/test with objdir != srcdir. > > This is on FreeBSD 6.2-RELEASE, on i386. > Both llvm and llvm-gcc were compiled with objdir != srcdir. > Release, not Debug build of LLVM. > > http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-make-check.txt > http://goanna.cs.rmit.edu.au/~emil/llvm-2.0-report.nightly.txtThank you so much for testing the release!! I've checked out the nightly test report and it looks like there is potentially one regression. SingleSource/UnitTests/Vector/SSE/sse.expandfft However, I need you to look at your /proc/cpuinfo (or whatever it is on FreeBSD) to tell me what flavors of sse you have (mmx, sse1, sse2, etc). Thanks, Tanya> > --Emil > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
> On make check the bit intrinsics test is still failing but it works from the > command line, strange ?Did Chris help you with this or is it still an issue?> What files do you want from the nightly report, as I am not familiar with it > ?in llvm-test, if you run the gmake TEST=nightly report command it will generated a report.nightly.txt file. Thats what I want to see. Thanks! -Tanya> > I will be doing Cygwin tests next. > > Aaron > > ----- Original Message ----- > From: "Tanya M. Lattner" <tonic at nondot.org> > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Tuesday, May 15, 2007 9:23 AM > Subject: [LLVMdev] 2.0 Pre-release tarballs online > > >> >> I've uploaded the 2.0 pre-release to this location: >> http://llvm.org/prereleases/2.0/ >> >> If you have free time and would like to help test this release, please >> download the appropriate tarballs from the website. >> >> Here are a few ways you can help test this release: >> >> 1) Download llvm-gcc4 binary and llvm. Compile and run make check. >> >> 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make >> check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. >> >> 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. >> >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. >> >> It would also be helpful for someone to compile/test with objdir !>> srcdir. >> The 2.0 release defaults to a Release build, but you are welcome >> to test with a Debug build as well. >> >> When reporting your results, please email the list and mention what >> platform, which option you chose (1, 2, 3, or 4), and if you made any >> configure changes (objdir != srcdir, or Debug build). Include the dejagnu >> test log or the nightly test report. >> >> Thanks, >> Tanya Lattner >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.5.467 / Virus Database: 269.7.1/805 - Release Date: 15/05/2007 >> 10:47 >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
I've updated the pre-release tarballs online. I'm also extending the testing completion date to May 22nd at 5pm PDT. The new release target date is May 23rd. If you have any free time, please give the new pre-release a try. Thanks to all who have tested LLVM! -Tanya P.S. Documentation review should still be completed today! Thanks!> I've uploaded the 2.0 pre-release to this location: > http://llvm.org/prereleases/2.0/ > > If you have free time and would like to help test this release, please > download the appropriate tarballs from the website. > > Here are a few ways you can help test this release: > > 1) Download llvm-gcc4 binary and llvm. Compile and run make check. > > 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make check, > and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. > > 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. > > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != srcdir. > The 2.0 release defaults to a Release build, but you are welcome to test with > a Debug build as well. > > When reporting your results, please email the list and mention what platform, > which option you chose (1, 2, 3, or 4), and if you made any configure changes > (objdir != srcdir, or Debug build). Include the dejagnu test log or the > nightly test report. > > Thanks, > Tanya Lattner > >
Just a reminder, if anyone is still testing, please send me your results by 5pm PDT Today! At this point, it looks like the release is on schedule for Wednesday. We won't be delaying it unless new test results reveal major problems. Thanks for all your help, Tanya On Fri, 18 May 2007, Tanya M. Lattner wrote:> > I've updated the pre-release tarballs online. I'm also extending the testing > completion date to May 22nd at 5pm PDT. The new release target date is May > 23rd. > > If you have any free time, please give the new pre-release a try. > > Thanks to all who have tested LLVM! > > -Tanya > > P.S. Documentation review should still be completed today! Thanks! > > >> I've uploaded the 2.0 pre-release to this location: >> http://llvm.org/prereleases/2.0/ >> >> If you have free time and would like to help test this release, please >> download the appropriate tarballs from the website. >> >> Here are a few ways you can help test this release: >> >> 1) Download llvm-gcc4 binary and llvm. Compile and run make check. >> >> 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run make >> check, and do "make ENABLE_OPTIMIZED=1 TEST=nightly report" in llvm-test. >> >> 3) Compile llvm-gcc4 and llvm from source. Run 'make check'. >> >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. >> >> It would also be helpful for someone to compile/test with objdir != >> srcdir. >> The 2.0 release defaults to a Release build, but you are welcome to test >> with a Debug build as well. >> >> When reporting your results, please email the list and mention what >> platform, which option you chose (1, 2, 3, or 4), and if you made any >> configure changes (objdir != srcdir, or Debug build). Include the dejagnu >> test log or the nightly test report. >> >> Thanks, >> Tanya Lattner >> >> >