search for: release_

...h branches is the lockdown of the root repository directory. I tried something like this but it breaks due to the restrictions: git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Obviously, replace <user> with whatever it needs to be to allow dcommit to work. Ideally we'd have clang and llvm-gcc git mirrors as well via the --prefix argument to git-svn init, but let's n...

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 disabled to access upper directories with svn. Thus, we (accessing llvm.org remotely) cannot do

...gt; I think the trouble with branches is the lockdown of the root repository > directory. Surely not (at the server) > git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >  --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_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...

The source is cloned from https://github.com/llvm-mirror/llvm Thanks. Zhoulai On Thu, Apr 9, 2015 at 9:15 AM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > On 4/9/15 9:58 AM, Zhoulai wrote: > >> Hi, I am using LLVM to develop a tool, using Mac OS 10.9. I have >> download llvm source and binary from >> >>

...end series. I've made a number of changes and attempted to incorporate all the feedback from the last review. Some highlights: 1) Clean up the paravirt time source patch to use a more Xen-like model 2) Change the hypercall queueing to pass a PA on the flush hypercall 3) Add MMU support for release_{pt,pd} and TLB flush 4) Use KVM specific errno values 5) Switch from per_cpu to more appropriate functions As for performance, I've got a few interesting results. kbuild with a guest using 2G of memory goes from 19 minutes to 12 minutes with the full series applied. Using 512mb, the build...

...end series. I've made a number of changes and attempted to incorporate all the feedback from the last review. Some highlights: 1) Clean up the paravirt time source patch to use a more Xen-like model 2) Change the hypercall queueing to pass a PA on the flush hypercall 3) Add MMU support for release_{pt,pd} and TLB flush 4) Use KVM specific errno values 5) Switch from per_cpu to more appropriate functions As for performance, I've got a few interesting results. kbuild with a guest using 2G of memory goes from 19 minutes to 12 minutes with the full series applied. Using 512mb, the build...

...ister. The main trouble here is that the X86 backend appears to respect LLVM memory model instead of the x86-TSO memory model, and may reorder instructions. In order to prevent illegal reordering of atomic accesses, the backend converts atomic accesses to pseudo-instructions in X86InstrCompiler.td (RELEASE_MOV* and ACQUIRE_MOV*) that are opaque to most of the rest of the backend, and only lowers those at the very end of the pipeline. I have decided to follow the same approach, just adding some more RELEASE_* pseudo-instructions rather than trying to find every possibly misbehaving part of the backend...

Would someone please merge commit 89091 from the mainline into release_26? Thanks, --Patrick Duncan Sands wrote: > Hi Patrick, > > >> I think these changes should be pretty uncontroversial. Would someone >> with commit authority please apply this for me? >> > > thanks for the patch. Applied in commit 89091. > > Ciao,...

...lines to your sources.list if you run stable, > which > | doesn't get updated, or if you're running testing close to the time > of a > | new release. Which is probably 12 to 18 months off at least. > > c) You can also add the CRAN "stable" port to run _current R release_ > on > Debian testing via CRAN, just what Petar asked for. Given that these > were > built on 'stable' it is highly likely that they will work on > 'testing'. > > So use the lines Paul sent to r-help in response to your earlier post: > > # Add R-rep...

On Feb 28, 2011, at 10:01 AM, David A. Greene wrote: > Chad Colgur <colgur at gmail.com> writes: > >> Will the 2.9 branch be reflected in the git mirrors? > > I really, really hope this is the case. The official git mirror > documentation says it is only trunk because the current branching scheme > in not suitable for git. I don't understand why that would be

...e with branches is the lockdown of the root repository >> directory. > Surely not (at the server) > >> git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \ >> --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_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 rel...

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to

...now offers a "closed source" unified driver as well. 8) My final comments The reality is that video card products are _obsoleted_ within 12 months. GPUs double in performance 2-3 times faster than CPUs, which means driver development goes hand-in-hand with engineering development _pre-release_. In other words, we can dream of a day where there is no cutting-edge intellectual property in GPUs so vendors can release drivers as GPL, and not have to hack kernel interfaces because of 3rd party NDA obligations. But the idea that video card drivers can be community developed means that their...