This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 04 Oct, 2006 12 commits
    •'s avatar
      Fix comment in RdrName · 7086e46a authored
    •'s avatar
      Improve unboxing of strict fields · 08a681f1 authored
      Note [Recursive unboxing]
      Be careful not to try to unbox this!
      	data T = MkT !T Int
      But it's the *argument* type that matters. This is fine:
      	data S = MkS S !Int
      because Int is non-recursive.
      Before this patch, we were only doing the unboxing if the *parent*
      data type was non-recursive (eg that meant S was not unboxed), but
      that is over-conservative. 
      This showed up with indexed data types (thanks to Roman for finding it)
      because indexed data types are conservatively regarded as always recursive.
    •'s avatar
      Remove redundant dump · 365ab3da authored
    •'s avatar
      Trim imports · eb1c4917 authored
    •'s avatar
      Improve liberate-case to take account of coercions · 21174275 authored
      Note [Scrutinee with cast]
      Consider this:
          f = \ t -> case (v `cast` co) of
      	         V a b -> a : f t
      Exactly the same optimistaion (unrolling one call to f) will work here, 
      despite the cast.  See mk_alt_env in the Case branch of libCase.
      This patch does the job.  For a change, it was really easy.
    •'s avatar
    •'s avatar
      Remove ILX from the GHC altogether (although I left the source file IlxGen in... · fb38b8ba authored
      Remove ILX from the GHC altogether (although I left the source file IlxGen in case anyone wants to see it)
    •'s avatar
      -frule-check is not a static flag · 7eb7a2d9 authored
    •'s avatar
      Tidy tyvar OccNames in TcTyClDecl · 4b922606 authored
      We want the universal and existential tyvars of a data constructor to
      have distinct OccNames.  It's confusing if they don't (in error messages,
      for example), and with the current way of generating IfaceSyn, it actally
      generates bogus interface files.  (Which bit Roman.)
      When IfaceSyn is full of Names, this won't matter so much, but it still
      seems cleaner.
      This patch adds a 'tidy' step to the generation of DataCon type 
      variables in TcTyClDecls.tcResultType 
    •'s avatar
      Improve pretty printing slightly · 1f315eba authored
    •'s avatar
      Second bite at the rules-only idea · a35f75aa authored
      This is part 2 of the patch that improved the interaction of RULES and
      recursion.  It's vital that all Ids that may be referred to from later in
      the module are marked 'IAmALoopBreaker' because otherwise we may do
      postInlineUnconditionally, and lose the binding altogether. 
      So I've added a boolean rules-only flag to IAmALoopBreaker.  Now we can
      do inlining for rules-only loop-breakers. 
    •'s avatar
      Eliminate case-of-cast · 0477b389 authored
      Note [Case of cast]
      Consider 	case (v `cast` co) of x { I# ->
      		... (case (v `cast` co) of {...}) ...
      We'd like to eliminate the inner case.  We can get this neatly by 
      arranging that inside the outer case we add the unfolding
      	v |-> x `cast` (sym co)
      to v.  Then we should inline v at the inner case, cancel the casts, 
      and away we go
      This patch does the job, fixing a performance hole reported by Roman.
  2. 03 Oct, 2006 6 commits
    • Ian Lynagh's avatar
      Fixes for the porting process for 6.6 · 08f6d461
      Ian Lynagh authored
    •'s avatar
      Make recursion and RULES interact better · c248518f authored
      See Trac #683
      This patch improves the interaction of recursion and RULES; at least I
      hope it does.   The problem was that a RULE was being treated uniformly like
      an "extra RHS". This worked badly when you have a non-recursive definition
      that is made recursive only by RULE.
      This patch maeks the occurrence analyser know whether a binder is referred to
      only from RULES (the RulesOnly constructor in OccInfo).  Then we can ignore
      such edges when deciding on the order of bindings in a letrec, and when
      setting the LoopBreaker flag.
      The remaining potential problem is this:
      	rec{ f = ...g...
      	   ; g = ...f...
      	     RULE g True = ...
      The RULE for g may not be visible in f's rhs.  This is fixable, but not
    •'s avatar
      Warning police only · f297deab authored
    •'s avatar
      Fix scoped type variables for expression type signatures · 9da46390 authored
      I had forgotten to bring scoped type variables into scope at an expression
      type signature, such as
      	e :: forall s. <type>
      where 's' should scope over the expression e.
      Like everything to do with scoped type variables, fixing this took an 
      unreasonable amount of work.  I'm sure there must be a better way to 
      achitect this!
      I updated the user manual too.
      A test is tc213.
      It would be good to push this into 6.6.1
    •'s avatar
      Trim imports · 1bf36305 authored
    •'s avatar
      Add error check for operators in types · 7fbb69b2 authored
      Fixes Trac #919
  3. 27 Jul, 2006 1 commit
  4. 01 Oct, 2006 1 commit
  5. 29 Sep, 2006 15 commits
  6. 28 Sep, 2006 5 commits