search for: release_29

...akumi wrote: > Good morning. > Hi Nakamura, > LLVM and clang can be built successfully on Fedora 12 PS3. > Hooray! :-) > On RC1, only one test failed. > test/CodeGen/X86/fold-pcmpeqd-0.ll > Eric commented that this should be fixed on the release branch right now. > On release_29 branch, all llvm tests can pass. Woo! :-) > (I don't mention clang tests :p ) > >.> > ...Takumi > > > Fedora release 12 (Constantine) > Linux speedking.localdomain 2.6.32.23-170.fc12.ppc64 #1 SMP Mon Sep 27 > 17:09:35 UTC 2010 ppc64 ppc64 ppc64 GNU/Linux &gt...

Good morning. LLVM and clang can be built successfully on Fedora 12 PS3. On RC1, only one test failed. test/CodeGen/X86/fold-pcmpeqd-0.ll On release_29 branch, all llvm tests can pass. (I don't mention clang tests :p ) ...Takumi Fedora release 12 (Constantine) Linux speedking.localdomain 2.6.32.23-170.fc12.ppc64 #1 SMP Mon Sep 27 17:09:35 UTC 2010 ppc64 ppc64 ppc64 GNU/Linux llvm config.status 2.9svn configured by ../../llvm/configure, gen...

...leaseLLVM.html. The major change is in how we do branching and tagging. I want to use a hierarchical version of tags for the various release candidates and final release. The structure of the tags would be something like this. The 2.9 release branch: https://llvm.org/svn/llvm-project/llvm/branch/release_29 The 2.9 release candidate 1: https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/RC1 The 2.9 release candidate 2: https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/RC2 The 2.9 final release (the one we send out to the public): https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/...

...have tried > several versions of LLVM including llvm 2.9 final. I am getting same error again > and again. > > I have successfully build the llvm on another machine with gcc version of 4.3. > > Thanks in advance. > > make[1]: Entering directory > `/home/janarbek/Work/llvm/RELEASE_29/final/trunk/lib/Support' > llvm[1]: Compiling Path.cpp for Debug+Asserts build > In file included from Path.cpp:299: > Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, > std::string*) const’: > Unix/Path.inc:716: error: ‘unlink’ was not declared in thi...

...ate] 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 -> llvm.org/release_32 = [up to date] release_33 -> llvm.org/release_33 = [up to date] release_34 -> llv...

...5 (Ubuntu/Linaro 4.4.4-14ubuntu5)  and I have tried several versions of LLVM including llvm 2.9 final. I am getting same error again and again. I have successfully build the llvm on another machine with gcc version of 4.3. Thanks in advance. make[1]: Entering directory `/home/janarbek/Work/llvm/RELEASE_29/final/trunk/lib/Support' llvm[1]: Compiling Path.cpp for Debug+Asserts build In file included from Path.cpp:299: Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, std::string*) const’: Unix/Path.inc:716: error: ‘unlink’ was not declared in this scope make[1]: *** [/ho...

...eam/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/RELEASE_25 llvm-upstream/svn-tags/RELEASE_26 llvm-upstr...

The patch does inseret unistd.h as below. However, I am still getting exactly same error when I do make.if you have any suggestions please let me know. #if HAVE_UNISTD_H #include <unistd.h> #endif   =========================================== Phone : 82-42-860-1838 Fax : 82-42-860-6790 Cell Phone: 82-10-7599-1981 =========================================== --- On Mon, 10/24/11, Eli

...; 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 -> llvm.org/release_32 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date]...

...have tried > several versions of LLVM including llvm 2.9 final. I am getting same error again > and again. > > I have successfully build the llvm on another machine with gcc version of 4.3. > > Thanks in advance. > > make[1]: Entering directory > `/home/janarbek/Work/llvm/RELEASE_29/final/trunk/lib/Support' > llvm[1]: Compiling Path.cpp for Debug+Asserts build > In file included from Path.cpp:299: > Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, > std::string*) const’: > Unix/Path.inc:716: error: ‘unlink’ was not declared in thi...

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

Is there a tag available for LLVM 2.9? If not what's a good revision # to consider 2.9? r129053? Thanks! Joe Abbey Software Architect Arxan Technologies, Inc. www.arxan.com <http://www.arxan.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Aug 15, 2011, at 6:04 PM, Joe Abbey wrote: > Is there a tag available for LLVM 2.9? > Yes. tags/2.9 in svn. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110815/e22e08ae/attachment.html>

...owing expression e.g. /^.*(?<!trunk|RELEASE_2.).$/m uses lookbehind to matches on: tags/SVA tags/eh-experimental tags/ggreif tags/non-call-eh tags/RELEASE_28 at 115869 branches/Apple branches/PowerPC-A branches/PowerPC-B but not on trunk tags/RELEASE_28 tags/RELEASE_29 tags/RELEASE_27 It probably needs some adjustments to get it right, but I believe this is basically a problem of finding the right regex. > So, right now I'm experimenting with various ways of doing stuff, but > the results looks not pretty good. > If anything would give me a wor...

...lable for check-out. The branch and tag structure > in SVN is detailed on this webpage: > > http://llvm.org/docs/HowToReleaseLLVM.html can you please explain explicitly where to get hold of the branch and tags. The branch seems to live at http://llvm.org/svn/llvm-project/llvm/branches/release_29 but there seems to be nothing relevant under http://llvm.org/svn/llvm-project/llvm/tags Thanks, Duncan.

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

...|RELEASE_2.).$/ 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 To...

Arnold Schwaighofer <arnold.schwaighofer at gmail.com> writes: > We used to have an LLVM-IR pass did tail duplication > (http://llvm.org/viewvc/llvm-project/llvm/tags/RELEASE_29/final/lib/Transforms/Scalar/TailDuplication.cpp) > It was not used and went away with 3.0. The documentation is out of > date. Ah. So is the MachineFunction version expected to work correctly? -David

...ike "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 best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics...

...rogram ] !1 = metadata !{i32 589865, metadata !"foodbg.c", metadata !"/home/deldon/tmp", metadata !2} ; [ DW_TAG_file_type ] !2 = metadata !{i32 589841, i32 0, i32 12, metadata !"foodbg.c", metadata !"/home/deldon/tmp", metadata !"clang version 2.9 (tags/RELEASE_29/final)", i1 true, i1 false, metadata !"", i32 0} ; [ DW_TAG_compile_unit ] !3 = metadata !{i32 589845, metadata !1, metadata !"", metadata !1, i32 0, i64 0, i64 0, i32 0, i32 0, i32 0, metadata !4, i32 0, i32 0} ; [ DW_TAG_subroutine_type ] !4 = metadata !{null} ... As you...