#4288: Poor -fspec-constr-count=n warning messages
---------------------------------+------------------------------------------
Reporter: igloo | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.14.2
Component: Compiler | Version: 6.13
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
The attached file, compiled with
{{{
ghc -O2 -fspec-constr-count=5 -c q.hs
}}}
gives a number of messages like
{{{
SpecConstr
Function `$j_X1BO{v} [lid]'
has one call pattern, but the limit is 0
Use -fspec-constr-count=n to set the bound
Use -dppr-debug to see specialisations
SpecConstr
Function `$j_X1BR{v} [lid]'
has two call patterns, but the limit is 1
Use -fspec-constr-count=n to set the bound
Use -dppr-debug to see specialisations
}}}
Note that the limit doesn't match the `spec-constr-count` we set.
The "limit" given is `sc_count`, but `decreaseSpecCount` changes
`sc_count` from its default of `specConstrCount dflags`. However, if this
was fixed then we would get even stranger messages like
{{{
has two call patterns, but the limit is 5
}}}
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4288>
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
