similar to: [LLVMdev] llvm.org git mirror down?

Bob, > Does anyone know if the llvm.org git mirror is down or just slow?  The clang repo is missing about the last 2 hours of commits. It seems that new user was added on llvm.org improperly (I have to check who and how did this actually). Thus we have no svn mailer entry for Aaron => git mirror stopped working. I'm going to fix stuff asap. -- With best regards, Anton Korobeynikov

> for Aaron => git mirror stopped working. > I'm going to fix stuff asap. Should be working now. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Yeah, it seems that the time the mirror was created there were no release branches and therefore nothing was exported :) On Fri, Nov 20, 2015 at 8:13 PM, Hans Wennborg <hans at chromium.org> wrote: > On Thu, Nov 19, 2015 at 2:38 PM, Martell Malone via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi All, >> >> I am currently trying to test out a few things

Thanks, Anton. I always forget about llvm-admin :). I'd say converting all branches would be best, would help track the MCJIT work for example. Gaël, does that sound good to you? You're the one making all the commits these days :). ~Will On Sun, Jan 5, 2014 at 9:03 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello > > I can create a mirror, this is not

Hi all, Don't suppose VMKit could be added to the set of subprojects with official git mirrors? Please and thank you! :) ~Will

Strange, seems to be working now on Linux, I had checkedout and used a clen build tree. Sorry for the noise. Aaron 2009/6/22 Anton Korobeynikov <anton at korobeynikov.info> > > Still not working, what does TOT stand for ? > Top Of the Tree. Works for me and Duncan also confirmed that it works > for him. Try to clean your build directory. > > -- > With best

Dear All, The release tarball was just reverted to old (original) state. This is what I have locally: $ shasum llvm-3.2.src.tar.gz 42d139ab4c9f0c539c60f5ac07486e9d30fc1280 llvm-3.2.src.tar.gz Please let me know asap, if something is still broken. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi I am running into a legalize dag issue after custom lowering a load. If someone can give me pointers that would be great. I am using llvm 2.6 When custom lowering a load, the following code gets executed. Tmp1 = TLI.LowerOperation(Tmp3, DAG); if (Tmp1.getNode()) { Tmp3 = LegalizeOp(Tmp1); Tmp4 = LegalizeOp(Tmp1.getValue(1)); <----------------- what

I am getting an "--emit-llvm is not supported in this configuration" error on a release build on Cygwin, the debug build is fine. make[3]: Entering directory `/usr/build/llvm/runtime/GCCLibraries/libc' llvm[3]: Compiling atox.c for Release build (bytecode) llvm-gcc: --emit-llvm is not supported in this configuration. make[3]: ***

Hi, Has there been discussion about having svn mirror git instead of vice versa? I've been happy with the git+cmake+ninja combo for a while now, but the online docs suggests this configuration is second-class to svn+autotools+make. Is the community transitioning to any particular configuration? Thanks, Greg On Wed, Nov 14, 2012 at 9:19 AM, Anton Korobeynikov <anton at

Hi, I am getting the following error message :- llvm[1]: Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAlphaAsmPrinter.a libLLVMAlphaCodeGen.a llvm[1]: Building llvm-config script. cat: /home/ang/build/dev/tools/llvm-config/FinalLibDeps.txt: No such file or directory make[1]: ***

Is there any overview or detailed socumentation on LLVM PIC ? Many thanks in advance, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090613/8b6b5719/attachment.html>

> The extra branches that Anton added to clang.git didn't rewrite anything. > Here's hoping it won't be necessary for llvm.git either. I was hoping that the rebuilt won't change the sha's and noone will notice anything (well, except those who already branched out of branches / tags). But it seems that after rebuild stuff was changed (I really dunno, why). So, we'll go

Hello Everyone I'm going to rebuild GIT mirrors to provide more consistent tags / branches. Basically, the contents will be the same, but naming scheme will change. So, trunk will go to svn/trunk, branches/* will got to svn/branches/* and tags/* will go to svn/tags/* This might break some scripts, etc. So, if anyone has some objections wrt this - please let me know. PS: First clang.git

Anton, Sorry I have not replied earlier. Can I ask what platform ABI's are documented other than Itanium ? I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF and MachO backends. Thanks, Aaron 2009/6/15 Anton Korobeynikov <anton at korobeynikov.info> > Hello, Aaron > > > Is there any overview or detailed socumentation on LLVM PIC ? > Did you

On Mon, Apr 25, 2016 at 1:26 PM, Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I wish we could just get the viewvc working or set up some kind of > forwarding from those URLs to something that works. > > There are tons and tons of links pointing to the viewvc which are now > broken, including the archives of all commit emails. I share in that desire; the

Is this going to rewrite the entire history of everything on trunk? If I have a local git repo that has been pulling from the existing mirror, what will be the implications of your change? On Mar 10, 2011, at 8:04 AM, Anton Korobeynikov wrote: > Hello Everyone > > I'm going to rebuild GIT mirrors to provide more consistent tags / branches. > Basically, the contents will be the

Anton Korobeynikov <anton at korobeynikov.info> writes: > Dear All, > > The release tarball was just reverted to old (original) state. > > This is what I have locally: > > $ shasum llvm-3.2.src.tar.gz > 42d139ab4c9f0c539c60f5ac07486e9d30fc1280 llvm-3.2.src.tar.gz > > Please let me know asap, if something is still broken. I'm confused. Does the release

> Just to be clear: we _really_ do not want all the sha's to change for trunk. Yes. That's why I said there will be other way :) In any case - please try clang.git once again. It should contain new branch/tag layout. If there will be some problems - let me know and I'll revert to prev. repository. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics,

This has been discussed many times. Might want to take a look in the mailing list archives. :) cmake and autotools are on roughly equal footing at this point with chandler and I handling each of them respectively and fairly quickly. git vs. svn is a different story though. -eric On Thu, Nov 15, 2012 at 8:31 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi, > > Has there