Re: Inhibiting the specialiser?

2017-09-14 Thread Harendra Kumar
As per the GHC manual, it should be -fno-specialise for disabling all
specialization, and -fno-cross-module-specialise for disabling only the
specialization of imported INLINABLE functions. Both of these flags are
"on" when using -O and -O2.

-harendra

On 15 September 2017 at 07:15, Conal Elliott  wrote:

> Is there a GHC flag for inhibiting the specializer (but not all
> optimizations)? I'm seeing huge output from the Specialise phase killed at
> 4GB and growing. The output starts as follows:
>
> Result size of Specialise
>   = {terms: 29,639, types: 10,921,552, coercions: 4,425,185}
>
> Sounds like a lot to me. Is it?. I get this behavior with -O2 and with -O.
>
> -- Conal
>
> ___
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
>
>
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users


Inhibiting the specialiser?

2017-09-14 Thread Conal Elliott
Is there a GHC flag for inhibiting the specializer (but not all
optimizations)? I'm seeing huge output from the Specialise phase killed at
4GB and growing. The output starts as follows:

Result size of Specialise
  = {terms: 29,639, types: 10,921,552, coercions: 4,425,185}

Sounds like a lot to me. Is it?. I get this behavior with -O2 and with -O.

-- Conal
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users