Skip to content
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

Unreachable error in wasm rollup when building on riscv64 #8

Open
kxxt opened this issue Mar 12, 2025 · 1 comment
Open

Unreachable error in wasm rollup when building on riscv64 #8

kxxt opened this issue Mar 12, 2025 · 1 comment

Comments

@kxxt
Copy link

kxxt commented Mar 12, 2025

When building electron, chromium or devtools-frontend on riscv64, an obscure unreachable error occurs sometimes. Retrying it might solve the issue, like revyos/revyos#27

FAILED: gen/front_end/ui/legacy/legacy.js 
python3 ../../third_party/node/node.py ../../node_modules/@rollup/wasm-node/dist/bin/rollup --silent --config ../../scripts/build/rollup.config.mjs --input gen/front_end/ui/legacy/legacy.prebundle.js --file gen/front_end/ui/legacy/legacy.js
['/home/kxxt/devtools-frontend/third_party/node/linux/node-linux-x64/bin/node', '../../node_modules/@rollup/wasm-node/dist/bin/rollup', '--silent', '--config', '../../scripts/build/rollup.config.mjs', '--input', 'gen/front_end/ui/legacy/legacy.prebundle.js', '--file', 'gen/front_end/ui/legacy/legacy.js'] failed:

[!] RuntimeError: unreachable
    at null.<anonymous> (wasm://wasm/005c7862:1:1261892)
    at null.<anonymous> (wasm://wasm/005c7862:1:1372394)
    at null.<anonymous> (wasm://wasm/005c7862:1:1017827)
    at null.<anonymous> (wasm://wasm/005c7862:1:1055580)
    at null.<anonymous> (wasm://wasm/005c7862:1:774288)
    at null.<anonymous> (wasm://wasm/005c7862:1:164288)
    at null.<anonymous> (wasm://wasm/005c7862:1:267427)
    at null.<anonymous> (wasm://wasm/005c7862:1:1162176)
    at null.<anonymous> (wasm://wasm/005c7862:1:893047)
    at null.<anonymous> (wasm://wasm/005c7862:1:905690)

Tested combinations:

Platform Product version v8 vendor compiler result
P550 sv48 Node.js 23.8.0-4.1 w/ trap-handler disabled 12.9.28.202 archriscv clang FAIL
P550 sv48 Node.js 23.8.0 12.9.28.202 luyahan clang 16 PASS
P550 sv39 Node.js 23.8.0-4.1 w/ trap-handler disabled 12.9.28.202 archriscv clang FAIL
P550 sv48 Node.js 23.9.0 w/ trap-handler disabled - archriscv gcc FAIL
P550 sv48 Node.js 23.9.0 - archriscv gcc PASS
P550 sv48 Node.js 22.14.0-2 12.4.21.254 archriscv gcc PASS
P550 sv48 electron 32.3.1 12.8.374.38-electron.0 riscv-forks cr clang PASS
P550 sv48 electron 33.4.4 13.0.245.25-electron.0 riscv-forks cr clang PASS
SG2042 sv39 Node.js 23.9.0-1 w/ trap-handler disabled - archriscv clang FAIL
@kxxt
Copy link
Author

kxxt commented Mar 12, 2025

This seems to be caused by the patch that disables trap handler to suite sv39 systems: #3 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant