> Here's the ticket:
>
> http://hackage.haskell.org/trac/ghc/ticket/2917
>
> Lennart's patch added allocaBytesAligned to Foreign.Marshal.Alloc, but we'll
> have to do a library proposal to add that.
>
> If you can reproduce the assertion failure, please submit a bug report.
Unfortunately this asse
On 03/06/2010 07:29, Evan Laforge wrote:
On Sun, May 30, 2010 at 5:15 PM, Antoine Latter wrote:
Hi GHC,
Is there a reason that Foreign.Marshall.Array.allocaArray calls into
allocaBytes instead of allocaBytesAligned? Since alloca needs the
alignment, wouldn't allocaArray also need it?
I'm not
On Sun, May 30, 2010 at 5:15 PM, Antoine Latter wrote:
> Hi GHC,
>
> Is there a reason that Foreign.Marshall.Array.allocaArray calls into
> allocaBytes instead of allocaBytesAligned? Since alloca needs the
> alignment, wouldn't allocaArray also need it?
>
> I'm not too up on how memory access is s
Hi GHC,
Is there a reason that Foreign.Marshall.Array.allocaArray calls into
allocaBytes instead of allocaBytesAligned? Since alloca needs the
alignment, wouldn't allocaArray also need it?
I'm not too up on how memory access is supposed to work, it was just
something that jump out at me.
Thanks,
