deps: V8: cherry-pick d8dc66f 3cab84c 471f862 77599ff

[luyahan]

Fix riscv64 segment fault
origin commit :

[riscv64][sparkplug] Fix sparkplug verify framesize failed

Change-Id: I7481749ba3d5c41d7405b0d88a51defbc8bec9d6
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3093009
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/master@{#76277}

Refs: v8/v8@d8dc66f

[riscv64] Use s1 to save code_obj

The caller saved a4 may be clobbered by the callee function. So we substitute it with the callee saved s1 to save code_obj.

Change-Id: Iebe707cbaa62d47fdee0aa117e32e88f67dac743
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3096886
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Ji Qiu <qiuji@iscas.ac.cn>
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/master@{#76294}

Refs: v8/v8@3cab84c

[riscv64] Link should greater and equal zero

Change-Id: Ieeb5888efc068707766aef6ba6fc842c5deaaf9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3146673
Commit-Queue: Yahan Lu <yahan@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Reviewed-by: Ji Qiu <qiuji@iscas.ac.cn>
Cr-Commit-Position: refs/heads/main@{#76784}

Refs: v8/v8@471f862

[riscv64] Add block before LoadAddress

fix node.js DCHECK failed
issue: https://github.com/riscv-collab/v8/issues/514

Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/main@{#77750}

Refs: v8/v8@77599ff

[nodejs-github-bot]

Review requested:

• @nodejs/v8-update

[XieJiSS]

@luyahan Hi, I‘m trying to build nodejs v16.13.1 these days. By applying your patch 1 and 2 (d8dc66f & 3cab84c, ref: riscv-collab/v8#516 (comment)), and if configured with --without-inspector, nodejs v16.13.1 can compile & pass all tests on SiFive Unmatched boards. Without specifying --without-inspector, test/parallel/test-v8-coverage.js would crash (signal 11). Is this what patch 3 is for?

[luyahan]

@luyahan Hi, I‘m trying to build nodejs v16.13.1 these days. By applying your patch 1 and 2 (d8dc66f & 3cab84c, ref: riscv-collab/v8#516 (comment)), and if configured with --without-inspector, nodejs v16.13.1 can compile & pass all tests on SiFive Unmatched boards. Without specifying --without-inspector, test/parallel/test-v8-coverage.js would crash (signal 11). Is this what patch 3 is for?

thanks your info ，i will to look it.

[gengjiawen]

@luyahan You may need use https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-v8-backport-sha

Generally you need bump common.gypi and we generally not squash cherrypick commit

[luyahan]

@luyahan You may need use https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-v8-backport-sha

Generally you need bump common.gypi and we generally not squash cherrypick commit

@gengjiawen I run git node backport

luyahan@p9-plct:~/source/node $ git node v8 backport 77599ff
✔ Update local V8 clone
❯ V8 commit backport
  ✔ Get current V8 version
  ✔ Generate patches
  ❯ Apply and commit patches to deps/v8
    ❯ Commit 77599ffe0a74
      ⠦ Apply patch
      ◼ Increment embedder version number
      ◼ Commit patch

? Resolve merge conflicts and enter 'RESOLVED' ‣

▸ Invalid input

What can i do to fix conflict? I can't find any conflicts in edit.

[gengjiawen]

@luyahan You may need use nodejs/node-core-utils@main/docs/git-node.md#git-node-v8-backport-sha
Generally you need bump common.gypi and we generally not squash cherrypick commit

@gengjiawen I run git node backport

luyahan@p9-plct:~/source/node $ git node v8 backport 77599ff
✔ Update local V8 clone
❯ V8 commit backport
  ✔ Get current V8 version
  ✔ Generate patches
  ❯ Apply and commit patches to deps/v8
    ❯ Commit 77599ffe0a74
      ⠦ Apply patch
      ◼ Increment embedder version number
      ◼ Commit patch

? Resolve merge conflicts and enter 'RESOLVED' ‣

▸ Invalid input

What can i do to fix conflict? I can't find any conflicts in edit.

Not sure (is you local branch reset to nodejs:v16.x-staging ). You can create an issue here https://github.com/nodejs/node-core-utils/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc

[targos]

I think it's okay to squash all fixes here since they all apply to the same platform.

[gengjiawen]

I think it's okay to squash all fixes here since they all apply to the same platform.

I am okay with this. So only bump common.gypi lgtm

[targos]

@luyahan did you target v16.x-staging because the fixes are already in v17.x ?

[luyahan]

@luyahan Hi, I‘m trying to build nodejs v16.13.1 these days. By applying your patch 1 and 2 (d8dc66f & 3cab84c, ref: riscv-collab/v8#516 (comment)), and if configured with --without-inspector, nodejs v16.13.1 can compile & pass all tests on SiFive Unmatched boards. Without specifying --without-inspector, test/parallel/test-v8-coverage.js would crash (signal 11). Is this what patch 3 is for?

This pacth can fix Refs: v8/v8@77599ff

[luyahan]

@luyahan did you target v16.x-staging because the fixes are already in v17.x ?

Yes, these patch had been add into v17.x.

[luyahan]

I reopen this pr in #41566