similar to: [LLVMdev] git-svn authorship (was: Howdy + GIT)

Below is a copy of the email I sent to llvm-admin. If it is lost in the ether, can you reply on this thread? There's an LLD contributor looking to add an ARMv7 backend. It's a significant contribution so I'd like to land the patch under the correct author. Hi LLVM admins, I'd like to commit patches on behalf of others, but I'm not comfortable simply adding "Patch by

>>>>> On Tue, 3 May 2016 16:36:01 -0400, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> said: Rafael> Care to send a patch deleting it? :-) On the other hand these requests come back from time to time on the mailing list and it is still used in many attics of various projects as a de-facto internal representation to interface with other tools for

+1 On Wed, May 4, 2016 at 3:10 AM, Filipe Cabecinhas via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > On Wed, May 4, 2016 at 9:35 AM, Ronan KERYELL via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >>>>>> On Tue, 3 May 2016 16:36:01 -0400, Rafael Espíndola via llvm-dev < > llvm-dev at lists.llvm.org> said: > > > >

> We have had no trouble using "Patch by <name>" as the form of attribution for a > lot of years with contributions from a wide range of companies. So I'm not really > inclined to change a process which leaves the system of record *exactly* the > same (a textual acknowledgement of attribution) and only makes one mirror of > it superficially better. Adding

The usual advice I provide people is "see what Clang does with an equivalent C construct" On Wed, May 4, 2016 at 12:18 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > Hi, > > There is another benefit to keeping the CppBackend: it's great for > learning how to use the IR and the C++ API in particular, as can be seen > from this SO Q&A: >

On Wed, May 4, 2016 at 3:10 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > As in "look at the source of clang" or as in "look at the -S -emit-llvm" > output? If you mean the former, then would that be easy for someone who > hasn't seen the clang source before? > Generally the latter - then potentially set some breakpoints & look at

On 1 October 2012 18:34, reed kotler <rkotler at mips.com> wrote: > This code is essentially from an LTP test ( http://ltp.sourceforge.net/). > > > #include <stdlib.h> > > int main() { > void *curr; > > do { > curr = malloc(1); > } while (curr); > > return 0; > > } > > If you compile it with no optimization, it will keep

This code is essentially from an LTP test ( http://ltp.sourceforge.net/ <http://ltp.sourceforge.net/> ). #include <stdlib.h> int main() { void *curr; do { curr = malloc(1); } while (curr); return 0; } If you compile it with no optimization, it will keep the malloc calls. If you compile it with -O2, it will create an infinite loop, i.e. assuming that malloc

>>>>> On Mon, 1 Oct 2012 19:40:58 -0700, Nick Lewycky <nlewycky at google.com> said: > On 1 October 2012 18:34, reed kotler <rkotler at mips.com> wrote: > This code is essentially from an LTP test ( > http://ltp.sourceforge.net/ ). > #include <stdlib.h> > int main() {   void  *curr; >   do {     curr =

Perhaps someone can shed some light on the problem I'm having using rsync 2.4.6. I'm getting the following error: receiving file list ... done htdocs/acescounseling/logs/ htdocs/adihome/logs/ . . htdocs/coupons/logs/error_log htdocs/court/logs/combined_log htdocs/cowgirl/logs/combined_log htdocs/cowgirl/logs/error_log htdocs/cowgirl/logs/ssl_log Connection to nova closed by remote host.

On 07/06/2011 07:53 AM, David A. Greene wrote: > Tobias Grosser<tobias at grosser.es> writes: > >>> Will git-cherrypick work or is the merging process going to confuse >>> git-svn? >> >> To use git-svn you should always have a history without any git >> merges. Just commit after commit after commit. I do not know what kind >> of history

Tobias Grosser <tobias at grosser.es> writes: >> Will git-cherrypick work or is the merging process going to confuse >> git-svn? > > To use git-svn you should always have a history without any git > merges. Just commit after commit after commit. I do not know what kind > of history git-cherrypick produces. To clarify, I just need to create the branch at the point

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

I am already successfully generating SPIR-V with a forward port of Khronos’ SPIR-V LLVM. What does one need in order to generate SPIR? From what I gather it is based on a specific LLVM IR version (3.4?) with a bunch of metadata. Is it possible to generate SPIR from LLVM trunk? If so how? Thanks Nic -------------- next part -------------- An HTML attachment was scrubbed... URL:

Rafael Ávila de Espíndola <rafael.espindola at gmail.com> writes: > On 07/05/2011 03:27 PM, David Greene wrote: >> My git-svn fu is not very strong. >> >> In the course of preparing a set of AVX patches, I've committed several >> changes to my local LLVM git clone. I don't want to send all of those >> changes upstream right away. What's the

On 07/05/2011 03:48 PM, David A. Greene wrote: > Rafael Ávila de Espíndola<rafael.espindola at gmail.com> writes: > >> On 07/05/2011 03:27 PM, David Greene wrote: >>> My git-svn fu is not very strong. >>> >>> In the course of preparing a set of AVX patches, I've committed several >>> changes to my local LLVM git clone. I don't want to

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 >

Hi all, I am happy to announce that Synopsys wants to contribute its implementation of 'C99 restrict' to the LLVM project. [1] This implementation is based on Hal Finkel's local restrict patches and on the 'RFC: Full 'restrict' support in LLVM' [2] Any help with extra testing and code review is welcome. To be generally useful, there are also some small gaps [1] that

Hi all, I'm trying to get the llvm's IR from the source code of Polybench (OMP) https://github.com/cavazos-lab/PolyBench-ACC/tree/master/OpenMP. I noticed a considerable difference between the IR generated using clang -emit-llvm -fopenmp and clang -emit-llvm: * using the -fopenmp flag I get a simplified IR in which I read a single basic block where I can highlight a llvm.memcpy

Hi all, Recently I do some jobs based on llvm-link tool. I wonder why link '@llvm.global_ctors' into dest file, even it's not used in dest file? And how can I remove it? Thank you all in advance! Fangqing Xilinx Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: