Work towards getting NodeJS running #161
Conversation
fwsGonzo
force-pushed
the
get_node_working
branch
from
79236b0
to
03fd25c
Compare
fwsGonzo
force-pushed
the
get_node_working
branch
from
03fd25c
to
f77c5d6
Compare
fwsGonzo
force-pushed
the
get_node_working
branch
3 times, most recently
from
1fcf325
to
1b63ec5
Compare
fwsGonzo
force-pushed
the
get_node_working
branch
from
1b63ec5
to
372e850
Compare
fwsGonzo
force-pushed
the
master
branch
3 times, most recently
from
9ff255f
to
58ad4f4
Compare
|
What is blocking this? |
|
futex emulation is very minimal in libriscv, which presents problems when there is complex thread-synchronization schemes The problem might be small, or big. No way to know without discovering what it is. |
|
This PR is a piece-wise solution to this PR, where v8 is now fully functional inside the sandbox, with Isolates, JIT-compilation and WebAssembly modules |
|
Task complete? |
|
No, now comes the second part where I have to try to see if NodeJS even makes sense. We'll see. Hopefully it doesn't use threading extensively, or there's a switch to disable it. |
|
Added improved Futex facility emulation: #199 It's aborting on something still, but hopefully I got a lot further on the startup process. I can use strace on the emulator to see most of what's happening, but for the next abort, likely remote GDB is needed. |
|
This PR has been superseded by #202 |
No description provided.