-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v20.x backport] deps: V8: backport 9ab40592f697 #56782
Conversation
Review requested:
|
We'd need to wait for #56781 to land, and we should amend the commit message to use the metadata of the other PR |
- Switch compiler to clang, this workarounds https://archriscv.felixc.at/.status/log.htm?url=logs/389-ds-base/389-ds-base-3.1.1-3.log See more details in riscv-forks/electron#7 - Cherry-pick icache flush fix, upstreamed: - nodejs/node#56781 - nodejs/node#56782 - Should still need nocheck
- Switch compiler to clang, this workarounds https://archriscv.felixc.at/.status/log.htm?url=logs/389-ds-base/389-ds-base-3.1.1-3.log See more details in riscv-forks/electron#7 - Cherry-pick icache flush fix, upstreamed: - nodejs/node#56781 - nodejs/node#56782 - Should still need nocheck
- Switch compiler to clang, this workarounds https://archriscv.felixc.at/.status/log.htm?url=logs/389-ds-base/389-ds-base-3.1.1-3.log See more details in riscv-forks/electron#7 - Cherry-pick icache flush fix, upstreamed: - nodejs/node#56781 - nodejs/node#56782 - Should still need nocheck
can you rebase please, the issue on smartos should have been fixed. |
Original commit message: [riscv] Flush icache in both local and remote harts Fix the I-Cache flush flag according to the implementation of flush_icache_mm in Linux kernel. Change-Id: I6e6b1f56c377c2c0a629e170737bfac6c357ce8d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6080611 Commit-Queue: Yahan Lu (LuYahan) <[email protected]> Reviewed-by: Ji Qiu <[email protected]> Cr-Commit-Position: refs/heads/main@{#97673} Refs: v8/v8@9ab4059 Co-authored-by: kxxt <[email protected]>
Rebased. Thanks for the ping. BTW should I do anything manually targeting v22.x. #56781 should apply to v22.x (except the v8_embedder_string part). Are there any automatic way to pick #56781 into v22.x or should I open another PR like this one? |
If lands cleanly it will be picked up automatically |
Landed in 5c9a397 |
Original commit message: [riscv] Flush icache in both local and remote harts Fix the I-Cache flush flag according to the implementation of flush_icache_mm in Linux kernel. Change-Id: I6e6b1f56c377c2c0a629e170737bfac6c357ce8d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6080611 Commit-Queue: Yahan Lu (LuYahan) <[email protected]> Reviewed-by: Ji Qiu <[email protected]> Cr-Commit-Position: refs/heads/main@{#97673} Refs: v8/v8@9ab4059 PR-URL: #56781 Backport-PR-URL: #56782 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Original commit message: [riscv] Flush icache in both local and remote harts Fix the I-Cache flush flag according to the implementation of flush_icache_mm in Linux kernel. Change-Id: I6e6b1f56c377c2c0a629e170737bfac6c357ce8d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6080611 Commit-Queue: Yahan Lu (LuYahan) <[email protected]> Reviewed-by: Ji Qiu <[email protected]> Cr-Commit-Position: refs/heads/main@{#97673} Refs: v8/v8@9ab4059 PR-URL: #56781 Backport-PR-URL: #56782 Co-authored-by: kxxt <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Debadree Chatterjee <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Manual backport for v20.x of #56781
Original commit message:
Refs: v8/v8@9ab4059