<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I agree with Reid, both on the general usefulness of this
infrastructure and the fact that shouldn't block you from retiring
it if running it isn't worth while for you given the current
usage.</p>
<p>I'll comment that I had been largely unaware this existed. I
vaguely remembered the original announcement, but had no idea this
was still up and running. To the point where I've written
prototype code which does largely the same thing, and was using it
for my own purposes. :)</p>
<p>Can I ask how much this is costing to maintain? Both in terms of
direct cost and operations cost? I've been toying with the idea
of standing up something like this myself for public use and am
curious if my ballpark guesses were accurate. <br>
</p>
<p>Philip<br>
</p>
<div class="moz-cite-prefix">On 7/4/21 11:13 AM, Reid Kleckner via
llvm-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACs=tyJq_gCdDSHPbciv8k3csJrr+xtnZC6f9gq6yV6aP1PWOQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Don't let me stop you from removing the bucket, but
I think this kind of infrastructure would be really handy.
Running `git bisect` directly is awfully slow if the search
requires rebuilding clang at every step, and an archive of
prebuilt compilers can really speed up that search process. I
believe Google has at least two internal clang binary archives
used for this purpose, and I would really prefer to see that
infrastructure externalized.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jul 2, 2021 at 10:59
AM Azhar Mohammed via cfe-dev <<a
href="mailto:cfe-dev@lists.llvm.org" moz-do-not-send="true">cfe-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The
Google cloud storage that we use to upload the compiler build
artifacts (mostly from the Green Dragon CI cluster) will soon
be going away (on July 12th). The primary motivation for it
was the use in bisection (through the `llvmlab bisect` tool
[1]), and it doesn’t look like it is getting used much anymore
(at least not since the move to monorepo as one can now use
`git bisect` directly). Please contact me if you would be
impacted by this, or if you have any thoughts or concerns.<br>
<br>
-<br>
Azhar<br>
<br>
[1] <a
href="https://lists.llvm.org/pipermail/llvm-dev/2015-October/091140.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/pipermail/llvm-dev/2015-October/091140.html</a><br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">cfe-dev@lists.llvm.org</a><br>
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</body>
</html>