<div dir="ltr">I filed <a href="https://llvm.org/bugs/show_bug.cgi?id=30736">https://llvm.org/bugs/show_bug.cgi?id=30736</a> to get that fixed.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 19, 2016 at 3:52 AM, Briltz, Denis <span dir="ltr"><<a href="mailto:Denis.Briltz@intel.com" target="_blank">Denis.Briltz@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="RU" link="blue" vlink="purple">
<div class="m_-1562626550108011407WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">“clang-x64-ninja-win7” was switched to VS2015.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">It is red now due to a few PDB tests and one sanitizer test.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Failing Tests (10):<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: DebugInfo/PDB/DIA/pdbdump-<wbr>flags.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: DebugInfo/PDB/DIA/pdbdump-<wbr>linenumbers.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: DebugInfo/PDB/DIA/pdbdump-<wbr>symbol-format.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-pdbdump/class-<wbr>layout.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-pdbdump/enum-<wbr>layout.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-pdbdump/load-<wbr>address.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-pdbdump/regex-<wbr>filter.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-symbolizer/pdb/<wbr>missing_pdb.test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> LLVM :: tools/llvm-symbolizer/pdb/pdb.<wbr>test<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> UBSan-Standalone-x86_64 :: TestCases/Integer/<wbr>suppressions.cpp<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><a href="http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/" target="_blank"><span lang="EN-US">http://lab.llvm.org:8011/<wbr>builders/clang-x64-ninja-win7/</span></a><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Denis<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="m_-1562626550108011407__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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> James Molloy [mailto:<a href="mailto:james@jamesmolloy.co.uk" target="_blank">james@jamesmolloy.co.<wbr>uk</a>]
<br>
<b>Sent:</b> Tuesday, October 18, 2016 10:13<br>
<b>To:</b> Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" target="_blank">mehdi.amini@apple.com</a>>; Reid Kleckner <<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>><br>
<b>Cc:</b> Aaron Ballman <<a href="mailto:aaron@aaronballman.com" target="_blank">aaron@aaronballman.com</a>>; <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>; Briltz, Denis <<a href="mailto:Denis.Briltz@intel.com" target="_blank">Denis.Briltz@intel.com</a>></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [llvm-dev] [cfe-dev] Revisiting our informal policy to support two versions of MSVC<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">No blocker from me! Thanks for your patience!<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, 18 Oct 2016 at 00:18, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" target="_blank">mehdi.amini@apple.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">If there is no blocker (James?), we should be able to move on, so I filed as a starter: <a href="https://reviews.llvm.org/D25710" target="_blank">https://reviews.llvm.<wbr>org/D25710</a><span class="m_-1562626550108011407gmailmsg"><span style="font-family:"Helvetica Neue"">:
[Doc] Drop MSVC2013 support</span></span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue";color:#000085">—</span><span style="font-family:"Helvetica Neue""> </span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue"">Mehdi</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Oct 12, 2016, at 4:03 PM, Reid Kleckner <<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">I migrated the sanitizer-windows builder to VS 2015, and it went green here:<u></u><u></u></p>
<div>
<p class="MsoNormal"><a href="http://lab.llvm.org:8011/builders/sanitizer-windows/builds/30342" target="_blank">http://lab.llvm.org:8011/<wbr>builders/sanitizer-windows/<wbr>builds/30342</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">That leaves two remaining builders using VS 2013:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://lab.llvm.org:8011/builders/clang-x86-win2008-selfhost/" target="_blank">http://lab.llvm.org:8011/<wbr>builders/clang-x86-win2008-<wbr>selfhost/</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/" target="_blank">http://lab.llvm.org:8011/<wbr>builders/clang-x64-ninja-win7/</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I'm going to be on vacation Fri-Tues this weekend, so I won't be around on Oct 15 to decomission any remaining VS 2013 bots.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I know someone at Intel is installing VS 2015 on clang-x64-ninja-win7, so I assume that's going to switch soon.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The clang-x86-win2008-selfhost builder is completely redundant with clang-x86-windows-<wbr>msvc2015. If someone can take responsibility for deleting the builder and slave from the buildbot config and pinging Galina for the master restart on
Monday, that would be great. I can delete the VM when I get back.<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Fri, Oct 7, 2016 at 12:14 PM, James Molloy <span class="m_-1562626550108011407gmailmsg">
<<a href="mailto:james@jamesmolloy.co.uk" target="_blank">james@jamesmolloy.co.uk</a>></span> 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">
<p class="MsoNormal">Hi Mehdi,<br>
<br>
Yes, all on track and thank you all for your kind patience!<br>
<br>
Cheers,<br>
<br>
James <u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">On Fri, 7 Oct 2016 at 20:13, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" target="_blank">mehdi.amini@apple.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Hi James,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Are you still on track for pulling the plug on MSVC 2013 at the end next week?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As another data point, other than new features or build failures, I just had to debug (with the help of Intel folks) a runtime failure because of a bug with zero-initialization in MSVC 2013 (see
<a href="https://connect.microsoft.com/VisualStudio/feedback/details/802160" target="_blank">
https://connect.microsoft.com/<wbr>VisualStudio/feedback/details/<wbr>802160</a> ).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">— <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Mehdi<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Sep 8, 2016, at 8:38 AM, James Molloy via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Thank you both, we appreciate it a lot!<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, 8 Sep 2016 at 16:37, Aaron Ballman via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<u></u><u></u></p>
</div>
<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">On Thu, Sep 8, 2016 at 11:24 AM, Reid Kleckner via llvm-dev<br>
<<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
> I can't say I'm excited to support MSVC 2013 for another month, but I'm more<br>
> concerned about the burden on other developers. People I talked to at the SF<br>
> bay area social last Thursday were really excited to drop 2013 support. I<br>
> guess I'll leave my buildbots on another month and see how it goes.<br>
<br>
I'm happy to help carry the burden as well, so if you run into<br>
anything you'd like to punt over to me, please let me know. I'm happy<br>
to handle it in addition to the things I usually pick up on.<br>
<br>
~Aaron<br>
<br>
><br>
> On Thu, Sep 8, 2016 at 7:03 AM, Robinson, Paul via llvm-dev<br>
> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> As this is an ABI-incompatible upgrade, and it's changing the informal<br>
>> policy on upgrades, could we please have some more grace time? Ideally<br>
>> another month, so the 15th October. If we haven't sorted it by then, it's<br>
>> our problem.<br>
>><br>
>><br>
>><br>
>> I had originally proposed 15 September mostly because nobody had proposed<br>
>> a specific date, and it has been kind of dragging on for a while. The<br>
>> primary cost of deferring to 15 October seems to be that the community (Hi<br>
>> Reid!) will have to keep fixing VS2013 related problems for another month,<br>
>> which isn't ideal but hopefully we can tolerate it.<br>
>><br>
>> (In fact at Sony we're only throwing the internal switch today, and we'll<br>
>> have to see what happens.)<br>
>><br>
>> --paulr<br>
>><br>
>><br>
>><br>
>> From: llvm-dev [mailto:<a href="mailto:llvm-dev-bounces@lists.llvm.org" target="_blank">llvm-dev-bounces@<wbr>lists.llvm.org</a>] On Behalf Of<br>
>> Craig, Ben via llvm-dev<br>
>> Sent: Wednesday, September 07, 2016 2:42 PM<br>
>> To: Zachary Turner; James Molloy; <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">
llvm-dev@lists.llvm.org</a><br>
>> Subject: Re: [llvm-dev] [cfe-dev] Revisiting our informal policy to<br>
>> support two versions of MSVC<br>
>><br>
>><br>
>><br>
>> I'll need to dig up the references for that... but I'm pretty sure the<br>
>> universal CRT that debuted in MSVC 2015 only covers the C parts, and not the<br>
>> C++ parts.<br>
>><br>
>><br>
>><br>
>> On 9/7/2016 4:28 PM, Zachary Turner wrote:<br>
>><br>
>> It's worth pointing out that from 2015 and on, they claim to support full<br>
>> forwards compatibility of the standard libraries, so this should (in theory)<br>
>> never be an issue again.<br>
>><br>
>><br>
>><br>
>> On Wed, Sep 7, 2016 at 1:12 PM James Molloy via llvm-dev<br>
>> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> As I understand it the specific issue we're seeing is related to what<br>
>> Martin described. But due to numerous bugs found when mixing objects<br>
>> compiled with different versions of MSVC in the past, we now are shy of<br>
>> doing it even if it seems to work superficially - that's no guarantee bugs<br>
>> won't be found down the line. We'd much prefer to stay within the realms of<br>
>> what Microsoft support.<br>
>><br>
>> Cheers,<br>
>><br>
>> James<br>
>><br>
>> On Wed, 7 Sep 2016 at 20:53, Craig, Ben via llvm-dev<br>
>> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> Note that this is intentional from the MSVC C++ library implementation<br>
>> side of things. For major versions, no attempt is made to preserve library<br>
>> ABI compatibility.<br>
>><br>
>> I am aware of a language ABI break in VC++ 2013.<br>
>> <a href="https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/" target="_blank">
https://randomascii.wordpress.<wbr>com/2013/12/01/vc-2013-class-<wbr>layout-change-and-wasted-<wbr>space/</a><br>
>><br>
>> I'm not currently aware of any on the VC++ 2015 side of things, but that<br>
>> doesn't mean much.<br>
>><br>
>><br>
>><br>
>> On 9/7/2016 2:34 PM, Martin O'Riordan via llvm-dev wrote:<br>
>><br>
>> Apart from the obvious licencing issues, each time I have moved from one<br>
>> version of VC++ to another, the big problem I have had is not specifically<br>
>> the ABI at the register passing, stack organisation level, but rather the<br>
>> implementation details of the Standard C++ libraries, and in particular the<br>
>> STL containers.<br>
>><br>
>> While the compiler team puts considerable effort into maintaining the ABI,<br>
>> the C++ library implementation usually changes a lot.<br>
>><br>
>> Since this is largely in the form of very complex headers defining<br>
>> templates which in turn cause other helper templates to be used, it is here<br>
>> that I find things go awry.<br>
>><br>
>> So for C++, a function like:<br>
>><br>
>> std::list<int> foo();<br>
>><br>
>><br>
>><br>
>> seems simple enough, but if the caller and the callee are compiled with<br>
>> different versions, it usually won't work because of some artefact of the<br>
>> STL implementation tuning that occurs between versions. In particular, this<br>
>> impacts things like using C++ interfaces across DLLs and in pre-compiled<br>
>> libraries.<br>
>><br>
>> I think that the ABI maintenance in this case tends to be for C and POD<br>
>> compatability, but not for the higher level C++ compatability which is<br>
>> unfortunate and restricts how we can use C++.<br>
>><br>
>> Is it possible that it is this aspect of the version change that is<br>
>> causing your ABI difficulties?<br>
>><br>
>> MartinO<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On 7 September 2016 at 20:18, Zachary Turner via llvm-dev<br>
>> <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> Can you elaborate on the abi incompatibility? I thought there were no<br>
>> breaks<br>
>><br>
>> On Wed, Sep 7, 2016 at 7:59 AM James Molloy via cfe-dev<br>
>> <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>><br>
>><br>
>> Firstly sorry I'm a bit late responding on this one. Internally to ARM we<br>
>> build LLVM for Windows. Our current build cluster has only VS2013 installed<br>
>> and as a result of this thread we've been working on getting VS2015<br>
>> installed. This involves a certain amount of IT-wrangling as the cluster we<br>
>> use is company-wide. There have been some hiccups regarding licensing of<br>
>> MSVC professional (we can't use the community edition for the same reasons<br>
>> mentioned by Paul previously) but we hoped to be ready in time for the 15th<br>
>> September switchover date.<br>
>><br>
>><br>
>><br>
>> It's recently been realised that VS2013 and VS2015 are not ABI compatible<br>
>> (something that really surprised me), and this means we have to synchronize<br>
>> moving LLVM's build to VS2015 as well as upgrading a third party library<br>
>> that we receive from the vendor in compiled library form. This is not<br>
>> something we're capable of doing by September 15th.<br>
>><br>
>><br>
>><br>
>> We try really hard at ARM to hide our internal processes because we<br>
>> believe that they're on the whole irrelevant to the community, however in<br>
>> this case we'd be really stuck, unable to get production builds.<br>
>><br>
>><br>
>><br>
>> As this is an ABI-incompatible upgrade, and it's changing the informal<br>
>> policy on upgrades, could we please have some more grace time? Ideally<br>
>> another month, so the 15th October. If we haven't sorted it by then, it's<br>
>> our problem.<br>
>><br>
>><br>
>><br>
>> Cheers,<br>
>><br>
>><br>
>><br>
>> James<br>
>><br>
>><br>
>><br>
>> On Thu, 1 Sep 2016 at 21:06 Mehdi Amini via cfe-dev<br>
>> <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> On Sep 1, 2016, at 1:05 PM, Reid Kleckner <<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Thu, Sep 1, 2016 at 12:53 PM, Mehdi Amini via cfe-dev<br>
>> <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
>><br>
>> Isn’t a big (the most) reason for supporting “old” toolchains to allow<br>
>> downstream users to upgrade with some flexibility?<br>
>><br>
>> If I have a large codebase that is using LLVM (let say a few custom<br>
>> backends), and is validated with “MSVC 2013”, I can upgrade to “2015” but I<br>
>> will need some qualification/validation: this is not free and take some<br>
>> time. If you drop aggressively supports for “old” toolchain it means that<br>
>> I’m either stuck with an “old” LLVM or that I have to update earlier than<br>
>> expected.<br>
>><br>
>><br>
>><br>
>> Isn’t this usually balanced in upstream LLVM to upgrade when there is a<br>
>> real *benefit* to it?<br>
>><br>
>> I’m mentioning it because it seems to conflict with the "always upgrade to<br>
>> the newest one unless there are serious issues with it” you mentioned above.<br>
>><br>
>><br>
>><br>
>> I agree, we should raise the minimum VS version requirement when the<br>
>> benefits to the LLVM community outweigh the costs of switching for major<br>
>> LLVM contributors and users. I think we'll always make that decision in the<br>
>> same way: by raising it on the mailing lists and discussing the pros and<br>
>> cons. That's basically what David said when he kicked this whole discussion<br>
>> off, anyway:<br>
>><br>
>><br>
>><br>
>> """But if we find ourselves in a situation where asking folks to upgrade<br>
>> to a compiler which has been widely deployed soothes development for the<br>
>> greater LLVM community, we should consider dropping support for the older<br>
>> versions of that compiler."""<br>
>><br>
>><br>
>><br>
>> I think everything is working as intended here.<br>
>><br>
>><br>
>><br>
>> Right, to be clear there is no misunderstanding: I was absolutely not<br>
>> suggesting the opposite when answering Zach..<br>
>><br>
>><br>
>><br>
>> —<br>
>><br>
>> Mehdi<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> We raised the VS 2013 upgrade issue, discussed it, determined that it was<br>
>> holding us back, and now we're doing the upgrade. If VS "15" brings major<br>
>> language compatibility improvements, I imagine we'll be having this same<br>
>> discussion again next year. If it doesn't, and supporting 2015 and "15" at<br>
>> the same time has the same cost, then we won't bother raising the floor for<br>
>> a while.<br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> cfe-dev mailing list<br>
>> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> cfe-dev mailing list<br>
>> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>><br>
>> LLVM Developers mailing list<br>
>><br>
>> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
>><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Employee of Qualcomm Innovation Center, Inc.<br>
>><br>
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux<br>
>> Foundation Collaborative Project<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Employee of Qualcomm Innovation Center, Inc.<br>
>><br>
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux<br>
>> Foundation Collaborative Project<br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">
http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><br>
><br>
______________________________<wbr>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal">______________________________<wbr>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/llvm-dev</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>