similar to: [LLVMdev] Designated Initializers work in clang++

On Jan 13, 2011, at 1:33 PM, Andrey Valyaev wrote: > di.cpp: > ------ > #include <iostream> > using namespace std; > > struct foo { > int a; > int b; > }; > > int main(int, char **) > { > const foo f = { .a = 10, .b = 11 }; > cout << f.a << ' ' << f.b << endl; > return 0; > } > ----- > > $

On 03/07/2011 08:30 PM, Anton Korobeynikov wrote: > Hi David > >> 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 \ >>

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

Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git

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]

Hi David > 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 \ >

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

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

Hi, Has anyone had any success with running different PassManagers on llvm::Modules they've already JITed and are executing? In detail: 1) getting the IR, in form of an llvm::Module 2) calling PassManager->run() on the module 3) calling getFunction() and getPointerToFunction() to JIT the module 4) executing the JITed code using the function pointer received in step 3 and then what I

Hi, I found the following wiki page in the Unladen Swallow project: http://code.google.com/p/unladen-swallow/wiki/CodeLifecycle This would appear to answer my question. Could someone confirm for me if it's definitely unsafe to attempt to optimise/JIT any Modules while a different thread is currently executing a JITed function which has been generated from them? Or am I just missing

On Thu, 24 Jun 2004, Reid Spencer wrote: > I asked Chris about this months ago but there was little interest in > changing it. I thought we were talking about -Weffc++ at that time? > Perhaps we need to file a bug to take care of the warnings it produces > so that LLVm is overloaded virtual clean, then we can turn on checking > for overloaded virtuals. This sounds like a great

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>

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:

Hi Stephen, I confirm your observation. AFAIK the current JIT keeps informations from the module, for example AssertingHandle on Values. It's part of my plan to make the MCJIT independent from Module stuff to allow reoptimizations, or to have multiple copies of JITed functions for one function in the module, but there is a long road to go. Olivier. On Tue, Nov 9, 2010 at 6:57 PM, Stephen

Hi all. I would like to declare a function that takes a function pointer as an argument. In C, it would be : void execute(char (*func)(void*), void *param) So, in my compiler, I have : std::vector<const Type *> cbFPtrArgs(1, Type::getInt8PtrTy(C)); FunctionType * cbFPtrTy = FunctionType::get(Type::getInt8Ty(C), cbFPtrArgs, false); Function * func =

Anton Korobeynikov <anton at korobeynikov.info> writes: > Hello Everyone > > As you might already know, git mirrors of llvm repository started from > repo.or.cz mirrors, where stuff was pushed almost by hands out of > git-svn local copy. Right now we have official and automatically > updated GIT mirrors on llvm.org and thus repo.or.cz mirrors look a bit > redundant.

You need a pointer-to-function type, but FunctionType just gives you a function type. Use PointerType::getUnqual(FunctionType::get(...)). Or TypeBuilder<char (*func)(void*), false>::get(context) from Support/TypeBuilder.h. On Mon, Nov 29, 2010 at 10:37 AM, Salomon Brys <salomon.brys at gmail.com>wrote: > Hi all. > I would like to declare a function that takes a function pointer

On 03/10/2011 02:53 AM, Anton Korobeynikov wrote: > 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. > > :( I

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

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