#4288: Poor -fspec-constr-count=n warning messages
---------------------------------+------------------------------------------
    Reporter:  igloo             |        Owner:              
        Type:  bug               |       Status:  new         
    Priority:  normal            |    Milestone:  7.0.2       
   Component:  Compiler          |      Version:  6.13        
    Keywords:                    |     Testcase:              
   Blockedby:                    |   Difficulty:              
          Os:  Unknown/Multiple  |     Blocking:              
Architecture:  Unknown/Multiple  |      Failure:  None/Unknown
---------------------------------+------------------------------------------

Comment(by simonpj):

 SimonM says

 > spec-constr-count decreases for nested specialisations. For instance,
 > if spec-constr-count is 6 and SpecConstr generates 2 specialisations
 > for a function foo, then spec-constr-count will be 3 for all functions
 > nested in foo. You can turn it off completely with
 > -fno-spec-constr-count.

 The messages are a bit counter-intuitive though - I encountered this
 recently too, and was baffled by the fact that the suggested flag, -fspec-
 constr-count, didn't seem to have any effect.

 Also, these messages should be clearly labelled as warnings, and there
 should be a way to disable them (I realise they're being generated by the
 SpecConstr pass and we don't normally generate warnings beyond the
 desugarer, but still.)

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4288#comment:5>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler

_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to