Call Arity, oneShot or both

[Joachim Breitner]

Hi,

Am Dienstag, den 28.10.2014, 15:45 +0100 schrieb Joachim Breitner:

> Also your suggestion to investigate fft2 was good: Turns out iterateFB
> would never inline, which defeats the purpose. With that fixed (just
> pushed to master) I expect Call Arity to handle the case in fft2 as
> well; well’ll see when the benchmarks finish.

indeed. So nofib gives no hard evidence that oneShot does any good (nor
does it do any harm).¹

But since it is plausible that there are cases out there where it might
help, even if just a little, we could go forward  –unless the
implementation becomes ugly. 

It also seems that the OS=Once flag survives most transformations just
fine; I had to add it to the list of IdInfo flags that make it through
TidyCore, though. Serializing and reading it from the interface was also
quite smooth.

I think I can prepare a differential revision soon. After writing some
Notes :-)

Greetings,
Joachim

¹ We need more benchmarks.

-- 
Joachim “nomeata” Breitner
  mail at joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nomeata at joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nomeata at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20141028/db6d8201/attachment.sig>