similar to: [LLVMdev] New Branch Commit mailing list

On Mon, Jan 28, 2013 at 9:48 AM, Chris Lattner <clattner at apple.com> wrote: > On Jan 26, 2013, at 3:20 PM, Tanya Lattner <tonic at nondot.org> wrote: >>>> >>>>> I agree that the list name is redundant and should be dropped, but >>>>> the revision number is compact and very useful... >>>>> >>>>> -Chris

On Jan 26, 2013, at 3:20 PM, Tanya Lattner <tonic at nondot.org> wrote: >>> >>>> I agree that the list name is redundant and should be dropped, but >>>> the revision number is compact and very useful... >>>> >>>> -Chris >>> >>> If we agreed to perform this change and we found the person who can change >>>

> This is my patch for MSVC 2008 and it was applied by Chris: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html > > I tested it and it is ok for the 2.3 release. I don't believe I can apply this patch. There have been several patches applied recently to TOT to allow MSVC 2005 which I think many people are using. Does this patch mean that one

As I saw from the mailing list the MSVC 2005 patches were made to take into account the new files from the development branch, files which are not in the 2.3 release. So for now the below patch is the only one functional for the release. If I am wrong, please someone correct me. If someone can make a 2005 patch for the release branch, it is ok. Else, I am afraid that this one is for now the

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.

This is my patch for MSVC 2008 and it was applied by Chris: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html I tested it and it is ok for the 2.3 release. Razvan ----- Original Message ----- From: "Tanya Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 20, 2008 7:40 AM

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 -

On Thu, 13 Apr 2006, Reid Spencer wrote: > 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,

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

Dear Tanya: > You also have a few CBE failures that I am not seeing. What version > of xcode do you have installed? Xcode 2.4.1 > Can you send me the following files? > SingleSource/Regression/C/Output/2008-01-07-LongDouble.* > SingleSource/Regression/C/Output/PR1386.* OK, I attached those files (llvm-2.2-test-output.tar.gz) Best regards, 2008/1/30, Tanya Lattner <tonic at

Hi Tanya, Thanks for creating the branch! What's the procedure for getting a patch into it? There might be one that I need to get in this week... Thanks! -bw On Sep 12, 2007, at 9:52 PM, Tanya Lattner wrote: > LLVMers, > > The LLVM 2.1 release branches have been created! Over the next 2 > days, I will be generating the pre-release tar balls. I will send out > mail once I

Tanya M. Lattner wrote: > How large of a change have you made? With 3 days before the branch > creation, I strongly advise people not to be checking in major changes. Depends how you look at it. Structurally, it separates two files into four and moves some functionality from one class to a new class, so in a sense that's a big change. Code-logic-wise, it does nothing at all. I will

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

Thanks for testing the release. Overall the test results look decent with a couple exceptions. You also have a few CBE failures that I am not seeing. What version of xcode do you have installed? Can you send me the following files? SingleSource/Regression/C/Output/2008-01-07-LongDouble.* SingleSource/Regression/C/Output/PR1386.* Thanks, Tanya On Jan 26, 2008, at 6:43 AM, Takanori Ishikawa

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

Tanya M. Lattner wrote: >>I recommend that you stick with the release_19 branch of both llvm and >>llvm-poolalloc. I and others are actively using these branches, so >>llvm-poolalloc bug fixes will most likely be made to this branch in >>addition to mainline CVS for the forseeable future. The release_19 >>branch of llvm-poolalloc is designed to always work with the

LLVMers, The LLVM 2.1 release branches have been created! Over the next 2 days, I will be generating the pre-release tar balls. I will send out mail once I am done and then the community pre-release testing will begin. I'll also be sending out detailed instructions and the release schedule. Full svn access is restored. Thanks for your patience! Thanks, Tanya Lattner

On 11/2/05, Tanya Lattner <tonic at nondot.org> 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 can try to test on MacOS X. -bw

Chris Lattner wrote: >On Tue, 13 Feb 2007, John T. Criswell wrote: > > >>>>I recommend that you stick with the release_19 branch of both llvm and >>>>llvm-poolalloc. I and others are actively using these branches, so >>>>llvm-poolalloc bug fixes will most likely be made to this branch in >>>>addition to mainline CVS for the forseeable

LLVMers, The 2.5 release branch has been created. You may check it out with the following commands: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25 svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25 svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25 Please do not commit anything to the release branch. If you have a patch that needs