[ ghc-Feature Requests-1097471 ] amd64: adjustor creation not supported

[SourceForge.net]

Feature Requests item #1097471, was opened at 2005-01-06 21:55
Message generated for change (Comment added) made by aanno
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358032&aid=1097471&group_id=8032

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Thomas Pasch (aanno)
Assigned to: Nobody/Anonymous (nobody)
Summary: amd64: adjustor creation not supported

Initial Comment:
Hello, 
 
when trying to use wxhaskell on ghc-6.2.2 on an amd64 
(unregistered gentoo build) the following happend: 
 
$ ./a.out  
a.out: internal error: adjustor creation not supported on  
this platform  
    Please report this as a bug to  
glasgow-haskell-bugs at haskell.org,  
    or http://www.sourceforge.net/projects/ghc/  
  
I'm not sure if this is a bug because amd64 is not 
officially supported. 

----------------------------------------------------------------------

>Comment By: Thomas Pasch (aanno)
Date: 2005-01-20 21:20

Message:
Logged In: YES 
user_id=349837

OK, I will have a try on this. I sort of understand 
x86 and x86_64 abi at the moment. There is only 
one question left at the moment: After I jump to  
StgFunPtr (a StgFun?) what will happen? Is this 
(a) a normal C land function that will require  
its argument (StgStablePtr hptr) as a 1st argument 
of the "universal" calling convention OR (b) some 
other kind of magic (from what source code?)  
that will pop its argument from the stack? 
 
Any answer would be appreciated. 
 
aanno 

----------------------------------------------------------------------

Comment By: Gour (ggd)
Date: 2005-01-08 11:34

Message:
Logged In: YES 
user_id=728695

Hi! 
 
Just to add it's important issue for me since it affects the general 
gui-availability for Haskell language on amd64 platform since gtk2hs 
bindings also depend on it. 
 
Pls. raise this priority a little bit - amd64 is really a very 'natural' platform 
for Haskell :-) 
 
Sincerely, 
Gour 
 

----------------------------------------------------------------------

Comment By: Wolfgang Thaller (wthaller)
Date: 2005-01-06 22:48

Message:
Logged In: YES 
user_id=566359

Yes, this is just a "missing feature". A small piece of platform specific 
code (<50 lines) is required to get foreign import "wrapper" declarations 
to work, and wxhaskell uses them a lot.

A volunteer who wants to fix this would need enough knowledge about 
assembly language in general to really understand a calling convention 
(literature on amd64's particular calling convention is available 
somewhere). Most of the amd64-specific details can be picked up on the 
job.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358032&aid=1097471&group_id=8032