Displaying 19 results from an estimated 19 matches for "release_16".
Did you mean:
release_19
2005 Nov 02
3
[LLVMdev] LLVM 1.6 Release Branch
Dear All,
I've created the LLVM release branch (CVS tag release_16).
Those developers wanting to commit changes to LLVM without having your
changes go into LLVM 1.6 can now commit to CVS mainline to your heart's
content.
:)
TESTING:
--------
1. I'm still looking for volunteers to test MacOS X and Solaris. If
you'd like to volunteer, please ema...
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
I.e., I see this when I run `git fetch`:
```
$ git fetch -v llvm.org
From http://llvm.org/git/llvm
= [up to date] master -> llvm.org/master
= [up to 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 -> llv...
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
...-dev at lists.llvm.org> wrote:
> I.e., I see this when I run `git fetch`:
> ```
> $ git fetch -v llvm.org
> From http://llvm.org/git/llvm
> = [up to date] master -> llvm.org/master
> = [up to 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]...
2005 Nov 07
1
[LLVMdev] LLVM 1.6 Release Branch
...t;> and out of my $PATH.
>
>
> I get the error with and without the --with-f2c option. I never used the
> NAG Fotran option. It works fine if I specifically use bash.
Can you do a "cvs status configure" on your llvm-test configure script
and make sure the sticky tag is release_16?
Also, does the configure process halt? Or does it just give an error
and keep going?
>
>> Can you verify that the configure script works for you without the
>> --with-f2c option? If it does, I think we'll just file a bug report
>> and fix it in 1.7.
>
>
>...
2009 Nov 14
1
[LLVMdev] SAFECode Source Code Released
...>
>>
>
> Hi John,
>
> This is great news!
> I'm reporting to you some problem I've found below, please tell me if
> I'm doing anything wrong.
>
> The docs/Install.html however says this:
> svn co http://llvm.org/svn/llvm-project/llvm/branches/release_16 llvm
>
> That looks like a typo and you meant release_26?
>
>
Indeed! Sorry for that error; I've corrected it in the documentation.
Thanks for catching that!
I'll take a look at the other issues you've mentioned later (I'm working
on a course project this weekend...
2011 Oct 06
0
[LLVMdev] svnsync of llvm tree
...>> llvm projects is svn, I'd just as soon use svn as the tool at my end.
> The git mirrors only 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/RELE...
2005 Nov 07
0
[LLVMdev] PowerPC Regressions for LLVM 1.6
...to mainline is just a lot easier than merging individual revisions
into the branch.
:)
If you need help with committing stuff to the release branch, just email
the list or ask me on the IRC channel. This gist of it is that you get
a working copy from CVS with the release branch tag (cvs co -r
release_16) and then do your commits in that working copy (all commits
will automatically go into the release_16 branch).
Thanks again, everbody, for your help with this release. I think we'll
be getting it out either today or tomorrow if everything goes well.
-- John T.
--
John T. Criswell
Researc...
2010 Jul 22
0
[LLVMdev] Is there a guide to LLVM's components?
David Piepgrass <dpiepgrass at mentoreng.com> writes:
> One thing that helps me understand complex software is a dependency
> graph. I found an LLVM dependency graph at
>
> https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies
>
> but it's really messy and hard to follow. From that graph I made a
> cleaner graph by hand (attached)... sorry about the fax-quality
> scan. But I have some questions about it...
>
>
> - How old is this graph?
It is for th...
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
2010 Jul 22
2
[LLVMdev] Is there a guide to LLVM's components?
One thing that helps me understand complex software is a dependency graph. I found an LLVM dependency graph at
https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies
but it's really messy and hard to follow. From that graph I made a cleaner graph by hand (attached)... sorry about the fax-quality scan. But I have some questions about it...
- How old is this graph?
- Is anything missing? (e.g. only S...
2013 Dec 17
0
[LLVMdev] Add call printf instructions problems
> But I got another problems. I successfully compile the pass and I can insert
> the call printf (C Lib function) instructions in the LLVM IR(eg: call.bc).
> If the call.bc didn't contain call printf instruction ,I can call printf
> successfully ,but if not ,there exists a problem. the llvm will rename my
> inserted call function , and the transformed code can not run correctly!
2012 Nov 16
0
[LLVMdev] [cfe-dev] 3.2 Release has branched :T+2 hours
Should be there
On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote:
> Anton, please add release_32 also in;
>
> clang-tools-extra
> compiler-rt
> dragonegg
> libcxxabi
> lldb
>
> They have release_32 in svn. I don't know they might be released, though.
>
> And, could you suppress generating refs/heads/svn-tags and prune them
2010 Jul 22
1
[LLVMdev] Is there a guide to LLVM's components?
> > I found an LLVM dependency graph at
> >
> > https://llvm.org/svn/llvm-
> project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies
> >
> > but it's really messy and hard to follow. From that graph I made a
> > cleaner graph by hand (attached)... sorry about the fax-quality
> > scan. But I have some questions about it...
> >
> > - How old is...
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,
2012 Nov 16
2
[LLVMdev] [cfe-dev] 3.2 Release has branched :T+2 hours
Anton, please add release_32 also in;
clang-tools-extra
compiler-rt
dragonegg
libcxxabi
lldb
They have release_32 in svn. I don't know they might be released, though.
And, could you suppress generating refs/heads/svn-tags and prune them for now?
I am sure that orphan branches will stress the llvm.org server to
begin git-pack-ing whole tree.
...Takumi
2012/11/15 Anton Korobeynikov
2005 Nov 07
0
[LLVMdev] LLVM 1.6 Release Branch
>> Everything builds fine on sparc. The configure script needs to be fixed
>> though (see previous email).
>
> I'm not getting the error with the configure script (on Kain, anyway). I've
> tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my
> $PATH.
I get the error with and without the --with-f2c option. I never used the
NAG Fotran
2013 Dec 17
2
[LLVMdev] Add call printf instructions problems
Thanks,Cheers!
I found the problem is that the "Function *call_print" using the same name
as the “class call_print”, which made the compiler wrongly resolved the
call_print type!
But I got another problems. I successfully compile the pass and I can
insert the call printf (C Lib function) instructions in the LLVM IR(eg:
call.bc). If the call.bc didn't contain call printf
2005 Nov 07
4
[LLVMdev] LLVM 1.6 Release Branch
Tanya Lattner wrote:
>
> Everything builds fine on sparc. The configure script needs to be fixed
> though (see previous email).
I'm not getting the error with the configure script (on Kain, anyway).
I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and
out of my $PATH.
Can you verify that the configure script works for you without the
--with-f2c option?
2011 Oct 06
0
[LLVMdev] MIPS 32bit code generation
...he
>> llvm projects is svn, I'd just as soon use svn as the tool at my end.
> The git mirrors only 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/RELE...