Skip to content

Toolset update: MSVC Compiler 19.52.36307.1#6260

Open
StephanTLavavej wants to merge 18 commits intomicrosoft:mainfrom
StephanTLavavej:april-update
Open

Toolset update: MSVC Compiler 19.52.36307.1#6260
StephanTLavavej wants to merge 18 commits intomicrosoft:mainfrom
StephanTLavavej:april-update

Conversation

@StephanTLavavej
Copy link
Copy Markdown
Member

@StephanTLavavej StephanTLavavej commented Apr 17, 2026

  • Got 1024 cores of Dpsv6 in uksouth, add comments.
  • VS-PR-713550 on 2026-03-03 added -Preview -NoLogo to Launch-VsDevShell.ps1.
  • Cycle locations.
  • Remove TRANSITION comment about DefaultOutboundAccess.
    • To be safe, I'm going to keep passing -DefaultOutboundAccess $false.
  • Python 3.14.4 (now required).
  • CUDA 13.2.1.
    • Intentionally not increasing the requirement for patch versions.
  • MSVC Compiler 19.52.36307.1 (now required).
    • Still can't update yvals_core.h due to the internal toolset.
  • Windows 11 SDK 10.0.28000 (now required for STL development, but not usage).
    • Verified that warnings still repro.
  • VS-PR-713693 on 2026-03-03 fixed DevCom-11012299 "EDG crashes when handling placement-new".
  • VS-PR-713693 on 2026-03-03 fixed VSO-2581623 "EDG should implement __builtin_is_implicit_lifetime".
  • libcxx/expected_results.txt: Cleanup an unnecessary MSVC-internal skip.
  • Some constexpr FAILs are now passing.
  • Extend Clang workaround to EDG.
    • Reported VSO-2941370 "EDG __builtin_is_implicit_lifetime isn't checking for trivial constructors".
  • New pools.
  • MSVC-PR-720628 on 2026-03-26 fixed DevCom-11070772 "MSVC fails to activate a union member of certain empty class type during constant evaluation".
  • Work around VSO-2946529 "/analyze emits warning C28285 for _BitScanForward declared by winnt.h".
    • This has already been fixed by OS-PR-14602802 on 2026-01-22, but I'm not sure when it'll ship (i.e. in a patch release of 10.0.28000.x, or in a whole new version which would take much longer).
  • Work around VSO-1639191 "Excessive memory consumption with /analyze targeting x86".
    • Fine-grained workarounds don't appear to be viable, so I'm disabling the entire tests. Because this is specific to x86 /analyze, we still have reasonable coverage of x86 vanilla and non-x86 /analyze.
  • Work around Ranges tests consuming excessive compiler memory #3567.
    • The tests for ranges::replace_copy and ranges::replace_copy_if are now OOMing for x86 /permissive configurations. Add a targeted workaround for this. Note that we still have reasonable coverage of x86 strict and non-x86 /permissive.

StephanTLavavej and others added 15 commits April 17, 2026 04:06
To be safe, I'm going to keep passing `-DefaultOutboundAccess $false`.
Intentionally not increasing the requirement for patch versions.
Still can't update yvals_core.h due to the internal toolset.
Followup to GH 6197. Any mention of a test as FAIL or SKIPPED for any configuration causes the MSVC-internal harness to skip it for all configurations.
Reported VSO-2941370 "EDG `__builtin_is_implicit_lifetime` isn't checking for trivial constructors".
…ivate a union member of certain empty class type during constant evaluation".
@StephanTLavavej StephanTLavavej requested a review from a team as a code owner April 17, 2026 14:09
@StephanTLavavej StephanTLavavej added the infrastructure Related to repository automation label Apr 17, 2026
@github-project-automation github-project-automation bot moved this to Initial Review in STL Code Reviews Apr 17, 2026
@StephanTLavavej StephanTLavavej moved this from Initial Review to Work In Progress in STL Code Reviews Apr 17, 2026
@StephanTLavavej StephanTLavavej moved this from Work In Progress to Final Review in STL Code Reviews Apr 17, 2026
…argeting x86".

Fine-grained workarounds don't appear to be viable, so I'm disabling the entire tests.

Because this is specific to x86 /analyze, we still have reasonable coverage of x86 vanilla and non-x86 /analyze.
The tests for `ranges::replace_copy` and `ranges::replace_copy_if` are now OOMing
for x86 /permissive configurations. Add a targeted workaround for this.

Note that we still have reasonable coverage of x86 strict and non-x86 /permissive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Related to repository automation

Projects

Status: Final Review

Development

Successfully merging this pull request may close these issues.

1 participant