Inhibiting the specialiser?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Inhibiting the specialiser?

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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Reply | Threaded
Open this post in threaded view
|

Re: Inhibiting the specialiser?

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 <[hidden email]> 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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users



_______________________________________________
Glasgow-haskell-users mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Reply | Threaded
Open this post in threaded view
|

RE: Inhibiting the specialiser?

Haskell - Glasgow-haskell-users mailing list
In reply to this post by Conal Elliott

Did you try -fno-specialise?

 

From: Glasgow-haskell-users [mailto:[hidden email]] On Behalf Of Conal Elliott
Sent: 15 September 2017 02:45
To: [hidden email]
Subject: Inhibiting the specialiser?

 

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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Reply | Threaded
Open this post in threaded view
|

Re: Inhibiting the specialiser?

Conal Elliott
In reply to this post by Harendra Kumar
Thanks! Exactly what I was looking for.

On Thu, Sep 14, 2017 at 8:30 PM, Harendra Kumar <[hidden email]> wrote:
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 <[hidden email]> 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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users




_______________________________________________
Glasgow-haskell-users mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Reply | Threaded
Open this post in threaded view
|

Re: Inhibiting the specialiser?

Conal Elliott
In reply to this post by Haskell - Glasgow-haskell-users mailing list
Thanks. I somehow didn't notice that flag.

On Fri, Sep 15, 2017 at 3:23 AM, Simon Peyton Jones <[hidden email]> wrote:

Did you try -fno-specialise?

 

From: Glasgow-haskell-users [mailto:[hidden email]] On Behalf Of Conal Elliott
Sent: 15 September 2017 02:45
To: [hidden email]
Subject: Inhibiting the specialiser?

 

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
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users