llvm dev - Jul 2020 - Proposal for CIRCT incubator project

> On Jul 8, 2020, at 8:52 AM, Renato Golin via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> It would be nice to have an external MLIR user in the project, and
> this project seems really well organised and relevant. +1 from me,
> too.
I think that flang beat us to the punch as the first external MLIR user :-) but
thank you for your support Renato!

-Chris
> 
> On Sat, 4 Jul 2020 at 23:30, Stephen Neuendorffer via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> 
>> 
>> 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.
>> Our code exists at https://github.com/circt as an out-of-tree MLIR
project and our group charter can be found at
https://github.com/circt/circt/blob/master/README.md.   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.
>> 
>> Steve Neuendorffer
>> Xilinx Research Labs
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

On Wed, 8 Jul 2020 at 22:43, Chris Lattner <clattner at nondot.org>
wrote:
> I think that flang beat us to the punch as the first external MLIR user :-)
but thank you for your support Renato!
Ah, but Flang is in the monorepo and builds together with LLVM, while
CIRCT (and my current project, Verona) "uses" MLIR/LLVM externally (as
a submodule).

There are a number of build issues in both LLVM and MLIR that make it
awkward for projects in that category to use the LLVM libraries and
having a project in the llvm group will give us an "official" reason
to solve those problems more efficiently.

I've been meaning to start a thread on that, but I need to collect all
the build issues I had in an email so we can discuss them. Not for
this thread, though. :)

cheers,
--renato

Renato, I'm happy to kibitz on the build problems.  Cmake seems to be
working well at this point for us, but it took quite a bit to get there and
there are some pitfalls. I'm aware of some namespace issues in mlir, but
haven't gotten around to dealing with them.

Steve


On Thu, Jul 9, 2020, 3:47 AM Renato Golin <rengolin at gmail.com> wrote:
> On Wed, 8 Jul 2020 at 22:43, Chris Lattner <clattner at nondot.org>
wrote:
> > I think that flang beat us to the punch as the first external MLIR
user
> :-) but thank you for your support Renato!
>
> Ah, but Flang is in the monorepo and builds together with LLVM, while
> CIRCT (and my current project, Verona) "uses" MLIR/LLVM
externally (as
> a submodule).
>
> There are a number of build issues in both LLVM and MLIR that make it
> awkward for projects in that category to use the LLVM libraries and
> having a project in the llvm group will give us an "official"
reason
> to solve those problems more efficiently.
>
> I've been meaning to start a thread on that, but I need to collect all
> the build issues I had in an email so we can discuss them. Not for
> this thread, though. :)
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200709/29da0022/attachment.html>