"static_wrapper" imports in the FFI

Iavor Diatchki iavor.diatchki at gmail.com
Tue Mar 16 20:01:32 EDT 2010

Optionally disabling executable heap blocks would be a separate patch.
 As far as I know, the only reason that the heap is executable is to
support the adjustor thunks used to implement "wrapper" imports.  The
"static_wrapper" patch provides a way to install Haskell callbacks in
many C libraries without the need for adjustor thunks.

On Tue, Mar 16, 2010 at 4:47 PM, Isaac Dupree
<ml at isaac.cedarswampstudios.org> wrote:
> On 03/16/10 19:38, Iavor Diatchki wrote:
>> The fact that, at present, all GHC-compiled programs require an
>> executable data segment is a fairly significant problem.
>> ...
>> I thought of implementing the feature as a preprocessor but it did not
>> seem very easy to do because we need to parse Haskell types.
> Something doesn't add up for me here.  If *all* GHC-compiled programs
> require an executable data segment, then how could a preprocessor possibly
> remedy this problem? (and likewise, how does the static_wrapper patch do
> so...)
> -Isaac
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

More information about the Glasgow-haskell-users mailing list