Re: [commit: ghc] wip/float-join-points: Wip on floating join points (128e4c1)

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

Re: [commit: ghc] wip/float-join-points: Wip on floating join points (128e4c1)

Joachim Breitner-2
Hi Simon,

Am Freitag, den 27.10.2017, 15:24 +0000 schrieb [hidden email]:
> commit 128e4c1ffa29f3dfade7128152c143cd601aaa3a
> Author: Simon Peyton Jones <[hidden email]>
> Date:   Fri Oct 27 16:20:24 2017 +0100
>     Wip on floating join points

do you expect to merge that soon, or can I land Exitification before
that? (I’m worried that I have to re-do a lot of performance analysis
if the Simplifier suddenly does new things to join points).

Blocking for Exitification is:
 * needs to land

   Or rather, I’d prefer if someone who understands the Simplifier
   better than I fixes it properly. See
   for bits that I am puzzled about.

 * I need to understand better why inlining join points in the final
   simplifier run regresses things.

   Unless you permit merging Exitification without final inlining
   even before we completely solve this mystery, on the grounds that
     - the nofib results say it’s the right thing to do and
     - there is a plausible theory (exit join points in unfolding
       enable optimizations in later modules in earlier phases).


Joachim Breitner
  [hidden email]

ghc-devs mailing list
[hidden email]

signature.asc (849 bytes) Download Attachment