1. 18 Jun, 2010 2 commits
    • Simon Marlow's avatar
      comment typo · 368a69a5
      Simon Marlow authored
    • dterei's avatar
      Add support of TNTC to llvm backend · 24a3fee9
      dterei authored
      We do this through a gnu as feature called subsections,
      where you can put data/code into a numbered subsection
      and those subsections will be joined together in descending
      order by gas at compile time.
  2. 17 Jun, 2010 6 commits
  3. 16 Jun, 2010 6 commits
  4. 15 Jun, 2010 1 commit
  5. 04 Jun, 2010 1 commit
  6. 27 May, 2010 1 commit
  7. 09 May, 2010 1 commit
  8. 07 May, 2010 1 commit
  9. 15 Jun, 2010 9 commits
  10. 14 Jun, 2010 3 commits
  11. 01 Jun, 2010 1 commit
  12. 31 May, 2010 1 commit
  13. 14 Jun, 2010 1 commit
    • simonpj@microsoft.com's avatar
      Gruesome fix in CorePrep to fix embarassing Trac #4121 · 31c7568b
      simonpj@microsoft.com authored
      This is a long-lurking bug that has been flushed into
      the open by other arity-related changes.  There's a
      long comment
           Note [CafInfo and floating]
      to explain.  
      I really hate the contortions we have to do through to keep correct
      CafRef information on top-level binders.  The Right Thing, I believe,
      is to compute CAF and arity information later, and merge it into the
      interface-file information when the latter is generated.
      But for now, this hackily fixes the problem.
  14. 31 May, 2010 2 commits
    • simonpj@microsoft.com's avatar
      Fix a bug in CorePrep that meant output invariants not satisfied · 919509ab
      simonpj@microsoft.com authored
      In cpePair I did things in the wrong order so that something that
      should have been a CprRhs wasn't.  Result: a crash in CoreToStg.
      Fix is easy, and I added more informative type signatures too.
    • simonpj@microsoft.com's avatar
      Robustify the treatement of DFunUnfolding · a90dc390
      simonpj@microsoft.com authored
      See Note [DFun unfoldings] in CoreSyn.  The issue here is that 
      you can't tell how many dictionary arguments a DFun needs just
      from looking at the Arity of the DFun Id: if the dictionary is
      represented by a newtype the arity might include the dictionary
      and value arguments of the (single) method.
      So we need to record the number of arguments need by the DFun
      in the DFunUnfolding itself.  Details in 
         Note [DFun unfoldings] in CoreSyn
  15. 14 Jun, 2010 2 commits
  16. 13 Jun, 2010 2 commits