You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
Main: JSException "RuntimeError: unreachable
at wasm-function[108]:0x6e91
at wasm-function[4070]:0xd77de
at wasm-function[4071]:0xd780b
at Scheduler.tick (file:///home/skull/tweag/asterius-alt/asterius/nofib/shootout/binary-trees/rts.scheduler.mjs:346:22)
at Immediate.<anonymous> (file:///home/skull/tweag/asterius-alt/asterius/nofib/shootout/binary-trees/rts.scheduler.mjs:381:29)
at processImmediate (internal/timers.js:456:21)"
After some tinkering I noticed that if I remove all invocations of GHC.Conc.par in the file, it executes as expected, so I think that this is the culprit.
To Reproduce
Download Main.hs from here, build it with Asterius, and execute using node:
Linking with --verbose-err gives a little more info:
Main: JSException "RuntimeError: barf: newSpark
at ExceptionHelper.barf (file:///home/skull/tweag/asterius-alt/asterius/nofib/shootout/binary-trees/rts.exception.mjs:147:13)
at barf (wasm-function[184]:0x9c55)
at Main_.Lr7z8_entry (wasm-function[108]:0x6eb7)
at scheduleTSO (wasm-function[4075]:0xd7aa5)
at scheduleTSO_wrapper (wasm-function[4076]:0xd7ad2)
at Scheduler.tick (file:///home/skull/tweag/asterius-alt/asterius/nofib/shootout/binary-trees/rts.scheduler.mjs:346:22)
at Immediate.<anonymous> (file:///home/skull/tweag/asterius-alt/asterius/nofib/shootout/binary-trees/rts.scheduler.mjs:381:29)
at processImmediate (internal/timers.js:456:21)"
Describe the bug
During the development of #639, I noticed that the nofib test
shootout/binary-trees
fails withAfter some tinkering I noticed that if I remove all invocations of
GHC.Conc.par
in the file, it executes as expected, so I think that this is the culprit.To Reproduce
Download
Main.hs
from here, build it with Asterius, and execute using node:Expected behavior
The program should execute without errors. The expected stdout can be found here.
Environment
The text was updated successfully, but these errors were encountered: