<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:143206639;
mso-list-type:hybrid;
mso-list-template-ids:1237902826 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1914703328;
mso-list-type:hybrid;
mso-list-template-ids:-1798517920 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">FWIW, I think this could be a very positive step for LLVM and the community. Most of the discussion has been about the details (documentation, in-tree vs. out-of-tree, etc.), but I think there are key bigger picture reasons:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Obviously, ML languages and frameworks are becoming widespread and a number of teams are investing resources into compilers for them. Having a successful LLVM project that provides
good infrastructure for these compilers would be valuable. While the TensorFlow compiler may (or may not) remain a Google project, having a core infrastructure available to the wider community should be super valuable.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Related point to #1: ML models and even core data types and approaches are evolving rapidly, so there is a lot of research happening on the underlying system infrastructure, from hardware
to compilers to languages. If MLIR can become the infrastructure of choice for these research projects (like LLVM did for the scalar and vector compiler world 15 years ago), that would be a big win.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">As Hal said, the LLVM infrastructure has not provided explicit support for high-level analyses and transformations, e.g., loop restructuring, multidimensional arrays, etc. Having
a good infrastructure to support these will make a number of languages and hardware targets easier to implement / target.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">--Vikram Adve</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">+ Donald B. Gillies Professor of Computer Science, University of Illinois at Urbana-Champaign<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">+ Scheduling: Kimberly Baker – </span><u><span style="color:#954F72"><a href="mailto:kabaker@illinois.edu">kabaker@illinois.edu</a></span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">+ Skype: vikramsadve || Zoom: </span><span style="font-size:10.0pt;font-family:Helvetica;color:#232333;background:white"><a href="https://illinois.zoom.us/j/2173900467">https://illinois.zoom.us/j/2173900467</a></span><span style="color:black">
<br>
+ Home page: <a href="http://vikram.cs.illinois.edu/"><span style="color:#954F72">http://vikram.cs.illinois.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal">+ Center for Digital Agriculture: <a href="https://digitalag.illinois.edu/">
https://digitalag.illinois.edu</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">llvm-dev <llvm-dev-bounces@lists.llvm.org> on behalf of via llvm-dev <llvm-dev@lists.llvm.org><br>
<b>Reply-To: </b>"llvm-dev@lists.llvm.org" <llvm-dev@lists.llvm.org>, "llvm-dev-request@lists.llvm.org" <llvm-dev-request@lists.llvm.org><br>
<b>Date: </b>Monday, September 9, 2019 at 1:58 PM<br>
<b>To: </b>"llvm-dev@lists.llvm.org" <llvm-dev@lists.llvm.org><br>
<b>Subject: </b>llvm-dev Digest, Vol 183, Issue 22<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Date: Mon, 9 Sep 2019 17:46:34 +0000<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">From: "Finkel, Hal J. via llvm-dev" <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">To: Chris Lattner <<a href="mailto:clattner@google.com">clattner@google.com</a>>, llvm-dev<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span"><span style="font-family:"-webkit-standard",serif;color:black">
</span></span><span style="font-family:"-webkit-standard",serif;color:black"><<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Cc: Reid Tatge <<a href="mailto:tatge@google.com">tatge@google.com</a>>, Mehdi Amini <<a href="mailto:aminim@google.com">aminim@google.com</a>>,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span"><span style="font-family:"-webkit-standard",serif;color:black">
</span></span><span style="font-family:"-webkit-standard",serif;color:black">Tatiana Shpeisman <<a href="mailto:shpeisman@google.com">shpeisman@google.com</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Subject: Re: [llvm-dev] Google’s<span class="apple-converted-space"> </span>TensorFlow<span class="apple-converted-space"> </span>team would like to<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span class="apple-tab-span"><span style="font-family:"-webkit-standard",serif;color:black">
</span></span><span style="font-family:"-webkit-standard",serif;color:black">contribute MLIR to the LLVM Foundation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Message-ID: <<a href="mailto:7611fea3-ba64-f587-ca64-fbdf49055a04@anl.gov">7611fea3-ba64-f587-ca64-fbdf49055a04@anl.gov</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Content-Type: text/plain; charset="utf-8"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Hi, Chris, et al.,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">I support adding MLIR as an LLVM subproject. Here are my thoughts:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">1. MLIR uses LLVM. LLVM is one of the MLIR dialects, MLIR is compiler infrastructure, and it fits as a natural part of our ecosystem.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">2. As a community, we have a lot of different LLVM frontends, many of which have their own IRs on which higher-level transformations are performed.
We don't currently offer much, in terms of infrastructure, to support the development of these pre-LLVM transformations. MLIR provides a base on which many of these kinds of implementations can be constructed, and I believe that will add value to the overall
ecosystem.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">3. As a specific example of the above, the current development of the new Flang compiler depends on MLIR. Flang is becoming a subproject of LLVM and
MLIR should be part of LLVM.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">4. The MLIR project has developed capabilities, such as for the analysis of multidimensional loops, that can be moved into LLVM and used by both LLVM-
and MLIR-level transformations. As we work to improve LLVM's capabilities in loop optimizations, leveraging continuing work to improve MLIR's loop capabilities in LLVM as well will benefit many of us.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">5. As a community, we have been moving toward increasing support for heterogeneous computing and accelerators (and given industry trends, I expect this
to continue), and MLIR can facilitate that support in many cases (although I expect we'll see further enhancements in the core LLVM libraries as well).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">That all having been said, I think that it's going to be very important to develop some documentation on how a frontend author looking to use LLVM backend
technology, and a developer looking to implement different kinds of functionality, might reasonably choose whether to target or enhance MLIR components, LLVM components, or both. I expect that this kind of advice will evolve over time, but I'm sure we'll need
it sooner rather than later.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Thanks again,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Hal<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">On 9/9/19 10:30 AM, Chris Lattner via llvm-dev wrote:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Hi all,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">The<span class="apple-converted-space"> </span>TensorFlow<span class="apple-converted-space"> </span>team at Google has been leading the charge to build
a new set of compiler infrastructure, known as the MLIR project<<a href="https://github.com/tensorflow/mlir">https://github.com/tensorflow/mlir</a>>. 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<<a href="https://llvm.org/devmtg/2019-10/talk-abstracts.html#tech19">https://llvm.org/devmtg/2019-10/talk-abstracts.html#tech19</a>>. 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<<a href="http://llvm.org/devmtg/2019-04/">http://llvm.org/devmtg/2019-04/</a>>.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">MLIR is already open source on GitHub<<a href="https://medium.com/tensorflow/mlir-a-new-intermediate-representation-and-compiler-framework-beba999ed18d">https://medium.com/tensorflow/mlir-a-new-intermediate-representation-and-compiler-framework-beba999ed18d</a>>,
and includes a significant amount of code in two repositories. “MLIR Core” is located in github/tensorflow/mlir<<a href="https://github.com/tensorflow/mlir">https://github.com/tensorflow/mlir</a>>, including an application independent IR, the code generation
infrastructure, common graph transformation infrastructure, declarative operation definition and rewrite infrastructure, polyhedral transformations etc. The primary<span class="apple-converted-space"> </span>TensorFlow<span class="apple-converted-space"> </span>repository
at github/tensorflow/tensorflow<<a href="https://github.com/tensorflow/tensorflow/">https://github.com/tensorflow/tensorflow/</a>> contains<span class="apple-converted-space"> </span>TensorFlow-specific functionality built using MLIR Core infrastructure.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">In discussions with a large number of industry partners<<a href="https://blog.google/technology/ai/mlir-accelerating-ai-open-source-infrastructure/">https://blog.google/technology/ai/mlir-accelerating-ai-open-source-infrastructure/</a>>,
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<<a href="http://llvm.org/docs/DeveloperPolicy.html">http://llvm.org/docs/DeveloperPolicy.html</a>>, 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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">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!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">-Chris<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">_______________________________________________<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">LLVM Developers mailing list<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a><<a href="mailto:llvm-dev@lists.llvm.org">mailto:llvm-dev@lists.llvm.org</a>><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">--<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Hal Finkel<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Lead, Compiler Technology and Programming Languages<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Leadership Computing Facility<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">Argonne National Laboratory<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">-------------- next part --------------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">An HTML attachment was scrubbed...<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"-webkit-standard",serif;color:black">URL: <<a href="http://lists.llvm.org/pipermail/llvm-dev/attachments/20190909/cfd721f3/attachment-0001.html">http://lists.llvm.org/pipermail/llvm-dev/attachments/20190909/cfd721f3/attachment-0001.html</a>><o:p></o:p></span></p>
</div>
</div>
</body>
</html>