similar to: [LLVMdev] Creating 1.9 branch NOW

Branch has been created. CVS is open again. -Tanya On Mon, 6 Nov 2006, Tanya M. Lattner wrote: > > Please refrain from comitting to cvs. I will send email once I have finished > creating the branch. > > Thanks, > Tanya > >

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'm creating the 2.0 release branch. Users with cvs commit access, please refrain from checking anything in. I will send email out once I have finished. -Tanya

This is just a reminder that I will be creating the 1.8 release branch in 1 hour. Please refrain from checking into cvs after 9PM PDT until I send out email confirming the branch has been created. Thanks, Tanya Lattner

I will be creating the release branch at 1:00pm PDT. Please refrain from checking in from 1:00-1:30pm. I will send email once I am done. Thanks, Tanya

Branches have been created. You are free to checkin to cvs head again. I'll send mail once I have the prerelease tar balls up. Please continue to review and revise the documentation. I can fold this into the release later. Thanks, Tanya On Thu, 13 Apr 2006, Tanya Lattner wrote: > > I will be creating the release branch at 1:00pm PDT. Please refrain from > checking in from

LLVMers, I will be creating the branch in 30 minutes (9PM PDT). At that time, I will send out mail announcing SVN commit access is suspended. Those with commit privileges should refrain from committing until I send out mail saying commit access is restored. Thanks, Tanya Lattner

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

Dear All, Some of you may have noticed that our SSL certificate expired about half an hour ago. We have a new SSL certificate, but we haven't had time to install it. I am going to attempt to install the new certificate. This will necessitate one server restart if I am successful and probably two if I'm not. Chances are that you will not notice any disruption, but if you're the

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

Hi Tanya, Please apply these patches to the release branch: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039776.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039781.html Thanks, Evan On Nov 7, 2006, at 10:39 PM, Tanya M. Lattner wrote: > > I created the 1.9 release branch last night. As a reminder, please > do not > check

I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r

John Criswell wrote: > Dear All, > > Some of you may have noticed that our SSL certificate expired about half > an hour ago. We have a new SSL certificate, but we haven't had time to > install it. > > I am going to attempt to install the new certificate. This will > necessitate one server restart if I am successful and probably two if > I'm not. > >

Here's what's left on Linux (GCC 4.1.0), after all updates that went into the branch: Running /proj/llvm/build/../llvm/test/Regression/CFrontend/dg.exp ... FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-12- LargeAggregateCopy.c.tr: gccas: /proj/llvm/build/../llvm/lib/VMCore/Function.cpp:266: unsigned int llvm::Function::getIntrinsicID() const: Assertion `0 &&

On Tue, Nov 07, 2006 at 10:39:46PM -0800, Tanya M. Lattner wrote: > cvs -d <CVS Repository> co -r release_19 llvm I'm getting a build error: llvm[2]: Compiling llvmAsmParser.cpp for Release build /rest/llvm/llvm/lib/AsmParser/llvmAsmParser.y: In function `int llvmAsmparse()': /rest/llvm/llvm/lib/AsmParser/llvmAsmParser.y:2105: error: expected `;' before '}' token

LLVMers, I am creating the LLVM 2.2 branch now. Please refrain from committing to SVN until I send mail announcing the branch has been created. Thanks, Tanya

The 2.6 code freeze is tomorrow, August 21st, at 9pm PDT. Please refrain from checking in any changes that are major or invasive. This is not the time to be checking in as much as you can because you are trying to cram it into the release. Those who do not use caution with what they commit, may find their commit privileges restricted around the next release. I'm going to stress this

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

The issue I had with Linux has been resolved. I was able to get the deja-gnu tests to pass on a Linux release build by first installing those release binaries into my PATH. Apparently running the debug versions while doing the "make check" in optimized mode, causes the failures. Why, I'm not sure. In any event, in going through this adventure, I learned a few things: 1.

> 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