Jeff Terrace
Jeff Terrace
Yeah, it was mainly developed as a proof of concept. It was very difficult to get it to compile, so trying to keep it maintained would be very difficult.
Yes, some other people are working on trying to update js.js to the latest version of Emscripten and LLVM.
No, but I have notified the two people who are working on it with this issue. I will ask them to post here.
If you have any in-progress commits, feel free to push them to a branch. I can help you with any blockers.
The second error looks troubling because I thought we hacked the entire JIT assembler out of the code that gets compiled. The first error is really confusing. Not sure where...
Do you have the updates in a branch somewhere I can check out?
I see your fork, but there are no new commits in there. Did you commit locally but forget to push?
Compiling now, but it takes a while.. I'll report back when I get a chance to try it out after it finishes.
Since the js.js API closely follows SpiderMonkey's JSAPI, a good starting point is to read this document to wrap your head around how the sandbox is interacted with: https://developer.mozilla.org/en-US/docs/SpiderMonkey/JSAPI_User_Guide Indeed,...
We could add additional architectures to the travis.yml file to try to repro: https://docs.travis-ci.com/user/multi-cpu-architectures/