<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 02/09/2016 10:05 AM, Chandler
Carruth via llvm-dev wrote:<br>
</div>
<blockquote
cite="mid:CAGCO0Ki3=N_NHbZz0aU3LdKGPVi3DxwaYrvvkwAPNWKYKsXhnw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">On Tue, Feb 9, 2016 at 9:58 AM Hal Finkel via
llvm-dev <<a moz-do-not-send="true"
href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">-----
Original Message -----<br>
> From: "Jacques Pienaar via llvm-dev" <<a
moz-do-not-send="true"
href="mailto:llvm-dev@lists.llvm.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a></a>><br>
> To: <a moz-do-not-send="true"
href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> Sent: Tuesday, February 9, 2016 11:40:21 AM<br>
> Subject: [llvm-dev] [RFC] Lanai backend<br>
<br>
> Hi all,<br>
<br>
Hi Jacques,<br>
<br>
> We would like to contribute a new backend for the Lanai
processor<br>
<br>
I suppose I can guess from your e-mail address who "we" are?<br>
</blockquote>
<div><br>
</div>
<div>Yep!</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> (derived from the processor described in [1]).<br>
> Lanai is a simple in-order 32-bit processor with:<br>
<br>
Can you say a few words about what this is, in what hardware
it appears, and how it can be used? Is this the Myricom
processor? What version(s)?</blockquote>
<div><br>
</div>
<div>This is internal hardware for us, so there's not a lot we
can share, and you can't really grab a version of the
hardware. If that's a problem for the community, I
completely understand.</div>
<div><br>
</div>
<div>Mostly, I wanted to offer to upstream this because it
seems likely about the same utility as the AMDGPU backend
for folks without an AMDGPU, or the XCore backend, etc. It's
small, and we're happy maintaining it and taking on any of
the effort around it. We're also happy with the usual policy
of if the maintainers stop showing up, the backend goes
away.</div>
<div><br>
</div>
<div>But we're working on the backend a bunch, and it didn't
make sense to keep it walled off. Especially if there is
anything that can be reused in other backends and/or if
there is any common infrastructure we need, this makes it
easy to test.</div>
<div><br>
</div>
<div>Still, totally up to the community if they want this. =]</div>
</div>
</div>
</blockquote>
I see no problem with having the backend upstream with the
understanding that all the normal policies apply. Getting more
people working on ToT is valuable to the community as a whole and
provided it's "just another backend" with plenty of tests, the cost
is low. <br>
<br>
Speaking of which, have we ever documented what those policies
actually are?<br>
<blockquote
cite="mid:CAGCO0Ki3=N_NHbZz0aU3LdKGPVi3DxwaYrvvkwAPNWKYKsXhnw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Aside
from the Clang/LLVM support, what other software, drivers,
etc. would be needed to make use of this support? What
versions of that software?<br>
</blockquote>
<div><br>
</div>
<div>This is a question for Jacques, I'll let him fill in the
details.</div>
<div><br>
</div>
<div>-Chandler</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>