[cfe-dev] "clang.org"

"C. Bergström" cbergstrom at pathscale.com
Tue Nov 12 21:04:03 PST 2013


On 11/13/13 11:29 AM, Sean Silva wrote:
>
>
>
> On Tue, Nov 12, 2013 at 2:56 AM, Alp Toker <alp at nuanti.com 
> <mailto:alp at nuanti.com>> wrote:
>
>     On the other hand, there have been some really interesting suggestions
>     coming in (VCS for experimental branches, a diagnostics wiki for
>     clang,
>     user-friendly distribution of clang and more) so I'll be handing
>     off to
>     another LLVM developer in the community who knows better how to
>     set that
>     up whether it's on llvm.org <http://llvm.org>, clang.org
>     <http://clang.org> or some combination.
>
>     Incidentally, is there a less contentious 'official' place LLVM
>     contributors can upload patches/builds like an FTP?
>
>
> Generally, we don't do that. Sort of like how we don't do branches 
> either; there's "one true mainline". We do have some "hosted 
> binaries", e.g. <http://llvm.org/apt/>, <http://llvm.org/builds/> but 
> AFAIK those are strictly derived from trunk, and I don't think that it 
> would be appropriate to host custom patched builds (I think the 
> philosophy is basically "if the patch is worth applying, then it will 
> be in trunk soon").
I strongly disagree - Testers are the compilers best friend. I'm not 
suggesting this is what it's used for.. just a hypothetical I'm tossing 
out..

What if not only a patch from reviews.llvm.org, but also some binaries 
to download? I'm sure there are a group of users who for whatever reason 
don't want to setup a build, patch it, build it and then test. The 
process would be - download it, bang on it and let us know if you think 
it's ready or you hit a problem.

Who would this serve? Performance testing / validation is my 1st 
thought... 2nd thought is anything just risky... before a final release 
you have multiple release candidates.. If one of those is bad - how do 
you as a user triage what might have caused a problem. This "alpha" 
level, nightly build or "patch/review" build serves as a stopgap between 
releases for adventurous (users).





More information about the cfe-dev mailing list