<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="Title" content="">
<meta name="Keywords" content="">
<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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">CCing Zach, who did a lot of the VS 2017 support work (AFAIK), and Reid, who's the general Microsoft support overlord.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">By full support for VS 2017, do you mean within the IDE itself? I haven't ever used clang from within the VS IDE, so I can't speak to that. All non-IDE stuff should work though, as far as I know.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Which compiler options/switches specifically are missing? Filing bugs for those at
<a href="https://bugs.llvm.org/">https://bugs.llvm.org/</a> is probably the way to go. clang-cl does support the /std switch, at least. 5.0 supports /std:c++14 and /std:c++latest, and trunk adds support for /std:c++17.<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"><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 Osman Zakir via llvm-dev <llvm-dev@lists.llvm.org><br>
<b>Reply-To: </b>Osman Zakir <osmanzakir90@hotmail.com><br>
<b>Date: </b>Thursday, December 7, 2017 at 7:09 AM<br>
<b>To: </b>"llvm-dev@lists.llvm.org" <llvm-dev@lists.llvm.org><br>
<b>Subject: </b>[llvm-dev] Updating LLVM/Clang support for VS for VS2017<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="divtagdefaultwrapper">
<p><span style="font-size:12.0pt;color:black">The Clang compiler doesn't have full support for VS2017 yet, right? I talked to someone on MSDN forums and they said that LLVM/Clang developers still haven't updated Clang's VS support to include VS2017. The patch
for finding VS2017 installation instances and toolchains was updated, and I'm thankful for that. But I'd like for the support for VS2017 to also be updated/included (whichever). <o:p></o:p></span></p>
<p><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p><span style="font-size:12.0pt;color:black">If I want to ask for the compiler options/switches to be the same as for the Clang compiler as well, and to also have access to the ISO C++ standard version compiler switches, where should I ask for that? MSDN,
or here? Or maybe both? <o:p></o:p></span></p>
</div>
</div>
</body>
</html>