[llvm-dev] Google’s TensorFlow team would like to contribute MLIR to the LLVM Foundation

[Tatiana Shpeisman via llvm-dev]

Fantastic news, indeed! Thank you for accepting MLIR as an LLVM project!

Tatiana

On Mon, Oct 7, 2019 at 9:16 PM Reid Tatge <tatge at google.com> wrote:

> This is great news!   Congratulations everyone!
>
> On Mon, Oct 7, 2019 at 9:14 PM Tatiana Shpeisman <shpeisman at google.com>
> wrote:
>
>> Congratulations, everybody!
>>
>> On Mon, Oct 7, 2019 at 3:55 PM Chris Lattner <clattner at google.com> wrote:
>>
>>> Fantastic, thank you!
>>>
>>> -Chris
>>>
>>> On Oct 7, 2019, at 1:17 AM, Tanya Lattner via llvm-dev <
>>> llvm-dev at lists.llvm.org> wrote:
>>>
>>> On behalf of the LLVM Foundation board of directors, we accept MLIR as a
>>> project into LLVM. This is based upon the responses that the community is
>>> supportive and is in favor of this. We will provide services and support on
>>> our side.
>>>
>>> Welcome MLIR!
>>>
>>> Thanks,
>>> Tanya Lattner
>>> President, LLVM Foundation
>>>
>>> On Sep 9, 2019, at 8:30 AM, Chris Lattner via llvm-dev <
>>> llvm-dev at lists.llvm.org> wrote:
>>>
>>> Hi all,
>>>
>>> The TensorFlow team at Google has been leading the charge to build a new
>>> set of compiler infrastructure, known as the MLIR project
>>> <https://github.com/tensorflow/mlir>.  The initial focus has been on
>>> machine learning infrastructure, high performance accelerators,
>>> heterogeneous compute, and HPC-style computations.  That said, the
>>> implementation and design of this infrastructure is state of the art, is
>>> not specific to these applications, and is already being adopted (e.g.) by the
>>> Flang compiler
>>> <https://llvm.org/devmtg/2019-10/talk-abstracts.html#tech19>.  If you
>>> are interested in learning more about MLIR and the technical design, I’d
>>> encourage you to look at the MLIR Keynote and Tutorial at the last LLVM
>>> Developer Meeting <http://llvm.org/devmtg/2019-04/>.
>>>
>>> MLIR is already open source on GitHub
>>> <https://medium.com/tensorflow/mlir-a-new-intermediate-representation-and-compiler-framework-beba999ed18d>,
>>> and includes a significant amount of code in two repositories.  “MLIR Core”
>>> is located in github/tensorflow/mlir
>>> <https://github.com/tensorflow/mlir>, including an application
>>> independent IR, the code generation infrastructure, common graph
>>> transformation infrastructure, declarative operation definition and rewrite
>>> infrastructure, polyhedral transformations etc.  The primary TensorFlow
>>> repository at github/tensorflow/tensorflow
>>> <https://github.com/tensorflow/tensorflow/> contains
>>> TensorFlow-specific functionality built using MLIR Core infrastructure.
>>>
>>> In discussions with a large number of industry partners
>>> <https://blog.google/technology/ai/mlir-accelerating-ai-open-source-infrastructure/>,
>>> we’ve achieved consensus that it would be best to build a shared ML
>>> compiler infrastructure under a common umbrella with well known neutral
>>> governance.  As such, we’d like to propose that MLIR Core join the
>>> non-profit LLVM Foundation as a new subproject! We plan to follow the LLVM
>>> Developer Policy <http://llvm.org/docs/DeveloperPolicy.html>, and have
>>> been following an LLVM-style development process from the beginning -
>>> including all relevant coding and testing styles, and we build on core LLVM
>>> infrastructure pervasively.
>>>
>>> We think that MLIR is a nice complement to existing LLVM functionality,
>>> providing common infrastructure for higher level optimization and
>>> transformation problems, and dovetails naturally with LLVM IR optimizations
>>> and code generation.  Please let us know if you have any thoughts,
>>> questions, or concerns!
>>>
>>> -Chris
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191007/f8d493bf/attachment.html>