<div dir="ltr">But even if you use link.exe for linking, you'd still need to emit debug info into object files first, at least in the AOT case. Unless, of course, you are not planning to use LLVM backend on Windows at all.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 16, 2015 at 10:04 AM, Andy Ayers <span dir="ltr"><<a href="mailto:andya@microsoft.com" target="_blank">andya@microsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The LLILC project does not require direct interaction with the PDB, so it’s not part of our plans.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The JIT uses a special reporting format to communicate debug info (frame info and machine->IL mappings) back to the CoreCLR EE. The debugger joins this with the
frontend-produced debug information (IL->source and logical frame offset->local, which is in a PDB) to complete the picture.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Something similar will likely happen in the AOT case, where the “code generator” just produces a subset of the data, and some other entity (the linker, say) incorporates
that into the PDB.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><a name="14cc32ffd147e768__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></a></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:llvmdev-bounces@cs.uiuc.edu" target="_blank">llvmdev-bounces@cs.uiuc.edu</a> [mailto:<a href="mailto:llvmdev-bounces@cs.uiuc.edu" target="_blank">llvmdev-bounces@cs.uiuc.edu</a>]
<b>On Behalf Of </b>Vadim Chugunov<br>
<b>Sent:</b> Wednesday, April 15, 2015 11:49 AM<br>
<b>To:</b> Russell Hadley<br>
<b>Cc:</b> <a href="mailto:llvmdev@cs.uiuc.edu" target="_blank">llvmdev@cs.uiuc.edu</a></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [LLVMdev] MS fork<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Just curious, are you planning to add support for debug info emission in mspdb format?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, Apr 15, 2015 at 7:01 AM, Russell Hadley <<a href="mailto:rhadley@microsoft.com" target="_blank">rhadley@microsoft.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Chandler has it right. Our intent is to upstream everything. The MS fork will be used as a staging area for LLVM changes as we work to get them upstreamed. Tactically
we're merging the MS fork everyday with mainline to try and stay close. <u></u><u></u></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><u></u> <u></u></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">We're still ramping up right now, and trying to figure out how best to work day to day, but our over arching goal is to enable (mainline) LLVM to be a great code generator
for C#.<u></u><u></u></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"><u></u> <u></u></span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">-R<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:"Calibri",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<div class="MsoNormal" style="text-align:center;background:white" align="center">
<span style="font-family:"Calibri",sans-serif;color:#212121">
<hr align="center" size="3" width="98%">
</span></div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
<a href="mailto:llvmdev-bounces@cs.uiuc.edu" target="_blank">llvmdev-bounces@cs.uiuc.edu</a> <<a href="mailto:llvmdev-bounces@cs.uiuc.edu" target="_blank">llvmdev-bounces@cs.uiuc.edu</a>> on behalf of Chandler Carruth <<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>><br>
<b>Sent:</b> Wednesday, April 15, 2015 3:14 AM<br>
<b>To:</b> C Bergström; <a href="mailto:llvmdev@cs.uiuc.edu" target="_blank">llvmdev@cs.uiuc.edu</a><br>
<b>Subject:</b> Re: [LLVMdev] MS fork</span><span style="font-family:"Calibri",sans-serif;color:#212121">
<u></u><u></u></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:#212121"> <u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:#212121">They presented on LLILC at EuroLLVM, and indicated they were just starting up but were definitely planning to contribute everything back to upstream.
Personally, I'm pretty happy to see them talking actively to the community, participating effectively in EuroLLVM and some of the stuff they talked about there was really exciting.<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:#212121"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:#212121">On Tue, Apr 14, 2015 at 10:16 PM C Bergström <<a href="mailto:cbergstrom@pathscale.com" target="_blank">cbergstrom@pathscale.com</a>> wrote:<u></u><u></u></span></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:#212121">Dear MS,<br>
<br>
Will you be cleaning up and encouraging people to get the work on<br>
github upstream?<br>
<a href="https://github.com/Microsoft/llvm/commits/MS" target="_blank">https://github.com/Microsoft/llvm/commits/MS</a><br>
<br>
Thanks<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><u></u><u></u></span></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>