search for: release_27

...vm/branches Repository Root: http://llvm.org/svn/llvm-project Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 Revision: 99954 Node Kind: directory Schedule: normal Last Changed Author: dpatel Last Changed Rev: 99943 Last Changed Date: 2010-03-30 17:20:25 -0500 (Tue, 30 Mar 2010) % svn update release_27 svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden (http://llvm.org) I tried update -N release_27 (which worked), then cd release_27 && svn update but no luck. I apparently have no svn-fu....

...svn/llvm-project > Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 > Revision: 99954 > Node Kind: directory > Schedule: normal > Last Changed Author: dpatel > Last Changed Rev: 99943 > Last Changed Date: 2010-03-30 17:20:25 -0500 (Tue, 30 Mar 2010) > > % svn update release_27 > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default' > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden > (http://llvm.org) > > I tried update -N release_27 (which worked), then cd release_27 && svn update > but no luck....

The 2. 7 release branch is created. If you want to check it out, you can issue the following commands: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_27 svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_27 svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_27 svn co https://llvm.org/svn/llvm-project/cfe/branches/release_27 The pre-release tarballs will be available on March 13th for testing. Thanks, Tanya ---...

...ate] 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 -> llvm.org/release_28 = [up to date] release_29 -> llvm.org/release_29 = [up to date] release_30 -> llvm.org/release_30 = [up to date] release_31 -> llvm.org/release_31 = [up to date] release_32 -> llv...

...: $ 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/RELEASE_22 llvm-upstream/svn-tags/RELEASE_23 llvm-upstream/svn-tags/RELEASE_24 llvm-upstream/svn-tags/RELEA...

...; 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 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date] release_31 -> llvm.org/release_31 > = [up to date]...

...2[0-7])" Several problems here: 1. Bunch of additional branches / tags are created due to multiple branch points. I don't recall for llvm, but for clang we'll end with two tags per each release. Something like: $ git branch -r trunk tags/RELEASE_26 tags/RELEASE_26 at 84939 tags/RELEASE_27 tags/RELEASE_27 at 102415 tags/RELEASE_28 tags/RELEASE_28 at 115869 The problem will be much worse with new release branch scheme, basically we'll need to add each branch by hand, etc... 2. We really don't want to push arbitrary branches to git repository. It's really easy to add...

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

...Bunch of additional branches / tags are created due to multiple > branch points. I don't recall for llvm, but for clang we'll end with > two tags per each release. Something like: > $ git branch -r > trunk > tags/RELEASE_26 > tags/RELEASE_26 at 84939 > tags/RELEASE_27 > tags/RELEASE_27 at 102415 > tags/RELEASE_28 > tags/RELEASE_28 at 115869 > > The problem will be much worse with new release branch scheme, > basically we'll need to add each branch by hand, etc... > 2. We really don't want to push arbitrary branches to git re...

On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > Please take a look at all release blockers: > http://llvm.org/bugs/show_bug.cgi?id=6586 5893 is not release-critical according to Doug. 6640 appears to be a test system problem with a patch available (one of the ones you're working on?) Which bugs do you have patches for? I don't want to start looking at something if

Hi, Just realized that ability to generate static object code (e.g. ELF w/o using JIT) is no longer available in 2.7 (at least in release_27 branch). For example > llc -filetype=obj whatever.bc doesn't work in Linux environment anymore (well it wasn't fully implemented before but it worked for simple bytecodes in 2.6). I used to generate code by creating TargetMachine and FunctionPassManager, then calling TargetMachine::a...

...Loc.getFilename() > Loc.getLineNumber() > Loc.getColumnNumber() > .... > } > A grep through my LLVM 2.7 source tree does not find MetadataContext anywhere. Is this something that was added to LLVM mainline after the LLVM 2.7 branch was created? I'm using the release_27 branch of LLVM, so I'm limited to facilities within that branch. -- John T. > } > > Best regards, > --Edwin >

Hi, Thank you, it is just what I need. But... it doesn't work for me: $ clang -S -O0 test.c -mllvm -show-mc-inst error: unknown argument: '-show-mc-inst' $ clang --version clang version 1.1 (branches/release_27) Target: x86_64-pc-linux-gnu Thread model: posix May be I need LLVM with higher version, or mention something in configure options? On Fri, Mar 2, 2012 at 4:32 PM, Benjamin Kramer <benny.kra at googlemail.com> wrote: > > On 02.03.2012, at 09:20, Konstantin Vladimirov wrote: > &...

All, There has been a huge lack of response to the release. We need people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers:

...oject: No rush on this and please take your time. Thanks. Okay, I've created a new LLVM sub-project called Giri(*). It currently contains only the static backwards slicing pass. I'll add the dynamic slicing code to the project later. The static slicing code works with LLVM 2.7 and the release_27 branch of the poolalloc project (the poolalloc project contains our DSA points-to analysis pass which the static slicing code uses to get the program's callgraph). You can get the code using the following SVN command: cd llvm/projects svn co https://llvm.org/svn/llvm-project/poolalloc/bran...

....... >> } >> > > A grep through my LLVM 2.7 source tree does not find MetadataContext > anywhere. Is this something that was added to LLVM mainline after the > LLVM 2.7 branch was created? It should be there, include/llvm/Metadata.h. > > I'm using the release_27 branch of LLVM, so I'm limited to facilities > within that branch. The example I've given is from code way older than the 2.7 branch (Dec 2009 or so). Best regards, --Edwin

On Mar 26, 2010, at 6:24 PM, Peter Shugalev wrote: > Hi, > > Just realized that ability to generate static object code (e.g. ELF w/o > using JIT) is no longer available in 2.7 (at least in release_27 branch). > > For example >> llc -filetype=obj whatever.bc > doesn't work in Linux environment anymore (well it wasn't fully > implemented before but it worked for simple bytecodes in 2.6). > > I used to generate code by creating TargetMachine and > FunctionPassM...

...adapted to compile and run with LLVM 2.7? I'm currently about to start a bigger project using DSA and it would be nice if I could use LLVM 2.7 instead of porting everything I do now from 2.6 to 2.7 later. > Mainline DSA/Poolalloc already compiles with LLVM 2.7. I will probably create a release_27 branch in the near future but have not gotten around to doing it yet. One of our students started some changes to DSA on mainline, so you may want to do some testing to see how well DSA is working before making the plunge to LLVM 2.7. -- John T. > Cheers, > Kevin

Hi Tobias, > The following expression e.g. > > /^.*(?<!trunk|RELEASE_2.).$/m > > uses lookbehind to matches on: Thanks. Clever trick, but... Variable length lookbehind not implemented in regex m/^.*(?<!trunk|RELEASE_2.).$/ at /usr/lib/git-core/git-svn line 4078. :( -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State

...at /usr/lib/git-core/git-svn line 4078. > > :( I got a new one. Today even with working test case: $cat in.txt tags/SVA tags/eh-experimental tags/ggreif tags/non-call-eh tags/RELEASE_28 at 115869 branches/Apple branches/PowerPC-A branches/PowerPC-B trunk tags/RELEASE_28 tags/RELEASE_29 tags/RELEASE_27 $cat rev_match #!/usr/bin/perl -wn print if /.(?<!trunk)(?<!RELEASE_27)$/; $./rev_match in.txt tags/SVA tags/eh-experimental tags/ggreif tags/non-call-eh tags/RELEASE_28 at 115869 branches/Apple branches/PowerPC-A branches/PowerPC-B tags/RELEASE_28 tags/RELEASE_29 Cheers Tobi -------------...