search for: rudkx

Displaying 15 results from an estimated 15 matches for "rudkx".

2011 Jul 28
4
[LLVMdev] git
> > > Besides, the git-svn readonly bridge is a great solution for those who want > to use git > It seems to be a reasonable solution for those individuals who want to use git, but in my experience not for organizations that want to use git, e.g. have a local server with local branches, with many people banging on that while at the same time continuously merging the LLVM mainline
2011 Jul 28
0
[LLVMdev] git
On Wed, Jul 27, 2011 at 8:59 PM, Mark Lacey <641 at rudkx.com> wrote: > >> Besides, the git-svn readonly bridge is a great solution for those who >> want to use git >> > > It seems to be a reasonable solution for those individuals who want to use > git, but in my experience not for organizations that want to use git, e.g....
2011 Aug 23
5
[LLVMdev] git Status
David, A few comments. > Naming Upstream > --------------- > > The intial clone from upstream results in a git remote reference with > the rather unhelpful name of "origin." As more remote sources get > added, it is easy to forget what "origin" is. Therefore, add a remote > with a more descriptive name. > > git remote add llvm-upstream
2010 Aug 17
1
[LLVMdev] Where can I find an explanation of $src1, $src2, $in, $ptr, etc.?
On Mon, Aug 16, 2010 at 7:42 PM, Bob Wilson <bob.wilson at apple.com> wrote: > > On Aug 16, 2010, at 7:24 PM, Mark Lacey wrote: > > > I have read through the TableGen Fundamentals documentation and been > browsing various .td files. One thing that is not clear to me is where > things like $src1 (as in GR32:$src1) are defined, and what they mean. The > TableGen
2011 Jul 24
0
[LLVMdev] git
> > There is a git tool named "git-flow" that specifically supports this model > and it seems like it might fit the LLVM development model so I wanted to > point it out in case others had not seen it. Perhaps the more core > developers can comment more on its usefulness in the LLVM ecosystem. > > [1] http://nvie.com/posts/a-successful-git-branching-model/ > [2]
2013 Aug 30
1
[LLVMdev] buildbot failure in LLVM on clang-amd64-openbsd
...e,jtsoftware,kevinqin,klimek,kremenek,kuba,labath,lattner,lhames,logan,lvoufo,majnemer,mgottesman,mkuper,mpopa,mren,mspencer,nadav,nicholas,nico,olesalscheider,papin_g,pcc,predmond,rafael,rdivacky,redstar,rengolin,resistor,revane,ributzka,rikka,rkotler,rlytton,rmitton,rnk,row,rsandifo,rsmith,rtrieu,rudkx,ruiu,samsonov,sbaranga,sbenza,sdt,sepavloff,shuxin_yang,silvas,stephenwlin,stoklund,sylvestre,tasiraj,timurrrr,tnorthover,tstellar,uweigand,venkatra,vmedic,void,whunt,wpan,wschmidt,ygao,yjiang > > BUILD FAILED: failed compile > > sincerely, > -The Buildbot > > >
2011 Aug 23
0
[LLVMdev] git Status
Mark Lacey <641 at rudkx.com> writes: > David, > > A few comments. >   > > Naming Upstream > --------------- > > The intial clone from upstream results in a git remote reference with > the rather unhelpful name of "origin."  As more remote sources get >...
2011 Jul 28
1
[LLVMdev] git
Jason Kim <jasonwkim at google.com> writes: > On Wed, Jul 27, 2011 at 8:59 PM, Mark Lacey <641 at rudkx.com> wrote: > > Besides, the git-svn readonly bridge is a great solution for those who want to use git > >   It seems to be a reasonable solution for those individuals who > want to use git, but in my experience not for organizations that > want to use g...
2011 Jul 24
2
[LLVMdev] git
Just to be up-front, I normally work on very small projects and I am very much a non-core LLVM developer (I'm the MicroBlaze backend maintainer). However, we have had success where I work using the git branching model described in [1] and [2]. There is a git tool named "git-flow" that specifically supports this model and it seems like it might fit the LLVM development model so I
2011 Aug 23
0
[LLVMdev] git Status
Mark Lacey <641 at rudkx.com> writes: > git remote add llvm-upstream http://llvm.org/git/llvm.git master > > If the intent is to rename origin, this can be done directly: >   git remote rename origin llvm-upstream Much better. Thanks. > Updating LLVM - no local changes > ---------------...
2010 Jul 24
0
[LLVMdev] -time-passes output from llc
Hi - In looking at the output from -time-passes I notice that there is one set of data for "Instruction Selection and Scheduling", and then another "Pass execution timing report". In looking through the code, it appears that the instruction selection & scheduling time is already accounted for as part of the target machine instruction selection pass that is reported in the
2011 Jan 29
2
[LLVMdev] Official git mirroring of llvm, clang, lldb, test-suite, etc.?
I know this comes up periodically, but it looks like it has been a few months since there was any posting indicating that having an official git mirror for LLVM, et al. was still in the works. I am wondering if there is a timeline or resources lined up to do this mirroring. The distributed nature of git fits very well with any open source development, and it would be great if there were some
2011 Dec 20
2
[LLVMdev] Control dependence analysis?
Does LLVM contain any control dependence analysis pass? I do not see one when looking through the lib/Analysis passes. Thanks, Mark
2010 Jun 15
0
[LLVMdev] [cfe-dev] Reducing the size of LLVM and clang
Is that really going to make a significant difference? I've been looking at the same issue, in my case trying to make a simple JIT (using only LLVM at the time, not trying to use clang to parse and then JIT, but rather deserializing bytecode and JIT it). I made the simplest example I could based on my limited knowledge of the interfaces, and even linking with -dead_strip and optimizing for
2010 Aug 17
3
[LLVMdev] Where can I find an explanation of $src1, $src2, $in, $ptr, etc.?
I have read through the TableGen Fundamentals documentation and been browsing various .td files. One thing that is not clear to me is where things like $src1 (as in GR32:$src1) are defined, and what they mean. The TableGen Fundamentals page seems silent on this, and I have not found other documentation that explains it. Browsing through the .td files has not helped, either (although that has been