[llvm-commits] [LLVMdev] RFC: LLVM incubation, or requirements for committing new backends

John Criswell criswell at illinois.edu
Tue Jul 17 09:21:39 PDT 2012


On 7/17/12 9:53 AM, Villmow, Micah wrote:
> [snip]

>   While I completely agree with 4 of the five points below, the requirement that we contribute to core for things that are outside the scope of the backend seems overly onerous.

>   [snip]

>   I would just hate to see these get delayed because of barriers to entry that seem artificial or out of scope of the proposed/required changes.

Just to add my two cents to this discussion, I completely agree with 
Micah that expecting patch submitters to first contribute to other, 
unrelated parts of LLVM is unreasonable.  Some of us contribute to the 
project not by working on the core compiler but by using it in our 
projects.  Most interesting projects (like a code generator) require a 
lot of TLC; developers of such projects do not have time to work on 
unrelated problems.

When someone asks that their code be integrated into LLVM, I think it's 
fair to ask whether there is a long-term maintainer and whether anyone 
will use the new feature(s).  Asking them to make their code more 
maintainable or to conform to coding standards is fair.  Asking people 
to work on unrelated tasks is a waste of their time.

-- John T.




More information about the llvm-commits mailing list