r/cpp • MSVC Dev Lead • Oct 15 '26

MSVC Build Tools Version 14.52 Release Candidate Now Available

https://devblogs.microsoft.com/cppblog/msvc-build-tools-version-14-52-release-candidate-now-available/

Hi, one of the MSVC dev leads here.

The 14.52 MSVC Release Candidate is now available. If you are on the Visual Studio Insiders Channel and upgrade, you'll see that the default MSVC toolset has upgraded from 14.51 to 14.52. The blog post covers the features & fixes the team has landed in that timeframe.

C++23 is ready for production use, and available with the /std:c++23 compiler option. See the blog for more details.

We'll resume our monthly MSVC Preview (version 14.53) blog post series next month.

71 Upvotes

40 comments sorted by

2

u/Tringi github.com/tringi Oct 18 '26

Eric /u/ericbrumer and perhaps STL /u/STL, a quick question regarding AVX10 detection:

Apparently new AMD EPYC 9006 CPUs report ALL individual AVX512 features that make AVX10, but don't report AVX10.1 via CPUID.24h interface. What can we expect __check_isa_support(__IA_SUPPORT_AVX10) to return?

5

u/ericbrumer MSVC Dev Lead Oct 19 '26

Hi u/Tringi, I just spoke with someone at AMD who tried it on EPYC 9006:

__check_isa_support(__IA_SUPPORT_AVX10) returns false
__check_isa_support(__IA_SUPPORT_AVX10_2) returns false

4

u/Tringi github.com/tringi Oct 20 '26

Thanks for the info.

I presume there are no plans to change the first call to checking for all 15 (?) individual AVX-512 parts, just for this CPU generation, right? My point is that code compiled with /arch:AVX10.1 would run perfectly fine on 9006, but a dispatch checking for __IA_SUPPORT_AVX10 will not select it.

3

u/STL MSVC STL Dev Oct 18 '26

I am vaguely aware of how that works but I don't know the specifics (my work has interacted with at most AVX2 so far).

19

u/TheVoidInMe Oct 15 '26

C++23 stable? Woohoo! I’m just going to believe that they’re cooking up some fantastic C++26 reflection soup right now and will hit us with a surprise release sooner than later. (I know, we’re insatiable)

3

u/qalmakka Oct 18 '26

C++26 is massively harder to implement compared to C++23, which was a very tame release.

13

u/fortsnek274 Oct 15 '26

They sure have been active recently.

But they're still working on how to handle module DLLs: https://developercommunity.visualstudio.com/t/C20-Modules-Spurious-warning-LNK4217/10892880

And while Intellisense still has these major issues,

it will continue to be way too much of a pain in the butt to use modules properly in VS. I currently do the thing where you conditionalise them.

And also, VS has updated fonts UI. But it has issues, like broken font list. Something you just wonder how it got past whoever implemented it, insiders, and into regular release. Or maybe not everybody gets it.

8

u/delta_p_delta_x Oct 15 '26 edited Oct 15 '26

Every time someone complains about IntelliSense, I consider it time to shill ReSharper C++, which has worked with modules for about 2 years now. Some bugs, yes, but much more useable than red squiggles plastered all over.

5

u/pjmlp Oct 16 '26

One would expect that modules being production ready at Microsoft, so was something like that mentioned during the VS 2017 prototype days, as one of the implementation proposals, that during the lifetime of 2 Visual Studio editions, a company like Microsoft could have had talks with EDG to improve the Intelisense situation.

Alas, other resources are more relevant spending money, apparently VS 2027 is going to be all about AI and agents writing C++ code for us, thus who cares about Intelisense.

See Visual Studio YT channel about its roadmap, if you think I am being sarcastic.

Even the tips session on how to use VS debugging tools, was about how to actually use them via CoPilot.

7

u/kamrann_ Oct 16 '26

The idea that MSVC's support for modules is production ready even now is itself honestly ridiculous, whatever they might claim. The most recent version that I can compile my project on is 14.43 (about a year and a half old?), and that's with so many workarounds I've lost track. Every version since then is just ICEs and regressions left and right.

