INTERNAL COMPILER ERROR in GitHub Actions (Windows)

[tniessen]

The build-windows job is failing in GitHub Actions with log outputs such as the following:

2024-06-06T15:11:06.5035248Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(150,75): error C2100: you cannot dereference an operand of type 'v8::internal::compiler::turboshaft::WordRepresentation' [D:\a\node\node\tools\v8_gypfiles\v8_compiler.vcxproj]
2024-06-06T15:11:06.8233400Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(136,15): fatal  error C1907: unable to recover from previous error(s); stopping compilation [D:\a\node\node\tools\v8_gypfiles\v8_compiler.vcxproj]
2024-06-06T15:11:06.8237233Z D:\a\node\node\deps\v8\src\compiler\turboshaft\representations.h(457,49): message : while evaluating constexpr function 'v8::internal::compiler::turboshaft::WordRepresentation::value' [D:\a\node\node\tools\v8_gypfiles\v8_compiler.vcxproj]
2024-06-06T15:11:06.8241123Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(150,75): message : while evaluating constexpr function 'v8::internal::compiler::turboshaft::WordRepresentation::operator v8::internal::compiler::turboshaft::WordRepresentation::Enum' [D:\a\node\node\tools\v8_gypfiles\v8_compiler.vcxproj]
2024-06-06T15:11:06.8244223Z   INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.40.33807\bin\HostX64\x64\CL.exe'
2024-06-06T15:11:06.8245867Z       Please choose the Technical Support command on the Visual C++
2024-06-06T15:11:06.8246835Z       Help menu, or open the Technical Support help file for more information
2024-06-06T15:11:08.2511636Z   gap-resolver.cc
2024-06-06T15:11:09.7950818Z   build-graph-phase.cc
2024-06-06T15:11:14.0480758Z   instruction.cc
2024-06-06T15:11:20.7664079Z   csa-optimize-phase.cc
2024-06-06T15:11:28.0510169Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(150,75): error C2100: you cannot dereference an operand of type 'v8::internal::compiler::turboshaft::WordRepresentation' [D:\a\node\node\tools\v8_gypfiles\v8_turboshaft.vcxproj]
2024-06-06T15:11:28.2696958Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(136,15): fatal  error C1907: unable to recover from previous error(s); stopping compilation [D:\a\node\node\tools\v8_gypfiles\v8_turboshaft.vcxproj]
2024-06-06T15:11:28.3949647Z D:\a\node\node\deps\v8\src\compiler\turboshaft\representations.h(457,49): message : while evaluating constexpr function 'v8::internal::compiler::turboshaft::WordRepresentation::value' [D:\a\node\node\tools\v8_gypfiles\v8_turboshaft.vcxproj]
2024-06-06T15:11:28.5043162Z D:\a\node\node\deps\v8\src\compiler\turboshaft\opmasks.h(150,75): message : while evaluating constexpr function 'v8::internal::compiler::turboshaft::WordRepresentation::operator v8::internal::compiler::turboshaft::WordRepresentation::Enum' [D:\a\node\node\tools\v8_gypfiles\v8_turboshaft.vcxproj]
2024-06-06T15:11:28.6606579Z   INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.40.33807\bin\HostX64\x64\CL.exe'
2024-06-06T15:11:28.8637254Z       Please choose the Technical Support command on the Visual C++
2024-06-06T15:11:29.0670434Z       Help menu, or open the Technical Support help file for more information

Example runs:

• https://github.com/nodejs/node/actions/runs/9403659736
• https://github.com/nodejs/node/actions/runs/9403178713
• https://github.com/nodejs/node/actions/runs/9403172862
• https://github.com/nodejs/node/actions/runs/9402871021
• https://github.com/nodejs/node/actions/runs/9402762584
• https://github.com/nodejs/node/actions/runs/9402061407
• https://github.com/nodejs/node/actions/runs/9398127117
• https://github.com/nodejs/node/actions/runs/9403178713

[joyeecheung]

Is it the same as nodejs/build#3739 ? @nodejs/platform-windows

[legendecas]

Saw the same error internally on VS 17.10. We downgraded VS to 17.9 fixed the problem.

[StefanStojanovic]

Is it the same as nodejs/build#3739 ? @nodejs/platform-windows

Yes, this is the same, as written in that issue, the fix for this is implemented and should be released in the next Visual Studio update.