<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Hal,<div class=""><br class=""></div><div class="">The project is still early and we’ve been working on building out some core infrastructure. There are lots of things (including existing synthesis frontends) that could benefit from this work. I’d love to see folks interested in clang integration join the group!</div><div class=""><br class=""></div><div class="">-Chris<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 5, 2020, at 8:28 AM, Hal Finkel via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div class=""><p class="">Hi, Steve,</p><p class="">I think it would be great to have hardware-synthesis capabilities
in the LLVM project. The incubation process discussion may be
ongoing, but as that settles, this seems like a good candidate to
me.</p><p class="">Out of curiosity, many existing HLS tools use C/C++-derived input
languages, and as Clang produces LLVM, do you have any plans for a
converter between LLVM and your MLIR dialects? Or are you just
targeting other kinds of frontends?</p><p class="">Thanks again,</p><p class="">Hal<br class="">
</p>
<div class="moz-cite-prefix">On 7/4/20 5:29 PM, Stephen Neuendorffer
via llvm-dev wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAO0d_3AOz9xx69rorunBFLQmqwFAKeU8pFtemumvL8j20o=3Lw@mail.gmail.com" class="">
<div dir="ltr" class=""><span id="gmail-docs-internal-guid-74a8d807-7fff-8a08-78b6-99bcf7722c77" class=""></span><br class="">
<div class=""><span style="background-color: transparent; font-family: Arial; font-size: 11pt; white-space: pre-wrap;" class="">For the past several months, members of the ‘CIRCT’ group have been working to begin adapting MLIR for hardware design. We believe that this area would benefit from good open source infrastructure enabling research and, eventually, the next generation of commercial tools. We have collected several dialects and envision a number of lowering flows using these dialects. We have reached the point where we are ready to share our ideas more widely and would like to be considered as an LLVM incubator project.</span><br class="">
</div>
<div class=""><span style="font-size: 11pt; font-family: Arial; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;" class="">
Our code exists at </span><a href="https://github.com/circt" style="text-decoration-line:none" moz-do-not-send="true" class=""><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap" class="">https://github.com/circt</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;" class=""> as an out-of-tree MLIR project and our group charter can be found at </span><a href="https://github.com/circt/circt/blob/master/README.md" style="text-decoration-line:none" moz-do-not-send="true" class=""><span style="font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap" class="">https://github.com/circt/circt/blob/master/README.md</span></a><span style="font-size: 11pt; font-family: Arial; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;" class="">. We have weekly discussions with a group of about 20 people from Xilinx, SiFive, Microsoft, PNNL, ETH Zurich, EPFL, Stanford, and Cornell, and welcome additional contributions. This project is still early and we see many elements as highly experimental. At the same time, we feel that the only way to vet these ideas is to build larger systems which will likely take some time and community investment. The LLVM incubator process would be a good way to help us organize this effort.</span></div>
<div class=""><br class="">
</div>
<div class="">Steve Neuendorffer</div>
<div class="">Xilinx Research Labs <span class=""><span style="font-size: 11pt; font-family: Arial; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap;" class="">
</span></span></div>
</div>
<br class="">
<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>
<pre class="moz-signature" cols="72">--
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
</div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></body></html>