David van Balen

I ran into the same issue, on windows with a stack project (Accelerate). Example error: ``` 2020-01-21 14:49:10.6271858 [ThreadId 31] - Scheduler thread exited unexpectedly: loadObj "C:\\Users\\dpvan\\AppData\\Local\\Temp\\ghc9852_0\\ghc_81.o": failed ``` HIE...

By using a GHC version (8.4.4) that I had not compiled Accelerate with before, I managed to get HIE work again (compiled hie for 8.4.4, changed the stack.yaml for Accelerate...

As far as I can see (but it's late, I'll check again tomorrow) this behaviour can't be supported by Accelerate. You can 'compose' Acc programs using `run` and `use`, but...

Looking again, perhaps it is better to go with the `Solo` route: The example in the haddoc is not run by the doctest, and trying myself I get a different...

This version now uses `Solo`, and now this example works as expected: ``` let convolve5x1 :: [A.Exp Double] -> A.Stencil5x1 Double -> A.Exp Double convolve5x1 kernel (A.Solo (a,b,c,d,e)) = Prelude.sum...

I changed `Solo` to `newtype Unary a = a`, because GHC.Tuple doesn't export Solo for GHC

Will update this to match https://github.com/AccelerateHS/accelerate/pull/512 next tutorial or procrastination session :)

@tmcdonell `warpRegAllocUnit` is not in the tables, but since 2.0 (when regAllocationStyle became Warp) it's always been equal to `regAllocUnit`. Is it safe to assume that these two are also...

That error means that _something_ went _wrong_ during sharing recovery. As the error indicates, the cause is often a user expressing nested data parallelism in a way we do not...