Michaël Zasso

https://ci.nodejs.org/job/node-test-commit-v8-linux/6686/nodes=benchmark-ubuntu2204-intel-64,v8test=v8test/console > 10:35:55 /home/iojs/build/workspace/node-test-commit-v8-linux/out/Release/node: bad option: --always-turbofan https://github.com/nodejs/node/commit/ab7d3693d60004dca93107e61b5f73e56cec9106

Commit: https://github.com/nodejs/node-v8/commit/6bb55c4c9366e94acd9d83367506ba557193f48a CI: https://ci.nodejs.org/job/node-test-commit/82585/ V8: https://ci.nodejs.org/job/node-test-commit-v8-linux/6742/

For the second issue, I tried to force gcc-11 on the release machine and rebuild. The error is still here: ``` /opt/rh/gcc-toolset-11/root/usr/lib/gcc/aarch64-redhat-linux/11/include/arm_neon.h:3353:28: note: initializing argument 1 of ‘uint64_t vgetq_lane_u64(uint64x2_t, int)’...

I wonder if the solution may be to add `-flax-vector-conversions` as suggested by the error message. Maybe Clang doesn't have this requirement.

Here's a full CI to get more info: https://ci.nodejs.org/job/node-test-commit/67540/

Failed on https://ci.nodejs.org/job/node-test-commit-arm-debug/11011/nodes=ubuntu2004_debug-arm64/console

The default value of the flag is "all" in Clang: https://github.com/llvm/llvm-project/blob/54067c5fbe9fc13ab195cdddb8f17e18d72b5fe4/clang/include/clang/Basic/LangOptions.def#L133-L134

Testing with the option (https://github.com/nodejs/node-v8/commit/4feafb221aebc3e9f50fd29b34b728ee619c2c8a): https://ci.nodejs.org/job/node-test-commit-arm-debug/11012/

First issue fixed by https://github.com/nodejs/build/pull/3596 Second issue fixed by https://github.com/nodejs/node/pull/51257

Here's how they are handling it: https://github.com/gahaas/node/commit/088fb7e762bf9400fe0231ad8d753c64d5d9d1d0