Version
v27.0.0-pre
Platform
Linux test-loongson-fedora43-loong64-1 7.1.0-0.rc7.260610gacb7500801e9.49.fc43.loongarch64 #1 SMP PREEMPT_DYNAMIC Fri Jun 12 18:09:12 CST 2026 loongarch64 GNU/Linux
Subsystem
v8
What steps will reproduce the bug?
Build Node.js from source on a Loong64 machine:
./configure --openssl-no-asm
make -j16
How often does it reproduce? Is there a required condition?
It reproduces 100% of the time when compiling the current main branch on the Loong64 architecture.
What is the expected behavior? Why is that the expected behavior?
The compilation and linking process should complete successfully without undefined reference errors.
What do you see instead?
We recently ran into a linking error on Loong64 during the Node.js build process: undefined reference to VisitUint64Add3WithCarry in the V8 Turboshaft compiler backend.
Here is the CI failure log for reference:
https://ci.nodejs.org/job/node-test-commit-loongarch64/nodes=clfs23-64/1168/console
I’ve identified two possible paths forward to resolve the issue:
- Cherry-pick upstream V8 patches:
Applying the following two V8 Gerrit CLs to our current V8 tree fixes the linker issue. I have verified this locally, and the build succeeds after applying them:
https://chromium-review.googlesource.com/c/v8/v8/+/8393957
https://chromium-review.googlesource.com/c/v8/v8/+/8416173
- Upgrade V8 to 15.6.4:
V8 15.6.4 already includes these changes and compiles successfully on our end.
I was wondering if there are any current plans to upgrade V8 to 15.6.4 in the near future? If a version bump is already planned, that would naturally resolve this problem.
I would love to get your advice on which approach the project prefers—whether I should submit a PR to cherry-pick these two patches, or wait for a V8 minor version bump.
Thanks so much for your time and guidance!
Additional information
No response
Version
v27.0.0-pre
Platform
Subsystem
v8
What steps will reproduce the bug?
Build Node.js from source on a Loong64 machine:
./configure --openssl-no-asm
make -j16
How often does it reproduce? Is there a required condition?
It reproduces 100% of the time when compiling the current main branch on the Loong64 architecture.
What is the expected behavior? Why is that the expected behavior?
The compilation and linking process should complete successfully without undefined reference errors.
What do you see instead?
We recently ran into a linking error on Loong64 during the Node.js build process: undefined reference to VisitUint64Add3WithCarry in the V8 Turboshaft compiler backend.
Here is the CI failure log for reference:
https://ci.nodejs.org/job/node-test-commit-loongarch64/nodes=clfs23-64/1168/console
I’ve identified two possible paths forward to resolve the issue:
Applying the following two V8 Gerrit CLs to our current V8 tree fixes the linker issue. I have verified this locally, and the build succeeds after applying them:
https://chromium-review.googlesource.com/c/v8/v8/+/8393957
https://chromium-review.googlesource.com/c/v8/v8/+/8416173
V8 15.6.4 already includes these changes and compiles successfully on our end.
I was wondering if there are any current plans to upgrade V8 to 15.6.4 in the near future? If a version bump is already planned, that would naturally resolve this problem.
I would love to get your advice on which approach the project prefers—whether I should submit a PR to cherry-pick these two patches, or wait for a V8 minor version bump.
Thanks so much for your time and guidance!
Additional information
No response