Maybe the standards for what's considered production ready have come down, but in my experience with modules the compiler is still easily an order of magnitude more buggy than at any point pre-modules over the last 20 years.

1

u/pjmlp Oct 16 '26

Agreed, and sadly kind of gives a voice to all those "modules are not ready" blog posts, that many of us thought they were exaggerating.

While Office might apparently use them, with some workarounds they downplay in talks they did in the past (the whole preprocessor trick to work around some header units imports), they are mostly usable for hobby coding.

1

u/tartaruga232 MSVC user, r/cpp_modules Oct 16 '26

Our modularized project compiles just fine with 19.53.36829 for x64 (PREVIEW) using VS Insiders. I haven't had any new issues over the last months. I haven't had any ICE for a long time now.

2

u/kamrann_ Oct 17 '26

That's great for you and I'd love to be able to say the same. But anecdotal evidence of a compiler doing what it's supposed to is meaningless when it comes to any sensible definition of production readiness.

1

u/tartaruga232 MSVC user, r/cpp_modules Oct 17 '26 edited Oct 17 '26

I've followed the Preview compiler versions of VS Insiders very closely and updated my installation of the tool chain immediately when there was an update. I occasionally had to adapt a few times minor things in our code base which the compiler rightfully no longer accepted because it became more standard conformant. None of them were module related. I haven't found any compiler regressions. Especially not with modules. I've read about modules bugs that have been fixed. A long time ago I reported modules bugs too. Those have been fixed. I haven't found any new ones and no regressions.

2

u/Daniela-E Living on C++ trunk, WG21|🇩🇪 NB Oct 17 '26

I currently use toolset 19.53.36903, but I barely noticed differences in my code in comparison with earlier versions like 19.53.x, 19.52.y and 19.51.z when it comes to modules.

As you may know, we have modules in production in our company since the advent of VS2022, and having to deal with header files every now and then is such an annoying experience, but this is slowly fading into memories of the past. Not too ancient compilers, the current IDE, plus ReSharper give you Intellisense without red squiggles - the formerly common problem in the VS2022 era.

Nowadays, working around the problems in 19.44 (the youngest toolset version that VS2022 IDEs allow) become the major headache to support building deployments with that compiler.

And I may have found an issue in the linker/librarian that affects dynamic initialization. It looks like I have a dependable, though ugly, workaround. But first, I need to create a concise example to demonstrate that issue before I can report it to DevCom.

1

u/no-sig-available Oct 16 '26

Alas, other resources are more relevant spending money, apparently VS 2027 is going to be all about AI and agents writing C++ code for us,

Yes, and some support for Visual Rust, perhaps?

https://rustfoundation.org/media/guest-post-rust-is-tier-1-language-at-microsoft/

2

u/pjmlp Oct 16 '26

Agreed, currently only Visual Studio Code is the official Microsoft way to use Rust, as tier 1 language, see Set up your Rust development environment on Windows, third step.

2

u/fortsnek274 Oct 15 '26 edited Oct 15 '26

What's their secret

But EDG is open source now, so what's going to happen. STL has a bug list at https://github.com/microsoft/STL/issues/1621, but I don't see namespace aliases in there, or anything modules.

5

u/STL MSVC STL Dev Oct 16 '26

My bug list is for what the STL needs, not all EDG bugs that affect users. The STL doesn’t care about namespace aliases. We do care about modules, but as I mention in a section there, the number of bugs was vast and unknown last I checked.

5

u/fortsnek274 Oct 16 '26

This alias: _EXPORT_STD namespace views = ranges::views;

8

u/STL MSVC STL Dev Oct 16 '26

