#7933: JavaScript Cmm backend -------------------------------+-------------------------------------------- Reporter: bosu | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Resolution: | Keywords: Os: Unknown/Multiple | Architecture: Unknown/Multiple Failure: None/Unknown | Difficulty: Unknown Testcase: | Blockedby: Blocking: | Related: -------------------------------+-------------------------------------------- Changes (by igloo): * owner: bosu => * status: patch => new Comment: The native codegen, LLVM backend, unreg backend, and this JS codegen, all have an interface that is roughly of the form {{{ someCodeGen :: DynFlags -> FilePath -> Stream IO RawCmmGroup () -> IO () }}} which might suggest that we could make them separate packages, and have some sort of plugin system. However, I'm not sure if this would really buy us anything: A new backend is likely to need to alter `DynFlags` too, and may also need other changes around the compiler. I think most of the backends export some other functions too, although I don't know what for OTTOMH. My gut feeling is that it's too early to merge this into GHC: Let's wait a while and see which of the 3 JS approaches turns out to be the most fruitful. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7933#comment:13 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler