Michaël Zasso
Michaël Zasso
I'm not sure what to do about it. Are we close to switching to ClangCL?
Thanks for the patch! I will update this PR once https://github.com/nodejs/node/pull/54682 is on `main`
Added https://github.com/nodejs/node-v8/pull/289
armv7 cross-compilation failed: https://ci.nodejs.org/job/node-cross-compile/49971/nodes=cross-compiler-rhel9-armv7-gcc-12-glibc-2.28/console (@richardlau)
There's nothing special about the canary CI. It's using the same machines and config as `main`
According to https://en.wikipedia.org/wiki/Xcode#Xcode_11.0_-_14.x_(since_SwiftUI_framework)_2, clang 15 wasn't included for a long time in Xcode (it's the LLVM column): 
In Jenkins, the buildbots use Clang 12 In GitHub actions, it seems to be Apple Clang 15 (LLVM 16). (on macOS)
on Linux, I think we only use Clang in GitHub actions, and it's on version 18.
@ronag `v8.serialize({a: new Int32Array(1024)})` returns a Buffer instance
I opened https://github.com/nodejs/node/pull/54565 so we can work on https://github.com/nodejs/node/pull/54526 with no rush.