similar to: [LLVMdev] git patches to svn

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] git patches to svn"

2013 Jan 01
0
[LLVMdev] Git-Svn commit?
On Mon, Dec 31, 2012 at 4:56 PM, Renato Golin <rengolin at systemcall.org> wrote: > With git, I normally issue a pull request, but in LLVM, this won't > work. Is there a FAQ/doc/manual on how to do that or what are the best > practices when working with git? Basically, once you are set up with git-svn (see
2011 Sep 13
1
[LLVMdev] git Status Update?
On 13 September 2011 15:50, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > I guess you have to rebase (pull --rebase or so) your branches. "git > rebase" is relatively smart, and will skip patches that you already have > in your local branch. http://llvm.org/docs/GettingStarted.html#git_mirror "Since the upstream repository is in Subversion, you should use
2012 Dec 31
3
[LLVMdev] Git-Svn commit?
Folks, I'm now using the git mirror, but I'm not sure how to commit changes via git, if at all possible. So far, I'm diffing & applying it on an RW svn tree and committing, but that makes me test twice and it's error prone. I read the manual regarding git-svn setup and all it has is the connection to svn to keep svn's linearity, but nothing on commit strategy. With git,
2013 Dec 21
3
[LLVMdev] running clang format on the Mips target
Hi David, What kind of "a lot of out-of-tree changes"? You should push changes incrementally as you do work. Holding onto changes means that many things, not just reformatting, can make them need to be redone. We frequently clean up and rewrite code to make it cleaner and easier to maintain. We are moving to a more strict internal review and pushing of changes and post commit
2011 Sep 13
0
[LLVMdev] git Status Update?
dag at cray.com (David A. Greene) writes: > But none of this explains how to prevent false conflicts when updating > your git workarea from the svn git mirror. The problem is that dcommit > changes the hash from what's in your local repository to something > different. When you then update from the git mirror, you get a conflict > because two commits with different hashes
2011 Sep 13
4
[LLVMdev] git Status Update?
Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> writes: > dag at cray.com (David A. Greene) writes: > >> Jason Kim <jasonwkim at google.com> writes: >> >>> I believe git has a similar system for maintaining "branches of patches"  >> >> A pointer/tutorial on how to do this would be most welcome. > > It depends on the definition of
2014 Feb 18
2
[LLVMdev] llvm-test lemon
Does anyone know if this is a known xfail? I'm getting a failure for Mips on this but at the same time, ecmascript.y gets errors when running it through lemon for both gccx86 and llvm mips so I don't know if the output is supposed to really compare or not. (This test runs lemon on multiple input files and computes a hash of the result and diffs the hash). All inputs that are not
2013 Feb 04
2
[LLVMdev] is llvm svn server down?
rkotler at ubuntu-rkotler:~/llvm_trunk$ svn update svn: OPTIONS of 'https://rkotler at llvm.org/svn/llvm-project/llvm/trunk': could not connect to server (https://llvm.org)
2015 Feb 04
6
[LLVMdev] llvm builtins
In the following example with gcc style builtins, in once case llvm.powi.f64 is emitted and in the other just a call to library function powf. ~/llvm/build/Debug+Asserts/bin/clang -S -emit-llvm pow1.c Why is that? Is there a way to force the call to an llvm style builtin? Tia. Reed -------------- next part -------------- A non-text attachment was scrubbed... Name: pow1.c Type: text/x-csrc
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:57 AM, David Blaikie wrote: > > > On Thu, Mar 19, 2015 at 9:52 AM, Reed Kotler <reed.kotler at imgtec.com > <mailto:reed.kotler at imgtec.com>> wrote: > > On 03/19/2015 09:38 AM, David Blaikie wrote: >> >> >> On Thu, Mar 19, 2015 at 9:34 AM, Reed Kotler >> <reed.kotler at imgtec.com <mailto:reed.kotler at
2013 Dec 20
4
[LLVMdev] running clang format on the Mips target
We are considering running clang format on the whole Mips target. Is there any rule against this? Is there any good argument against doing this even if there is no rule against it? TIA. Reed
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:38 AM, David Blaikie wrote: > > > On Thu, Mar 19, 2015 at 9:34 AM, Reed Kotler <reed.kotler at imgtec.com > <mailto:reed.kotler at imgtec.com>> wrote: > > On 03/19/2015 09:24 AM, David Blaikie wrote: >> >> >> On Thu, Mar 19, 2015 at 9:18 AM, Reed Kotler >> <reed.kotler at imgtec.com <mailto:reed.kotler at
2015 Mar 19
4
[LLVMdev] Final added to parser<bool>
Well, you are an mclinker contributor and Google uses mclinker and now it's broken as the result of your change. I still don't see any justification to making a change in a public interface that is used by other non LLVM projects to fix some issue with clang warnings. People should be able to derive from those classes. I can't understand your reasoning as to why these classes must
2013 Aug 16
5
[LLVMdev] workflow for linking clang
the good news is that (thanks to Simon) the clang driver is working so well for Mips now that we are more or less switching away from using llc during development for all our various host/target configurations. the bad news is that we have make clang all the time and it is really slow to do that. we used to be able to just make in the lib/target/Mips and then in llc and it was really fast.
2015 Mar 19
2
[LLVMdev] Final added to parser<bool>
On 03/19/2015 09:24 AM, David Blaikie wrote: > > > On Thu, Mar 19, 2015 at 9:18 AM, Reed Kotler <reed.kotler at imgtec.com > <mailto:reed.kotler at imgtec.com>> wrote: > > Well, you are an mclinker contributor > > > Me personally? Not that I know of. Sorry. I thought i had seen your name in an mclinker commit. > > and Google uses mclinker >
2014 Aug 31
2
[LLVMdev] lowering and non legal types in fast-isel
I understand that but falling back makes the compilation slower. I'm wondering what could be done to remove this restriction about fast-isel not being able to handle non legal types. ________________________________________ From: Anton Korobeynikov [anton at korobeynikov.info] Sent: Sunday, August 31, 2014 12:55 AM To: Reed Kotler Cc: LLVMdev at cs.uiuc.edu Subject: Re: [LLVMdev] lowering
2019 Nov 08
2
Workflow to commit changes using git alone (?)
Hi all, I have recently given commit access to LLVM and successfully pushed a test commit from my local master branch. However, I can’t find which is the recommended workflow for committing more serious stuff using git alone. I have read the docs but everything seems to still require svn before bridging to github. I want to use git alone to commit a patch that I got reviewed. I currently have
2014 Feb 25
2
[LLVMdev] configure with clang vs gcc
I see what my problem is here.... I'll continue to move further. Seems like Richards fix is still okay. On 02/25/2014 02:42 PM, Eric Christopher wrote: > On Tue, Feb 25, 2014 at 2:41 PM, reed kotler <rkotler at mips.com> wrote: >> On 02/25/2014 02:38 PM, Eric Christopher wrote: >>> On Tue, Feb 25, 2014 at 2:32 PM, reed kotler <rkotler at mips.com> wrote:
2015 Mar 19
3
[LLVMdev] Final added to parser<bool>
On 03/19/2015 08:55 AM, David Blaikie wrote: > > > On Thu, Mar 19, 2015 at 4:30 AM, Reed Kotler <Reed.Kotler at imgtec.com > <mailto:Reed.Kotler at imgtec.com>> wrote: > > One could argue that mclinker is doing something good or not by > how it's using this class > but I don't see the need for parser<bool> to be final. That is a >
2014 Jun 04
2
[LLVMdev] compiler job open at Mips/Imagination for LLVM and other compiler work
If you apply, please mention me, there is a referral fee. :) _*Software Design Engineer -- Compilers*_ *Opportunity* MIPS SW Team is responsible for enhancement, development and support of the development tools for MIPS processors. You will have some or all of the following responsibilities working as a part of a team: * researching and implementing new techniques and optimisations