<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Chandler,<br>
<br>
on 2013/3/15 17:15, Chandler Carruth wrote:<br>
</div>
<blockquote
cite="mid:CAGCO0Ki3oW=LjAfEXr7mV_sTmyxageU5mQNj_W7smUpL9hm93Q@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 15, 2013 at 1:54 AM,
Jiong Wang <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jiwang@tilera.com" target="_blank"
class="cremed">jiwang@tilera.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> I agree that
everyone should contribute to keep the community active
and vigorious. But I think there are difference between
contributors.<br>
<br>
some are focused and with expertise on middle end,
while others may on front or back end. so the normal way
for a new contributor is, find a familiar point to
start, then go deeper and wider and expand one's
contribution during this process.<br>
<br>
For Tilera corporation and me, we would like the keep
tilegx backend actively maintained and improved, and
wish it could be a good target to improve and test VLIW,
many core features etc.</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote
cite="mid:CAGCO0Ki3oW=LjAfEXr7mV_sTmyxageU5mQNj_W7smUpL9hm93Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">Inevitably, if you care about LLVM's
support for your platform, you will care about bugs and
features in the target-independent stack of LLVM's software
(including the target independent parts of Clang, etc). There
will be bugs which are priorities only for you and/or your
users, features most pressing only for you or your users, etc.
As such, it seems likely that you will need at least a basic
working familiarity with the stack, and the ability to improve
it in at least basic ways. Simple things like finding and
fixing bugs in the target independent code generator,
improving DAG combine optimizations, or looking for compile
time hotspots are almost always approachable by nearly anyone
on the project.</div>
</div>
</blockquote>
<br>
I am not quite understand your points here, for a backend
maintainer, of course, these things are daily work.<br>
<br>
<blockquote
cite="mid:CAGCO0Ki3oW=LjAfEXr7mV_sTmyxageU5mQNj_W7smUpL9hm93Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra" style="">Essentially, you don't need to
invent a new middle end optimization, or improve the
subtleties of our alias analysis. Most of LLVM, and most of
our bugs/missing features/areas for improvement, involve
straightforward C++ code and systems that anyone who cares can
go in, hack, and improve. That's what occupies the majority of
the maintenance work as it happens. There is relatively little
deeply detailed work requiring specialized knowledge.</div>
</div>
</blockquote>
<br>
Anyway, my question is "how could tilegx backend included in
community repository?", I am here to seek answer for this. I
searched mailinglist archive, and learned R600 and AArch64's request
post, but find few things.<br>
<br>
---<br>
Regards,<br>
Jiong<br>
Tilera Corporation.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>