{"id":9135,"date":"2016-06-03T10:10:39","date_gmt":"2016-06-03T17:10:39","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/?p=9135"},"modified":"2019-07-31T09:25:40","modified_gmt":"2019-07-31T09:25:40","slug":"clang-3-8-in-the-may-release-of-clang-with-microsoft-codegen","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/clang-3-8-in-the-may-release-of-clang-with-microsoft-codegen\/","title":{"rendered":"Clang 3.8 in the May release of Clang with Microsoft CodeGen"},"content":{"rendered":"

This blog post written by Dave Bartolomeo, Yuriy Solodkyy, and Andrew Pardoe<\/em><\/p>\n

We have just released\u00a0our fifth out-of-band update of Clang\/C2 toolset. As always, this release has been driven by your feedback. While we’ve heard a lot of feature requests the one’s we’ve heard most frequently are that you want Clang 3.8 and you want x64-hosted compilers. We’re happy to say that we’re shipping both Clang 3.8 and x64-hosted compilers in the May 2016 release.<\/p>\n

Clang 3.8\u00a0is\u00a0the latest official release of Clang. Moving to Clang 3.8 brings in roughly six months of features and bug fixes from the Clang community. We’ve also added x64-hosted versions of the Clang\/C2 compiler toolset. This enables you to compile\u00a0projects that require more memory than x86 can provide. The x64 Clang\/C2 toolset\u00a0also gives more compatibility with projects that\u00a0compile with the\u00a0x64-hosted MSVC toolset.<\/p>\n

This post focuses on changes since the last release. For a more\u00a0detailed discussion of the Clang\/C2 toolset please read “Clang with Microsoft CodeGen (March 2016) released<\/a>”\u00a0and any of the posts tagged with the keyword \u201cclang\u201d<\/a>.<\/p>\n

This release revises the version of C2.dll to 19.0.25317.0.<\/p>\n

How to enable the x64-hosted Clang\/C2 compiler<\/h2>\n

To change your Visual Studio project to use the x64-hosted tools, you need to set the ‘PreferredToolArchitecture’ MSBuild property to ‘x64’. This will set your project to use the x64-hosted version of the entire C++ toolset, whether you’re using Clang\/C2 or the MSVC compiler.<\/p>\n

There is currently no method to force the 64-bit tools in Visual Studio so you have to edit your .vcxproj file. Insert the following after the <Import...Microsoft.Cpp.Defaults<\/code> line:<\/p>\n

  <Import Project=\"$(VCTargetsPath)\\Microsoft.Cpp.Default.props\" \/>\n  <PropertyGroup>\n    <PreferredToolArchitecture>x64<\/PreferredToolArchitecture>\n  <\/PropertyGroup>\n<\/pre>\n
The edit needs to be made after importing the properties file as it may get changed in one of the files it imports based on your host architecture. If you use -v (Enable Verbose mode in the IDE) in your compiler options, you\u2019ll see the full path to clang.exe in the output–make sure it includes the amd64 subdirectory.<\/p>\n
There are more details about this technique in this Stack Overflow post: How to make Visual Studio use the native amd64 toolchain<\/a>.<\/p>\n
If you use a build system other than MSBuild, you’ll need to get your build system to pick up clang.exe from ‘C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\Clang 3.7\\bin\\amd64<\/b>\\{x86|amd64|arm}\\clang.exe’ instead of ‘C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\Clang 3.7\\bin\\x86<\/strong>\\{x86|amd64|arm}\\clang.exe’<\/p>\n
How to get this update<\/h2>\n
Through VS Notifications<\/h4>\n
If you already have the March 2016 update of Clang\/C2 installed you should receive a notification in the VS Notifications pane that this update is available. Click on that notification to begin the installation process.<\/p>\n
\"notification2\"<\/a><\/p>\n
 <\/p>\n
Use the VS installer<\/h4>\n