[GHC] #1373: Allow Access to generated STG from the GHC API

[GHC]

#1373: Allow Access to generated STG from the GHC API
--------------------------------+-------------------------------------------
    Reporter:  guest            |        Owner:         
        Type:  feature request  |       Status:  new    
    Priority:  normal           |    Milestone:         
   Component:  GHC API          |      Version:  6.6.1  
    Severity:  minor            |   Resolution:         
    Keywords:  STG              |   Difficulty:  Unknown
          Os:  Unknown          |     Testcase:         
Architecture:  Unknown          |  
--------------------------------+-------------------------------------------
Comment (by ekmett at gmail.com):

 Actually, I looked there first, but core is (by definition) a bit farther
 from the target language than STG.

 The reason STG is such a big win as a starting point to for generating
 javascript is all the work has already been done. Closures have been
 converted, all variables needed to execute each closure are named right
 there at the binding, so they can be transformed syntactically into
 arguments for the constructor once translated. Its all over but for a
 dozen or so transformation rules and a huge investment in writing primops.
 A simple javascript conversion can just transform the variables from the
 environment into fields on an object or array.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1373>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
-------------- next part --------------
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs at haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs