similar to: [LLVMdev] 2.3 Branch Created!

Hi Tanya, Are we allowed to patch the release branch yet? 50940 should go in. Evan On May 9, 2008, at 9:37 PM, Tanya Lattner wrote: > LLVMers, > > The 2.3 branch has been created. I will now begin the pre-release > testing and packaging. I will have the pre-release version tarballs > and binaries ready on Monday, May 12th. I will ask you all to begin > testing at that

Hi (Tanya?), Just thought I'd let you know: there appears to be a directory called "release_23"[1] in SVN, under /tags/RELEASE_23. Strange, but doesn't really hurt anything (unless you checkout 2.3!). Regards, -Mahadevan. [1] http://www.llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_23/release_23/

Hello, How do I download the poolalloc module for llvm 2.3? This is the svn command I was trying but it doesn't work: svn co http://llvm.org/svn/llvm-project/poolalloc/RELEASE_23 Max -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090823/3649d72f/attachment.html>

> 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

There is no 2.3 release of poolalloc. This is a research project at UIUC and they do not do releases of it. -Tanya On Aug 23, 2009, at 6:25 PM, Max Stonebraker wrote: > Hello, > > How do I download the poolalloc module for llvm 2.3? This is the svn > command I was trying but it doesn't work: > > svn co http://llvm.org/svn/llvm-project/poolalloc/RELEASE_23 > >

Tanya Lattner wrote: > There is no 2.3 release of poolalloc. This is a research project at > UIUC and they do not do releases of it. We have not done scheduled releases of the poolalloc source code. In the past, we have merely kept the SVN version updated with LLVM mainline (more or less). If you want to use DSA or poolalloc, I recommend that you update to the upcoming LLVM 2.6 release

LLVMers, I will be creating the 2.3 release branch today at 9PM PDT. During that time, commit access to SVN will be forbidden. I will send out mail shortly before the branch creation, and once it has been completed. Thanks, Tanya

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

>I just sent a reply to Razvan with 3 patches that I think should be merged >into the release branch. I want to keep it somewhat in sync with mainline. >Can you try applying those 3 patches and let me know if it builds for you >and what version of MSVC you have? It doesn't build. first problem is patch 51098 that adds lib\VMCore\Use.cpp and lib\Transforms\Utils\UnrollLoop.cpp

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

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

Razvan Aciu wrote: > 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.

> Ok, I got the release_23 branch and added/removed files until it would build > without errors. I didn't have time to test the clang build, but at least this > patch will make things compile so someone else can test it. I just sent a reply to Razvan with 3 patches that I think should be merged into the release branch. I want to keep it somewhat in sync with mainline. Can you try

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:

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

I tried to compile on Windows ( using the win32/llvm.sln in MSVC Express 2008 ) the new 2.3 branch and here are the results: 1. I needed to copy the file Configure.exe.embed.manifest to Configure.exe.intermediate.manifest . This is a bug from the previous llvm release (2.2) 2. I copied the file SimplifyLibCalls.cpp from lib/Transforms/Scalar to lib/Transforms/IPO. I think the position of

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 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

Dear All, I have finished updating the DSA and Poolalloc source code so that it compiles with the LLVM 2.6 API. If you check out the LLVM 2.6 branch (directions are in the llvmdev archives; look for the email by Tanya Lattner about the LLVM 2.6 branch), you should be able to build mainline DSA and Pool Allocation against it. If you have trouble building DSA/Pool Allocation, please email

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? Razvan ----- Original Message ----- From: "Tanya M. Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Monday, May 19, 2008 9:00 PM Subject: