Repository : ssh://darcs.haskell.org//srv/darcs/ghc

On branch  : newcg

http://hackage.haskell.org/trac/ghc/changeset/8071691488802dbe5e67b5a47206f564a2d0bcbf

>---------------------------------------------------------------

commit 8071691488802dbe5e67b5a47206f564a2d0bcbf
Author: Simon Marlow <marlo...@gmail.com>
Date:   Sun Feb 19 13:04:34 2012 +0000

    remove some obsolete notes

>---------------------------------------------------------------

 compiler/cmm/cmm-notes |   14 --------------
 1 files changed, 0 insertions(+), 14 deletions(-)

diff --git a/compiler/cmm/cmm-notes b/compiler/cmm/cmm-notes
index bbad34c..9df5cb0 100644
--- a/compiler/cmm/cmm-notes
+++ b/compiler/cmm/cmm-notes
@@ -119,10 +119,6 @@ Things to do:
  - NB that CmmProcPoint line 283 has a hack that works around a GADT-related
    bug in 6.10.
 
- - SDM (2010-02-26) can we remove the Foreign constructor from Convention?
-   Reason: we never generate code for a function with the Foreign
-   calling convention, and the code for calling foreign calls is generated
-
  - AsmCodeGen has a generic Cmm optimiser; move this into new pipeline
    EZY (2011-04-16): The mini-inliner has been generalized and ported,
    but the constant folding and other optimizations need to still be
@@ -151,16 +147,6 @@ Things to do:
 
  - Top-level SRT threading is a bit ugly
 
- - Add type/newtype for CmmModule = [CmmGroup]    -- A module
-                        CmmGroup  = [CmmTop]      -- A .o file
-                        CmmTop    = Proc | Data   -- A procedure or data
-
- - This is a *change*: currently a CmmGroup is one function's-worth of code
-   regardless of SplitObjs.   Question: can we *always* generate M.o if there
-   is just one element in the list (rather than M/M1.o, M/M2.o etc)
-
-   One SRT per group.
-
  - See "CAFs" below; we want to totally refactor the way SRTs are calculated
 
  - Pull out Areas into its own module



_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to