llvm dev - Dec 2017 - Updating LLVM/Clang support for VS for VS2017

CCing Zach, who did a lot of the VS 2017 support work (AFAIK), and Reid,
who's the general Microsoft support overlord.

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.

Which compiler options/switches specifically are missing? Filing bugs for those
at https://bugs.llvm.org/ 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.

From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Osman
Zakir via llvm-dev <llvm-dev at lists.llvm.org>
Reply-To: Osman Zakir <osmanzakir90 at hotmail.com>
Date: Thursday, December 7, 2017 at 7:09 AM
To: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org>
Subject: [llvm-dev] Updating LLVM/Clang support for VS for VS2017


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).



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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20171207/55b3fede/attachment.html>

I'm curious to know what's missing as well.  The only thing I can think
of
off the top of my head is that we haven't updated the VS integration to add
clang-cl as a toolchain to the IDE.  But, I don't know that we even did
that for 2015 either, that has been stale for quite a while.

As far as C++ language and ABI compatibility, I'm not aware of anything
that's missing.

On Thu, Dec 7, 2017 at 12:12 PM Shoaib Meenai <smeenai at fb.com> wrote:
> CCing Zach, who did a lot of the VS 2017 support work (AFAIK), and Reid,
> who's the general Microsoft support overlord.
>
>
>
> 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.
>
>
>
> Which compiler options/switches specifically are missing? Filing bugs for
> those at https://bugs.llvm.org/ 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.
>
>
>
> *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of
Osman
> Zakir via llvm-dev <llvm-dev at lists.llvm.org>
> *Reply-To: *Osman Zakir <osmanzakir90 at hotmail.com>
> *Date: *Thursday, December 7, 2017 at 7:09 AM
> *To: *"llvm-dev at lists.llvm.org" <llvm-dev at
lists.llvm.org>
> *Subject: *[llvm-dev] Updating LLVM/Clang support for VS for VS2017
>
>
>
> 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).
>
>
>
> 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?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20171207/30795762/attachment.html>

I also imagine Osman refers to the Visual Studio IDE integration, not
so much the compiler itself.

The last time we updated that was for the VS "14" CTP.

This stuff lives in LLVM's tools/msbuild/ directory, and contributions
would be very welcome.

On Thu, Dec 7, 2017 at 12:18 PM, Zachary Turner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I'm curious to know what's missing as well.  The only thing I can
think of
> off the top of my head is that we haven't updated the VS integration to
add
> clang-cl as a toolchain to the IDE.  But, I don't know that we even did
that
> for 2015 either, that has been stale for quite a while.
>
> As far as C++ language and ABI compatibility, I'm not aware of anything
> that's missing.
>
> On Thu, Dec 7, 2017 at 12:12 PM Shoaib Meenai <smeenai at fb.com>
wrote:
>>
>> CCing Zach, who did a lot of the VS 2017 support work (AFAIK), and
Reid,
>> who's the general Microsoft support overlord.
>>
>>
>>
>> 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.
>>
>>
>>
>> Which compiler options/switches specifically are missing? Filing bugs
for
>> those at https://bugs.llvm.org/ 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.
>>
>>
>>
>> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of
Osman Zakir
>> via llvm-dev <llvm-dev at lists.llvm.org>
>> Reply-To: Osman Zakir <osmanzakir90 at hotmail.com>
>> Date: Thursday, December 7, 2017 at 7:09 AM
>> To: "llvm-dev at lists.llvm.org" <llvm-dev at
lists.llvm.org>
>> Subject: [llvm-dev] Updating LLVM/Clang support for VS for VS2017
>>
>>
>>
>> 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).
>>
>>
>>
>> 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?
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>