similar to: [LLVMdev] LLVM 1.8 Release Schedule

I'd like to tag and create the branch for llvm and llvm-test soon. Does anyone still have tests to XFAIL, warnings to fix, or other critical bug fixes? Please respond to this mail and let me know ASAP if you are done or need more time. -Tanya

LLVM Developers, It is now 1 week before I will create the 2.0 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before

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 pros and cons in my eyes, please feel free to add your

LLVMers, It is now 1 week before I will create the 1.9 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before the

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

This is just a friendly reminder that the 1.9 release is coming up. The code freeze is just a month away. Here are the important dates: * October 30, 2006: Email sent out asking platform maintainers to XFAIL tests, check for regression/file bugs, and check in any final stuff for the release. * November 6, 2006: Code freeze and release branch created. Documentation review. * November 13, 2006:

Hi Tanya, The new type-legalization mode (-promote-elements) which enables vector-select in LLVM (and a nice perf boost for several workloads), is currently disabled because of a _single_ bug in the ARM codegen which makes a few tests fail. If ARM is not a supported target, can I mark these tests as 'XFAIL' and enable vector-select support in LLVM ? Thanks, Nadav -----Original

LLVMers, I'd like to propose the following release schedule for 2.0: * April 30th - 1 week before code freeze warning email. * May 7th - Code freeze and branch creation. * May 14th - Pre-releases available for additional testing. All documentation changes committed to branch and mainline. * May 21st - Release. If anyone has objection to this schedule, please respond to the list and we can

> 1. I'm still looking for volunteers to test MacOS X and Solaris. If you'd > like to volunteer, please email the list to let us know. I'll do minimal testing on Sparc. I'm not going to look into any regressions though since no one has been really watching Sparc since I graduated and I am sure there are regressions. > 2. If you maintain a platform other than those

The various intrinsic assert/crashes should all be fixed on mainline CVS (they are PR733, which I just fixed). The only ones that I'm wary of are: XPASS: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-20- StaticRedeclare.c.tr FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2005-12-04- DeclarationLineNumbers.c: In the former case, I would guess that the test isn't

Tanya Lattner wrote: > > Everything builds fine on sparc. The configure script needs to be fixed > though (see previous email). I'm not getting the error with the configure script (on Kain, anyway). I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my $PATH. Can you verify that the configure script works for you without the --with-f2c option?

Tanya Lattner wrote: > >> 1. I'm still looking for volunteers to test MacOS X and Solaris. >> If you'd like to volunteer, please email the list to let us know. > > > I'll do minimal testing on Sparc. I'm not going to look into any > regressions though since no one has been really watching Sparc since I > graduated and I am sure there are

LLVMers, Sorry for the delay in this email. The 1.8 release has been pushed out 1 week, so today marks 1 week before I create the 1.8 branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test

I will be creating the branch at 9PM PST. Please refrain from checking in any large changes until after the branch creation. I'm still seeing unexpected dejagnu failures for PPC and X86. Platform maintainers, please XFAIL these and file bugzilla bugs. Email me if you have concerns or questions. -Tanya

I just updated again (both llvm and llvm-gcc). The only thing that changed was: P test/Regression/CFrontend/2005-12-04-DeclarationLineNumbers.c The regression test below was done *with* your llvm-gcc changes to llvm- expand.c. I don't know what the failures are all about, but I will try it again. If its the same, I'll let you know. Reid. On Thu, 2006-04-13 at 16:20 -0500, Chris Lattner

I've put the pre-release tar balls here: http://llvm.org/prereleases/1.8/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Quick Summary of Important Dates: August 7th - All documentation reviewed and changes checked in. August 8th -

Dear All, I've created the LLVM release branch (CVS tag release_16). Those developers wanting to commit changes to LLVM without having your changes go into LLVM 1.6 can now commit to CVS mainline to your heart's content. :) TESTING: -------- 1. I'm still looking for volunteers to test MacOS X and Solaris. If you'd like to volunteer, please email the list to let us know.

Just a reminder, please complete your testing by May 21st! Thanks, Tanya ---------- Forwarded message ---------- Date: Tue, 13 May 2008 00:25:41 -0700 From: Tanya Lattner <tonic at nondot.org> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: 2.3 Pre-release available for testing LLVMers, The 2.3 pre-release is available for testing:

>> Everything builds fine on sparc. The configure script needs to be fixed >> though (see previous email). > > I'm not getting the error with the configure script (on Kain, anyway). I've > tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my > $PATH. I get the error with and without the --with-f2c option. I never used the NAG Fotran

On May 19, 2008, at 9:13 PM, Razvan Aciu wrote: > I tested this pre-release on MSVC and I noted that none of the > submitted > patches (mine or others) were applied. > So the llvm 2.3 will not compile out of the box in MSVC? > Please provide me with a link to the patch(s) that need to be applied (llvm-commits archive email). I only apply patches that have been sent to me and