<p dir="ltr">We support the last two major releases of msvc unless there is a really compelling case to drop support early. So whenever the successor to msvc 2015 comes out is when we plan to drop support for msvc 2013.</p>
<p dir="ltr">~Aaron</p>
<div class="gmail_quote">On Mar 16, 2016 4:17 PM, "Michael Spertus via cfe-dev" <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not unlike gdb visualizers, Visual Studio visualizers require some setup: You have to put clang.natvis and llvm.natvis in Documents\Visual Studio 20xx\Visualizers. However, VS2015 added support for visualizers in a project. Once we stop supporting VS2013, we will be able to automagically eliminate the manual setup. Is there a timeline for dropping VS2013 support?<br>
<br>
Mike<br>
<br>
-----Original Message-----<br>
From: cfe-dev [mailto:<a href="mailto:cfe-dev-bounces@lists.llvm.org">cfe-dev-bounces@lists.llvm.org</a>] On Behalf Of Jonathan Roelofs via cfe-dev<br>
Sent: Wednesday, March 16, 2016 12:21 PM<br>
To: C Bergström <<a href="mailto:cbergstrom@pathscale.com">cbergstrom@pathscale.com</a>>; David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>><br>
Cc: <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
Subject: Re: [cfe-dev] Visual Studio visualizer improvements for Clang<br>
<br>
<br>
<br>
On 3/16/16 11:16 AM, C Bergström via cfe-dev wrote:<br>
> Cool results, but XML - ewwie..<br>
> ---------<br>
> I digress - What's lldb do in this case?<br>
<br>
<a href="https://github.com/llvm-mirror/llvm/blob/master/utils/lldbDataFormatters.py" rel="noreferrer" target="_blank">https://github.com/llvm-mirror/llvm/blob/master/utils/lldbDataFormatters.py</a><br>
<br>
><br>
> On Thu, Mar 17, 2016 at 1:14 AM, David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a><br>
> <mailto:<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>>> wrote:<br>
><br>
> FWIW, GDB has a visualizer system in python - I wrote up some<br>
> visualizers for SmallVector, etc, but I couldn't find a way to plug<br>
> them in for free into GDB (everything required some reconfiguration<br>
> of GDB to point to a script directory or the like). I might check<br>
> them in anyway with a README telling people how to set them up if<br>
> they want to.<br>
><br>
> On Wed, Mar 16, 2016 at 9:59 AM, C Bergström <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
> <mailto:<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>>> wrote:<br>
><br>
> Looks cool! I'm not a VS guy - how did you achieve this? Was<br>
> there some source changes in clang or is this a plugin that<br>
> leverages clang for VS?<br>
><br>
> Thanks<br>
><br>
> On Wed, Mar 16, 2016 at 11:04 PM, Michael Spertus via cfe-dev<br>
> <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a> <mailto:<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>>> wrote:<br>
><br>
> Chandler suggested that I socialize the improvements that I<br>
> have been making to Clang data structure visualizations in<br>
> Visual Studio. For example, these changes replace the<br>
> traditional incomprehensible Locals/Watch display of a<br>
> TemplateArgumentLoc____<br>
><br>
> __ __<br>
><br>
> ____<br>
><br>
> __ __<br>
><br>
> Now it clearly displays that it is a Type Template Parameter<br>
> where T has been replaced by struct A.____<br>
><br>
> ____<br>
><br>
> __ __<br>
><br>
> I only have a small portion of the Clang data types done so<br>
> far, but it is already really helping me keep track of what<br>
> is going on while debugging Clang (It’s also been an<br>
> excellent way for me to learn Clang data structures J ). I<br>
> will be continuing to add further visualizations over the<br>
> next few weeks and ongoing. ____<br>
><br>
> __ __<br>
><br>
> I hope these prove helpful to the community,____<br>
><br>
> __ __<br>
><br>
> Mike____<br>
><br>
><br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a> <mailto:<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a> <mailto:<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
><br>
<br>
--<br>
Jon Roelofs<br>
<a href="mailto:jonathan@codesourcery.com">jonathan@codesourcery.com</a><br>
CodeSourcery / Mentor Embedded<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div>