Hi Andy,
> I think I've made most of the changes in the mangler to get
> it to work with
> gcc 2.95.2 on HP-UX (only about 6 lines). One question
> however, the *_info
> is inverted and placed in the code section I presume so that
> its address is
> identical to the entry point for an associated function. Is
> it only for the
> *_entry of a function that this adjacency matters? I'm
> interested to know as
> I'd like to know what potentially needs to be in the same
> subspace as the
> info table, as the linker reserves the right to reorder subspaces.
Info tables (*_info) need to be right up against their corresponding
entry code (*_entry) for closures, or return code (*_ret) for return
addresses. Vector tables (*_vtbl) can float around in relation to their
code (*_alt), but they have to be inverted too.
> I've got a couple of small programs working, and without the
> need for my
> original procedure label workaround. Once you let me know the
> above, I'll
> see if I can get GHC to build itself, and if that works, I'll
> let you know
> my changes to the mangler.
Sounds great! I think we owe you a beer or two :)
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
