<div dir="ltr"><div dir="ltr">On Mon, May 10, 2021 at 11:40 PM pawel k. <<a href="mailto:pawel.kunio@gmail.com">pawel.kunio@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hi Tom,<div dir="auto">That looks like great quick fix, Im wondering if we could propose data format or computation model change for example to db- or other disk-vs-mem-based where we could lto link huge projects anyway. I wonder whether whole lto data needs to be loaded into mem at once and whether its tree- or other datastructure based.</div></div></blockquote><div><br>That's what ThinLTO is intended to/does address - but has tradeoffs. It has limited whole program data - but better than traditional compilation, since it can use profiling/other analysis to inform how to partition the program.<br><br>- Dave<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto">-Pawel</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">wt., 11.05.2021, 07:26 użytkownik Tom Stellard via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> napisał:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 5/10/21 10:09 PM, Tom Stellard wrote:<br>
> On 5/10/21 10:03 PM, David Blaikie wrote:<br>
>> best to check the bot owners & include them on an email like this? But yeah, if they aren't responsive to stabilizing their bots - certainly open to disabling them straight on the zorg repo.<br>
>><br>
> <br>
> Is there a list of bot owners somewhere?  I tried to dig through the llvm-zorg<br>
> repo to figure out who owned the bot, but I couldn't find anything.<br>
> <br>
<br>
I've learned that there are instructions for finding bot owners in the<br>
Developer Policy: <a href="https://llvm.org/docs/DeveloperPolicy.html#working-with-the-ci-system" rel="noreferrer noreferrer" target="_blank">https://llvm.org/docs/DeveloperPolicy.html#working-with-the-ci-system</a><br>
<br>
It looks like Galina is the owner of these workers.<br>
<br>
-Tom<br>
<br>
> -Tom<br>
> <br>
>> On Mon, May 10, 2021 at 9:59 PM Tom Stellard via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer" target="_blank">llvm-dev@lists.llvm.org</a>>> wrote:<br>
>><br>
>>     Hi,<br>
>><br>
>>     Both the clang-with-lto-ubuntu and clang-with-lto-ubuntu-release builders are<br>
>>     consistently failing due to one of the linker jobs running out of memory.<br>
>>     Is there any easy way to fix these failures (Maybe by using zram?)<br>
>>     If not, can we disable these bots?<br>
>><br>
>>     Thanks,<br>
>>     Tom<br>
>><br>
>>     _______________________________________________<br>
>>     LLVM Developers mailing list<br>
>>     <a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer" target="_blank">llvm-dev@lists.llvm.org</a> <mailto:<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer" target="_blank">llvm-dev@lists.llvm.org</a>><br>
>>     <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a> <<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>><br>
>><br>
> <br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" rel="noreferrer" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
</blockquote></div></div>