<div dir="ltr">Ah, OK - thanks for clarifying. So the long and the short of it is that the LLVM project may receive bugs filed from this new source. Fair enough - so long as they've got good (ideally small, portable, etc) reproduction steps, hopefully they'll be actionable/someone can prioritize the fix for them. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 22, 2019 at 12:54 PM Nicholas Krause <<a href="mailto:xerofoify@gmail.com">xerofoify@gmail.com</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">
<div>
<br>
<br>
<div>On 11/22/19 2:46 PM, David Blaikie
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Sorry, I'm not sure I follow/understand your email,
or what sort of replies/responses/discussion you're hoping to
get from it - perhaps you could rephrase and/or provide more
detail?</div>
</blockquote>
<br>
David,<br>
<br>
Sorry its more to give you guys a heads up in case they ask about it
being of interest and know that<br>
its something of interest outside that project. The Yocto and its
related projects are a embedded build <br>
system. Since its goal is to build the whole custom embedded
distribution I've suggested that they start<br>
testing upstream gcc/llvm.<br>
<br>
My reasoning is that while we have a testsuite for both having a
software that builds and supports lots<br>
of real software can be of use. To my knowledge it has the ability
to build over 10000 open source <br>
packages. <br>
<br>
Basically the idea is to automate testing of not just the testsuite
but a suite of real software builds<br>
nightly or so as it takes time to build all that software. You can
of course just build one piece of<br>
software and its dependencies separate through.<br>
<br>
This is a link to the project:<a href="https://www.yoctoproject.org/" target="_blank">https://www.yoctoproject.org/</a><br>
And a link to all the recipes for building software it supports that
are upstreamed: <br>
<a href="https://layers.openembedded.org/layerindex/branch/master/recipes/" target="_blank">https://layers.openembedded.org/layerindex/branch/master/recipes/</a><br>
<br>
The GCC side knows as well but thought I would give you guys the
heads up as well and sorry for not <br>
explaining it better,<br>
Nick <br>
<blockquote type="cite"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Nov 16, 2019 at 3:59
PM Nicholas Krause via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-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">Greetings
All,<br>
<br>
I've already mentioned this on the GCC side but it seems that
the Yocto <br>
Project<br>
<br>
has a class for testing upstream projects. The project is used
for <br>
building embedded<br>
<br>
distributions but due to the ability with bitbake and the
amount of <br>
supported upstream<br>
<br>
projects I've asked them to mention that other projects are
interested <br>
in seeing this<br>
<br>
happen at the usual Embedded Linux/IOT conference meeting they
have yearly.<br>
<br>
Just getting the LLVM side note that its already been
discussed with them,<br>
<br>
Nick<br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div>