<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="-1">A note on the criteria for inclusion into LLVM</font></p>
<p><font size="-1">What does it mean to be included into LLVM?</font></p>
<p><font size="-1">- My impression is that a project becomes part of
the release package.</font></p>
<p><font size="-1">- That there is some responsibility by the LLVM
community or general interest in fixing bugs and providing
updates.</font></p>
<p><font size="-1">For the first item, after downloading the entire
release the user will choose to make use of any given project.
It would appear that some projects in the release are not
commonly of great user interest.</font></p>
<p><font size="-1">For the second item, I would think that for these
less primary projects, that maintenance will likely have a lower
priority and that it will primarily depend on those who have an
interest in that project.</font></p>
<p><font size="-1">My observation is that some projects are not
useful for the core purposes of LLVM and rather it is LLVM that
is useful to the core purposes of some projects. We could remove
some projects without any effect on what I think we could
identify as components that have a necessary LLVM
interdependency.<br>
</font></p>
<p><font size="-1">That we could remove some unnecessary projects
does not require that they no longer have visibility or
relevance to a more inclusive LLVM user group. It rather
suggests we can provide easy visibility, and individual download
and inclusion with LLVM for these satellite projects, of which
there may be many. They become second tier projects. These are
important projects in the larger context but not essential to
the development LLVM.</font></p>
<p><font size="-1">Also in this way the libc project starts
second-tier and may at some point become part of the primary
LLVM project when that useful interdependency can be well
justified.</font></p>
<p><font size="-1">Regards, Neil Nelson</font><br>
</p>
<div class="moz-cite-prefix"><font size="-1">On 7/24/19 1:04 AM,
Rajesh K Singh via llvm-dev wrote:</font><br>
</div>
<blockquote type="cite"
cite="mid:CA+NSXo5THhYG0DAa=fhdqsKkCxZ26u6JRZQFofnEPjDvXio7bQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<p style="font-family:sans-serif;font-size:12.8px">Hello,</p>
<p style="font-family:sans-serif;font-size:12.8px">I have been
following f18 and LLVM for over six months now.I</p>
<p style="font-family:sans-serif;font-size:12.8px">Itwas great
to know that f18’s inclusion in LLVM has been accepted and
approved.</p>
<p style="font-family:sans-serif;font-size:12.8px">I am writing
here to find answer to below points:</p>
<ul
style="margin-bottom:0in;font-family:sans-serif;font-size:12.8px;margin-top:0in"
type="disc">
<li style="margin:0in 0in
0.0001pt;font-size:11pt;font-family:'calibri',sans-serif">Any
tentative timelines by which f18 would be integrated with
LLVM!</li>
<li style="margin:0in 0in
0.0001pt;font-size:11pt;font-family:'calibri',sans-serif">By
when, the f18 would be available for performance evaluation!</li>
<li style="margin:0in 0in
0.0001pt;font-size:11pt;font-family:'calibri',sans-serif">What
is availability of documents (Design docs) for better
understanding of f18 sources!</li>
</ul>
<p style="font-family:sans-serif;font-size:12.8px">Thanks in
anticipation<u>!</u></p>
<p style="font-family:sans-serif;font-size:12.8px">Best Regards,</p>
<p style="font-family:sans-serif;font-size:12.8px">RK</p>
</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>