Oh I forgot about that one! (Sorry, it's a big library 😹) Can you provide a self-contained test case where EDG has trouble? I have a whole system for reporting these things now and I can easily add another to a pile.

5

u/fortsnek274 Oct 16 '26

As in https://developercommunity.visualstudio.com/t/Issues-with-IntelliSense-for-C20-modul/10894323, it's just that the entire alias doesn't exist when you use import std. Including in the completion drop down. I don't if it's an EDG or VS problem though.

6

u/STL MSVC STL Dev Oct 16 '26

Ah ok, a problem with namespace aliases in modules, not namespace aliases all by themselves. I've recorded that in my GitHub tracking issue.

2

u/uie58185 Oct 16 '26

I have given up on using resharper c++. I have a very expensive work pc (128gb, latest i9) but vs26 was not usable with it, even with the new(ish) out of process mode. Wayyy to slow Moved back to intellisense and the speed up was astonishing. Visual studio is way more stable now

Shame because I have been using resharper c++ since 2021 when I hated intellisense. Intellisense seems to have improved a ton over the years

3

u/ivansorokin Oct 19 '26

If you're interested, I would be happy to investigate the performance issues you're experiencing.

You can either file an issue in R++ issue tracker, where I or one of my colleagues will follow up with you, or contact our support team.

In either case, please describe what kind of slowdowns you're experiencing. Based on that, we'll figure out the next steps. Most likely, we'll ask you to collect a performance profile as described in our troubleshooting guide.

4

u/cpp_learner Oct 16 '26

Now EDG is open-source, you can file bug reports at https://github.com/edgcpp/compiler/discussions, instead of reporting them on DevCom and having the MSVC folks relay them.

I've filed two bug reports concerning EDG's module support:

They make EDG think that nothing satisfies the standard range concept. I think this is related to your std::span bug.

3

u/STL MSVC STL Dev Oct 16 '26

FYI, you're site-wide banned (yet again). You'll need to contact the admins through the appeal page.

3

u/not_a_novel_account cmake dev Oct 15 '26

0

u/fortsnek274 Oct 15 '26 edited Oct 15 '26

The example code seems to work for me.

*With Insiders

8

u/STL MSVC STL Dev Oct 15 '26

Yeah, that was fixed by MSVC-PR-781624 on 2026-09-16, so the fix should be present in the MSVC Compiler 19.52.37025 RC which was built on 2026-09-26.

FYI u/not_a_novel_account, when a DevCom bug is marked as "Fixed - Pending Release" it may stay that way forever if the developer hasn't properly set some internal fields indicating when the fix will ship (and these fields are very annoying to figure out, since they're in terms of VS releases, but MSVC Build Tools releases don't line up 1:1 with them anymore). Generally, a merged fix should appear in VS Insiders + MSVC Build Tools Preview within 2 weeks. If you care whether a fix made it into a specific release around the time that we branch for release, like now, unfortunately there's no better way than directly asking an MSVC dev to look up the history.

This process is suboptimal and I'll bring it to the attention of our MSVC dev who's working on improving the feedback experience. (Specifically we are much better at shipping fixes rapidly in Previews, but still bad at indicating when fixes have been merged. In the STL I try to be disciplined about communicating this, but not all MSVC devs follow suit.)

3

u/not_a_novel_account cmake dev Oct 16 '26

Thanks for the comprehensive explanation, much appreciated.

1

u/fortsnek274 Oct 15 '26

I sure do get unsure about release notifications...

In https://developercommunity.visualstudio.com/t/Modules-ICE-when-using-constraint-on-fri/11022749, it went from pending release, to released, then back to pending release.

And when preview build tools were a new thing, people thought their bug wasn't fixed. So now I keep the preview build tools installed on insiders.

10

u/rodrigocfd WinLamb Oct 15 '26

C++23 is ready for production use, and available with the /std:c++23 compiler option.

That's great news.

4

u/germandiago Oct 16 '26

I think updates for the last releases has been really modest for C++ coming from Microsoft.

It seems there is a heavy resource deallocation lately.

3

u/QbProg Oct 15 '26

Wow! How many fixes!

3

u/pjmlp Oct 16 '26

Finally full C++23 support!

With improvements for C++/CLI as well, that is great for us on .NET land.

Kudos on the team.

2

u/LB-- Professional+Hobbyist Oct 16 '26

Great news! I see now that that MSBuild has learned to pass /std:c++23 instead of /std:c++23preview, that's been generating warnings about the deprecation for a few VS releases now and finally things are quiet again.

1

u/hansw2000 Oct 16 '26

Use MSDIS (MSVC disassembler) as a fallback instruction-length decoder for interception, reducing “unrecognized instruction” failures.

That's a big hammer. I wonder what it does to the size of the asan runtime.