Re: Segfault when using integer-simple

On 2013-06-17 14:16, Stephen Paul Weber wrote: > Somebody claiming to be CJ van den Berg wrote: >> I don’t use integer-simple in my Android cross-compiler builds because I >> ran into problems. Possibly the same problem as you. I never did >> investigate any further though because it seemed like in

Re: Segfault when using integer-simple

Somebody claiming to be CJ van den Berg wrote: I don’t use integer-simple in my Android cross-compiler builds because I ran into problems. Possibly the same problem as you. I never did investigate any further though because it seemed like integer-gmp was the way to go for acceptable performance

Re: Segfault when using integer-simple

On 2013-06-16 22:33, Stephen Paul Weber wrote: > Somebody claiming to be Carter Schonwald wrote: >> Could you open a ticket on trac for this issue? Also have you tried to >> reproduce it on other architectures? > > Done: > > I have just now tes

Re: Segfault when using integer-simple

Somebody claiming to be Carter Schonwald wrote: Could you open a ticket on trac for this issue? Also have you tried to reproduce it on other architectures? Done: I have just now tested on native linux-i486, but nothing else yet. I tried to b

Re: Segfault when using integer-simple

Could you open a ticket on trac for this issue? Also have you tried to reproduce it on other architectures? On Saturday, June 15, 2013, Stephen Paul Weber wrote: > This may not be integer-simple, but that's my immediate suspicion. The > following two programs crash with SIGSEGV and core dump wh

Segfault when using integer-simple

This may not be integer-simple, but that's my immediate suspicion. The following two programs crash with SIGSEGV and core dump when run on my BB10 device after being cross-compiled with my GHC-to-QNXNTO-ARM cross-compiling GHC: module Main (main) where import Data.Bits import Data.ByteStrin