search for: release_28

Hello all, According to: http://llvm.org/releases/2.8/docs/GettingStarted.html#checkout folks can check out a specific release from Subversion. As of right now, RELEASE_28 contains folders for each of the release candidates, as opposed to the final content. Same goes for Clang. -Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101006/392c5f85/attachment.html>

...ltiple > 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 branch by an ac...

Bill Wendling <wendling at apple.com> writes: > On Dec 6, 2010, at 9:31 AM, David Greene wrote: > > Is there a reason there is no RELEASE_28 tag for test-suite? > > SVN wouldn't allow me to make one. So getting the latest release_28 branch should be equivalent, yes? I just want to make sure we have a way to test 2.8 long-term. -Dave

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

...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 branch by an accident, so it will be much bet...

Is there a reason there is no RELEASE_28 tag for test-suite? -Dave

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

...er trick, but... > > Variable length lookbehind not implemented in regex > m/^.*(?<!trunk|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 1...

...pstream/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/RELEASE_25 llvm-upstream/svn-t...

...cute the JITed code instead. As an added complication, different threads may be performing the initial compilation or reoptimisation, but before we consider this, is there any reason why the above shouldn't work? When I do it, I occasionally get assertion errors such as: <more path...>/RELEASE_28/include/llvm/ADT/APInt.h:819: bool llvm::APInt::operator==(const llvm::APInt&) const: Assertion `BitWidth == RHS.BitWidth && "Comparison requires equal bit widths"' failed. Stack dump: 0. Running pass 'Function Pass Manager' on module 'lib0000'. 1. Running...

...; 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 -> llvm.org/release_32 > = [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

...; As an added complication, different threads may be performing the > initial compilation or reoptimisation, but before we consider this, is > there any reason why the above shouldn't work? > > When I do it, I occasionally get assertion errors such as: > > <more path...>/RELEASE_28/include/llvm/ADT/APInt.h:819: bool > llvm::APInt::operator==(const llvm::APInt&) const: Assertion `BitWidth > == RHS.BitWidth && "Comparison requires equal bit widths"' failed. > Stack dump: > 0.      Running pass 'Function Pass Manager' on module '...

On Dec 6, 2010, at 9:31 AM, David Greene wrote: > Is there a reason there is no RELEASE_28 tag for test-suite? > SVN wouldn't allow me to make one. -bw -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101207/c87515cd/attachment.html>

...fferent threads may be performing the > > initial compilation or reoptimisation, but before we consider this, is > > there any reason why the above shouldn't work? > > > > When I do it, I occasionally get assertion errors such as: > > > > <more path...>/RELEASE_28/include/llvm/ADT/APInt.h:819: bool > > llvm::APInt::operator==(const llvm::APInt&) const: Assertion `BitWidth > > == RHS.BitWidth && "Comparison requires equal bit widths"' failed. > > Stack dump: > > 0. Running pass 'Function Pass Manager&...

...8PtrTy(C)); FunctionType * cbFPtrTy = FunctionType::get(Type::getInt8Ty(C), cbFPtrArgs, false); Function * func = cast<Function>(M->getOrInsertFunction(fName, Type::getInt32Ty(C), cbFPtrTy, Type::getInt8PtrTy(C), (Type *)0)); But then I get an error form LLVM : /home/salomon/AppSRC/LLVM/release_28/lib/VMCore/Type.cpp:456: llvm::FunctionType::FunctionType(llvm::Type const *, std::vector<llvm::Type const *> const &, bool): Assertion `isValidArgumentType(Params[i]) && "Not a valid type for function argument!"' failed. It seems that a FunctionType is not a valide...

...; int main(int, char **) { const foo f = { .a = 10, .b = 11 }; cout << f.a << ' ' << f.b << endl; return 0; } ----- $ clang++ -Wall -Wextra -Weffc++ -o di di.cpp $ ./di 10 11 It is a standard C99! Or am I wrong? $ clang++ --version clang version 2.8 (branches/release_28) Target: i386-pc-linux-gnu Thread model: posix -- http://mdf-i.blogspot.com Andrey Valyaev

...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 Korobeynikov Faculty of Mathematics an...

NAKAMURA Takumi <geek4civic at gmail.com> writes: > Matthieu, > > On Tue, Mar 1, 2011 at 8:02 AM, Matthieu Moy > <Matthieu.Moy at grenoble-inp.fr> wrote: >> At some point in the past, an anti-git-svn system had been set up on >> llvm.org. Has this been disabled since? I don't manage to do much with >> git-svn: > > Maybe sure. Anton said it is

...e counterproductive to provide a repo.or.cz mirror at all, because people will think it's a "proper" git repository when it really isn't. BTW, the llvm.org git-svn mirror is for trunk only, right? How difficult would it be to include the latest release tag in the git-svn mirror (RELEASE_28 right now)? This would greatly help people that work with the latest release of llvm rather than trunk. -Dave