Displaying 15 results from an estimated 15 matches for "release_25".
Did you mean:
release_26
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
...ate] 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 -> llvm.org/release_28
= [up to date] release_29 -> llvm.org/release_29
= [up to date] release_30 -> llv...
2011 Oct 06
0
[LLVMdev] svnsync of llvm tree
...hink 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/RELEASE_22
llvm-upstream/svn-tags/RELEASE_23
llvm-upstr...
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
...; 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 -> llvm.org/release_28
> = [up to date] release_29 -> llvm.org/release_29
> = [up to date]...
2010 Feb 15
2
[LLVMdev] Buildbot
Do the buildbots only build debug components? I am seeing lots of this on
trunk with release-style builds:
[x86_64-off-opt]: Failed with signal(SIGABRT) at line 1
[x86_64-off-opt]: while running: llvm-as < /ptmp/dag/llvm-
project.official/llvm/tags/RELEASE_25/test/Transforms/TailDup/basictest2.ll |
opt -tailduplicate -disable-output
[x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'poscnt.1'
[x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'tmp.289'
[x86_64-off-opt]: llvm-as: /ptmp/da...
2011 Oct 06
1
[LLVMdev] svnsync of llvm tree
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
2009 Jan 22
0
[LLVMdev] LLVM 2.5 release branch created
LLVMers,
The 2.5 release branch has been created. You may check it out with the
following commands:
svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25
svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25
svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25
Please do not commit anything to the release branch. If you have a
patch that needs to be merged in, you must get it approved by a code
owner and for...
2009 Feb 03
0
[LLVMdev] 2.5 Branch Created
LLVMers,
The 2.5 release branch has been created. You may check it out with the
following commands:
svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25
svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25
svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25
Please do not commit anything to the release branch. If you have a
patch that needs to be merged in, you must get it approved by a code
owner and for...
2009 Mar 03
1
[LLVMdev] Patch for GettingStarted.html
Hey,
I have written a few lines about Release and Debug Builds (SVN checkout
vs. LLVM distribution). I've also added the RELEASE_25 tag to the tags
list and corrected a typo.
Can someone please review? As I'm not a native speaker/writer it may
contain strange wording/spelling mistakes ;). Any feedback welcome.
BR
Josef
--
zapster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: docpatch....
2010 Feb 15
0
[LLVMdev] Buildbot
....com> wrote:
> Do the buildbots only build debug components? I am seeing lots of this on
> trunk with release-style builds:
>
> [x86_64-off-opt]: Failed with signal(SIGABRT) at line 1
> [x86_64-off-opt]: while running: llvm-as < /ptmp/dag/llvm-
> project.official/llvm/tags/RELEASE_25/test/Transforms/TailDup/basictest2.ll |
> opt -tailduplicate -disable-output
> [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'poscnt.1'
> [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'tmp.289'
> [x86_64-off-opt]:...
2012 Apr 27
0
[LLVMdev] git branch release_31
...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 best regards, Anton Korob...
2012 Apr 26
2
[LLVMdev] git branch release_31
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
2011 Aug 29
2
[LLVMdev] svnsync of llvm tree
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,
2009 Feb 20
0
[LLVMdev] libLTO warning
...took place at just the wrong time and
picked up a change when I tried to have libLTO build on Linux as well.
That change should never have made it into the 2.5 branch.
Tanya, could you please revert 62987 from the 2.5 branch? It's this patch:
http://llvm.org/viewvc/llvm-project/llvm/branches/release_25/tools/Makefile?r1=62895&r2=62987
fortunately just a one-liner. I'm really sorry for the trouble...
Nick
>
> Kind regards,
> Maurice
>
>
> ------------------------------------------------------------------------
>
> _____________________________________________...
2009 Feb 20
2
[LLVMdev] libLTO warning
Hi all,
I just svn-updated the 2.5 branch on my machine and I noticed this warning
during the build.
*** Warning: Linking the shared library
/home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool
*** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o
/home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o
/home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o
2011 Oct 06
0
[LLVMdev] MIPS 32bit code generation
...hink 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/RELEASE_22
llvm-upstream/svn-tags/RELEASE_23
llvm-upstr...