[GHC] #2241: unknown epilogue mangling, WARNING: Epilogue junk

[GHC]

#2241: unknown epilogue mangling, WARNING: Epilogue junk
----------------------+-----------------------------------------------------
 Reporter:  igloo     |          Owner:             
     Type:  bug       |         Status:  closed     
 Priority:  high      |      Milestone:  6.10 branch
Component:  Compiler  |        Version:  6.9        
 Severity:  normal    |     Resolution:  fixed      
 Keywords:            |     Difficulty:  Unknown    
 Testcase:            |   Architecture:  Unknown    
       Os:  Unknown   |  
----------------------+-----------------------------------------------------
Changes (by igloo):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 This was fixed by
 {{{
 Mon May 12 12:06:43 BST 2008  Simon Marlow <simonmar at microsoft.com>
   * Fixes to via-C prototype generation (FIX BUILD on Windows)

   Previously we declared all external labels with type StgWord[],
   because the same label might be used at different types in the same
   file, e.g. if there are multiple foreign import declarations for the
   same function.  However, we have to declare called functions with the
   right type on Windows, because this is the only way to make the
   compiler add the appropriate '@n' suffix for stdcall functions.

   Related to this is the reason we were getting mangler complaints
   (epilogue mangling) when compiling the RTS with -fvia-C.  The function
   barf() doesn't return, but we had lost that information by declaring
   our own prototypes, and so gcc was generating extra code after the
   call to barf().

   For more details see
 http://hackage.haskell.org/trac/ghc/wiki/Commentary/Compiler/Backends/PprC
 }}}

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2241#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler