overdrigzed:
As far as I know, hs-plugins works by taking an expression, writing it to a file, calling GHC to parse it, transform it to Core, optimise it, transform it to STG, optimise it, transform it to C--, optimise it, transform it to ANSI C, optimise it, pass it to GCC, compile it, link it, and *then* using the GHC runtime linker to load the generated object code into memory, type-check it, and, finally, execute it.
Don't forget the Evil Mangler, which optimises the compiled assembly! [1]http://www.cse.unsw.edu.au/~chak/haskell/ghc/comm/the-bea st/mangler.html
Close, but hs-plugins uses -fasm, so its: File -> Core -> STG -> C-- -> ASM -> ld -> link -> typecheck -> run. Avoiding mangler and gcc. -- Don