search for: release_19

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

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

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 future. The release_19 >>> branch of llvm-pool...

What versions of llvm and llvm-poolalloc should I check out of cvs, in order to use DSA? In a previous post John Criswell suggested checking llvm and llvm-poolalloc out of cvs using the -r release_19 flag. However, there were several post later that said that changes should not be made to the release_19 branch. At any rate, I've not seen any update on which versions of llvm and llvm-poolalloc compile with each other. Could someone please let me know? I tried using the -r release_19 f...

...nline cvs. Poolalloc is broken, however. On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > What versions of llvm and llvm-poolalloc should I check out of cvs, in > order to use DSA? In a previous post John Criswell suggested checking > llvm and llvm-poolalloc out of cvs using the -r release_19 flag. > However, there were several post later that said that changes > should not > be made to the release_19 branch. > > At any rate, I've not seen any update on which versions of llvm and > llvm-poolalloc compile with each other. Could someone please let me > know? I...

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 future. The release_19 >>>>branch...

I have a few questions on using dsa now that it has been moved out of llvm. I have llvm -r release_19 checked out from cvs, and llvm-poolalloc -r release_19 checked out from cvs into the projects directory, as John Criswell previously suggested. 1) I have some compiler transforms that I'm writing that use DSA. They can no longer find the header files for DSA. My transforms are located in t...

Ryan M. Lefever wrote: > I have a few questions on using dsa now that it has been moved out of > llvm. I have llvm -r release_19 checked out from cvs, and > llvm-poolalloc -r release_19 checked out from cvs into the projects > directory, as John Criswell previously suggested. > > 1) I have some compiler transforms that I'm writing that use DSA. They > can no longer find the header files for DSA. My tran...

Forgot to hit "Reply All." -- John T. -------------- next part -------------- An embedded message was scrubbed... From: John Criswell <criswell at cs.uiuc.edu> Subject: Re: using dsa Date: Tue, 06 Mar 2007 09:53:43 -0600 Size: 3103 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070306/ef7c2f29/attachment.mht>

...oken, however. > > On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > >> What versions of llvm and llvm-poolalloc should I check out of cvs, in >> order to use DSA? In a previous post John Criswell suggested checking >> llvm and llvm-poolalloc out of cvs using the -r release_19 flag. >> However, there were several post later that said that changes >> should not >> be made to the release_19 branch. >> >> At any rate, I've not seen any update on which versions of llvm and >> llvm-poolalloc compile with each other. Could someone ple...

...below to check out llvm-poolalloc. When I want to get new updates made to llvm-poolalloc, do I perform the following commands? cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login <Hit return for an empty password> cd llvm/projects cvs -d :pserver:anon at llvm.org:/var/cvs/llvm update -r release_19 llvm-poolalloc In other words, do I specify the -r option to perform an update? Also, how do I produce the doxygen for DSA? Regards, Ryan John T. Criswell wrote: > Vikram S. Adve wrote: > > >>This kind of regression is a fallout of having some code live in >>separate C...

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 release_19 llvm-gcc svn co svn://anonsvn.opensource.apple.com/svn/llvm/tags/release-1.9 dst-directory Unlike code changes, please go ahead and commit any documentation changes to the release branch (a...

...than I'm able to keep up; constantly updating llvm-poolalloc every time mainline LLVM has changed has proved too time consuming. I've decided that it's better to update once mainline has stabalized (and I've got more time). So, for now, I'm using LLVM 1.9 (technically, the release_19 branch, which is identical to LLVM 1.9 except that DSA has been moved from the LLVM source base to the Pool Allocation project). Using the release_19 branch of the llvm and llvm-poolalloc modules should give you something that compiles and (hopefully) works. To get it, download the llvm-gcc3...

...lease 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 release_19 llvm-gcc > svn co svn://anonsvn.opensource.apple.com/svn/llvm/tags/release-1.9 > dst-directory > > Unlike code changes, please go ahead and commit any documentation...

This kind of regression is a fallout of having some code live in separate CVS modules as "projects." It would help to have someone volunteer to maintain each project, which can be as little as making sure it continues to compile or as much as supporting it with answers to questions and bug fixes. Here is the current list of projects: llvm-poolalloc llvm-java (currently unused

On Feb 13, 2007, at 11:08 AM, John T. Criswell wrote: > there is a difference between RELEASE_19 and release_19. I have not tried, but I won't be surprised if CVS itself gets confused between this two on systems like Darwin which is case insensitive but case preserving. - Devang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/...

...oken, however. > > On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > >> What versions of llvm and llvm-poolalloc should I check out of cvs, in >> order to use DSA? In a previous post John Criswell suggested checking >> llvm and llvm-poolalloc out of cvs using the -r release_19 flag. >> However, there were several post later that said that changes >> should not >> be made to the release_19 branch. >> >> At any rate, I've not seen any update on which versions of llvm and >> llvm-poolalloc compile with each other. Could someone ple...

...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 release_19 llvm-gcc > svn co svn://anonsvn.opensource.apple.com/svn/llvm/tags/release-1.9 dst-directory > > Unlike code changes, please go ahead and commit any documentation changes...

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 /rest/llvm/llvm/lib...

...at cs.uiuc.edu> > Date: > Tue, 06 Mar 2007 09:53:43 -0600 > To: > "Ryan M. Lefever" <lefever at crhc.uiuc.edu> > > To: > "Ryan M. Lefever" <lefever at crhc.uiuc.edu> > > > Ryan M. Lefever wrote: >> >> I tried using the -r release_19 flag (as was originally >> suggested), but that version of LLVM fails to compile. I get the >> following error: > I did a clean checkout of the release_19 branch and got the same > problem. It seems that the following line in tools/llvm-config/Makefile > is doing it: > &gt...