build: enable Maglev for riscv64

[JamieMagee]

V8's BUILD.gn has listed riscv64 as a Maglev-supported architecture since V8 14.0, and the source files exist in deps/v8/src/maglev/riscv/. But Node.js never wired it up on its side:

• configure.py didn't include riscv64 in maglev_enabled_architectures
• tools/v8_gypfiles/v8.gyp had no GN-scraper conditions for riscv64 in the two Maglev source blocks (it had arm, arm64, x64, s390x, ppc64, just not riscv64)

This adds riscv64 to both, following the same approach as #60863 which did this for s390x.

Refs: nodejs/build#4099

[nodejs-github-bot]

Review requested:

• @nodejs/gyp
• @nodejs/v8-update

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/72555/

[nodejs-github-bot]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7110/

[nodejs-github-bot]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7110/

[nodejs-github-bot]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7110/

[Renegade334]

Started CI to satisfy the PR requirements although there is no riscv runner – perhaps someone from @nodejs/platform-riscv64 can verify the build passes the node/V8 test suites?

[sxa]

@Renegade334 Yep I'm looking at what I can do - although we've got quite a lot of RISC-V PRs around at the moment so it won't be quick.

[JamieMagee]

Rebased onto latest main.

[kxxt]

Started CI to satisfy the PR requirements although there is no riscv runner – perhaps someone from @nodejs/platform-riscv64 can verify the build passes the node/V8 test suites?

I am testing this one in my CI to see if any tests regress: https://github.com/riscv-forks/node-riscv/actions/runs/28420684700?pr=5

[kxxt]

I can confirm that there are no regressions with this change. Test results:

[19:21|% 100|+ 5701|-   2]: Done
Failed tests:
out/Release/node /home/kxxt/node-riscv/test/parallel/test-snapshot-reproducible.js
out/Release/node /home/kxxt/node-riscv/test/wpt/test-compression.js

The first one is a known failure and the second one is flaky, which should be fixed by #64027.

[Renegade334]

RSLGTM

[github-actions]

Failed to start CI

- Validating Jenkins credentials
✔  Jenkins credentials valid
- Querying data for job/node-test-pull-request/72555/
[SyntaxError: Unexpected token '<', ..."    
  https://github.com/nodejs/node/actions/runs/28438109518

[github-actions]

Failed to start CI

- Validating Jenkins credentials
✔  Jenkins credentials valid
- Querying data for job/node-test-pull-request/72555/
[SyntaxError: Unexpected token '<', ..."    
  https://github.com/nodejs/node/actions/runs/28444126538

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74455/

[sxa]

Kicked off https://ci.nodejs.org/job/node-test-pull-request/74455/ manually as the failure message from an hour ago is referencing node-test-pull-request/72555/ which no longer exists on the CI.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74457/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/74460/

[sxa]

Win32 failures in latest run are due to #64216 so while I'd probably be ok to land it if you want to rebase so we can get a clean CI that would be good.