Opened 3 years ago

Closed 3 years ago

#8588 closed bug (invalid)

ForeignImport coercion evaluated before typechecking

Reported by: zcourts Owned by:
Priority: normal Milestone:
Component: Compiler Version: 7.6.3
Keywords: Cc:
Operating System: Windows Architecture: x86_64 (amd64)
Type of failure: Other Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


I'm fairly new to Haskell by all accounts this could have been caused by me doing something silly. Following the real world haskell book's directions on the FFI resulted in:

"Multiple markers at this line: - buildwrapper.exe: panic! (the 'impossible' happened) (GHC version 7.6.3 for i386-unknown-mingw32): ForeignImport coercion evaluated before typechecking Please report this as a GHC bug: - 16 changed lines"

I went to the Haskell Wiki to try an example from there to see if the RWH e.g. was just out dated. All examples I've come across causes this error inc. those at and reading FFI section didn't help.

The current failing code is

{-# LANGUAGE ForeignFunctionInterface #-}
module Events.CEvent where
import Prelude hiding (sin)
import Foreign.C -- get the C types
import Foreign.Ptr (Ptr,nullPtr)
-- pure function
foreign import ccall "sin" c_sin :: CDouble -> CDouble
sin :: Double -> Double
sin d = realToFrac (c_sin (realToFrac d))
-- impure function
foreign import ccall "time" c_time :: Ptr a -> IO CTime
getTime :: IO CTime
getTime = c_time nullPtr   

I've also tried this which causes the same error

{-# LANGUAGE ForeignFunctionInterface #-} 

module Events.Event2 where
import Foreign
import Foreign.C.Types

foreign import ccall "math.h sin"
     c_sin :: CDouble -> CDouble

Change History (1)

comment:1 Changed 3 years ago by zcourts

Resolution: invalid
Status: newclosed

As usual stuff doesn't become obvious until after you've made a fool of yourself on the NET. The one thing I hadn't tried was building from the terminal. Doing so everything builds and links fine and I'm able to execute the C function using ghci.

I'm using so it must be a bug in the BuildWrapper it's using

Note: See TracTickets for help on using tickets.