<html 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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">As we <a href="https://lists.llvm.org/pipermail/llvm-dev/2020-February/139574.html">
announced several months ago</a>, we’ve been working on a new LLD Mach-O port, modeled after the design used in the COFF and ELF ports. We’ve made significant progress; we’re able to self-host and pass our test suite on x86-64, and we’re on track to do the
same on arm64. We’re also able to successfully link and run various internal Facebook binaries, and others have even been able to
<a href="https://bugs.llvm.org/show_bug.cgi?id=48657">link Chromium successfully</a> (the resulting binary is crashy, which is being investigated).<br>
<br>
At this point, we believe we’re mature enough that it makes sense to switch the ld64.lld symlink (which is what Clang invokes by default when told to use LLD for a Darwin platform) to use the new Mach-O port instead of the old one. We would like to make this
change before the LLVM 12 branch cut, and also note it prominently in the release notes and invite people to try the new port and file bugs (and of course contribute to it as well). Our port still has a few known limitations and missing features (which we’ll
also note in the release notes), but it is complete enough to be useful at this point, and we’d like it to be easily usable in the LLVM 12 release. Let us know if you have any concerns with this plan.<o:p></o:p></span></p>
</div>
</body>
</html>