search for: release_23

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/

...date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date] release_22 -> llvm.org/release_22 = [up to date] release_23 -> llvm.org/release_23 = [up to date] release_24 -> llvm.org/release_24 = [up to date] release_25 -> llvm.org/release_25 = [up to date] release_26 -> llvm.org/release_26 = [up to date] release_27 -> llvm.org/release_27 = [up to date] release_28 -> llv...

...nly contain what's in trunk in the SVN repos. I think it contains branches of several previous releases: $ git branch -r llvm-upstream/master llvm-upstream/release_1 llvm-upstream/release_16 llvm-upstream/release_20 llvm-upstream/release_21 llvm-upstream/release_22 llvm-upstream/release_23 llvm-upstream/release_24 llvm-upstream/release_25 llvm-upstream/release_26 llvm-upstream/release_27 llvm-upstream/release_28 llvm-upstream/release_29 llvm-upstream/svn-tags/RELEASE_1 llvm-upstream/svn-tags/RELEASE_20 llvm-upstream/svn-tags/RELEASE_21 llvm-upstream/svn-tags/RELEA...

...t; llvm.org/release_1 > = [up to date] release_16 -> llvm.org/release_16 > = [up to date] release_20 -> llvm.org/release_20 > = [up to date] release_21 -> llvm.org/release_21 > = [up to date] release_22 -> llvm.org/release_22 > = [up to date] release_23 -> llvm.org/release_23 > = [up to date] release_24 -> llvm.org/release_24 > = [up to date] release_25 -> llvm.org/release_25 > = [up to date] release_26 -> llvm.org/release_26 > = [up to date] release_27 -> llvm.org/release_27 > = [up to date]...

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

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>

...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 time. If you need to check out the branch before then, here is the proper command (for llvm): svn co https://llvm.org/svn/llvm-project/llvm/branches/release_23 The release schedule may be found on the llvm.org main page. Have a good weekend. Thanks! -Tanya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080509/43959a61/attachment.html>

...errors were because these projects wasn't updated to reflect the actual status of the llvm files. I checked all the files (removed, moved or added) and now they are ok. It compiles all targets from the first "Build Solution", both for Debug and for Release mode. You need the latest release_23 files. I also added a compiling.txt with some notes. The .sln and .vcproj files now are updated to the 2008 version of MSVC Express (my development environment). If you want to keep compatibility with MSVC 2005, someone with that environment needs to take the old project files and sync them wit...

...hat it is made for MSVC 2008. If there will be no other patches, > the alternative is that the 2.3 release will not work with any MSVC. > Anyway, it is not so hard to sync the MSVC projects with the 2.3 release > files and if someone with MSVC 2005 can do it, please do it. 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. m. PS. Visual Studio really hates how the operator new is overridden in User.h:42, you get thousands u...

...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 > > Max > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part -------------- An HTML attachment was scrubbed... UR...

...e pre-release version tarballs > and binaries ready on Monday, May 12th. I will ask you all to begin > testing at that time. > > If you need to check out the branch before then, here is the proper > command (for llvm): > svn co https://llvm.org/svn/llvm-project/llvm/branches/release_23 > > The release schedule may be found on the llvm.org main page. > > Have a good weekend. > > Thanks! > -Tanya > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs...

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

..., llvm::BasicBlock*>*)this)->__gnu_cxx::_EqualOpConcept<llvm::BasicBlock, llvm::BasicBlock*>::__a == ((__gnu_cxx::_EqualOpConcept<llvm::BasicBlock, llvm::BasicBlock*>*)this)->__gnu_cxx::_EqualOpConcept<llvm::BasicBlock, llvm::BasicBlock*>::__b' D:/msys/home/Razvan/release_23/include/llvm/ADT/APInt.h:1242: note: candidates are: bool llvm::operator==(uint64_t, const llvm::APInt&) make[1]: *** [/home/Razvan/release_23/lib/VMCore/Release/BasicBlock.o] Error 1

...hes = branches/*:refs/remotes/origin/*" > into something like "branches = branches/*:refs/remotes/branches/*" This is exactly what was done on llvm.org. Here is an example fron clang.git: fetch = trunk:refs/heads/master tags = tags/{RELEASE_20,RELEASE_21,RELEASE_22,RELEASE_23,RELEASE_24,RELEASE_25,RELEASE_26,RELEASE_27,RELEASE_28,RELEASE_29,RELEASE_30,RELEASE_31}:refs/heads/svn-tags/* branches = branches/{release_20,release_21,release_22,release_23,release_24,release_25,release_26,release_27,release_28,release_29,release_30,release_31}:refs/heads/* -- With bes...

Hi Anton, On Thu, Apr 26, 2012 at 4:05 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Sebastian, > >> I just saw that the git branch remotes/origin/release_31 has been created >> for llvm.  Unfortunately it is missing the right context: right now I can only >> see 11 patches in that branch with the last patch having no parent. >> >> Could

...these projects wasn't > updated to reflect the actual status of the llvm files. > I checked all the files (removed, moved or added) and now they are ok. > It compiles all targets from the first "Build Solution", both for Debug and > for Release mode. You need the latest release_23 files. I also added a > compiling.txt with some notes. > The .sln and .vcproj files now are updated to the 2008 version of MSVC > Express (my development environment). If you want to keep compatibility with > MSVC 2005, someone with that environment needs to take the old project file...

...> > > 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 >> >> Max >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> >> http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev &g...

On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote: > On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server. While I agree bootstrapping a new mirror from scratch is time and resource consuming,

...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 neither of which seem to exist in the release_23 branch another problem is patch 51237 which among other things renames lib\Transforms\Scalar\SimplifyCFG.cpp to lib\Transforms\Scalar\SimplifyCFGPass.cpp however the removal of lib\Transforms\Ipo\SimplifyLibCalls.cpp is necessary, so it won't build without this patch either. I didn't have...

...;t >> updated to reflect the actual status of the llvm files. >> I checked all the files (removed, moved or added) and now they are ok. >> It compiles all targets from the first "Build Solution", both for Debug >> and >> for Release mode. You need the latest release_23 files. I also added a >> compiling.txt with some notes. >> The .sln and .vcproj files now are updated to the 2008 version of MSVC >> Express (my development environment). If you want to keep compatibility >> with >> MSVC 2005, someone with that environment needs to ta...