how to check for performance regressions caused by ghc hacking?

[Isaac Dupree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While working on making GHC more compilable by other compilers, and
seeing some code that would be nicer-looking refactored anyway: I want
to change the code, but I'm afraid I'll make GHC's speed worse (these
are critical things like FastString and FiniteMap).  I could send my
patches to the list, but would the reviewers know any better than me
just by looking at it? (I'm much better at mental
strictness/sharing/etc. analysis than I used to be, at least) ... so,
what's a good way to observe the overall speed that a GHC compiles
things at? (Is or should this be somewhere in the GHC Commentary?  I
didn't find anything relevant there)


Isaac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYznFHgcxvIWYTTURAiXbAJsEBstvLehNg68VK6i+1q9FdxhjygCgi6oH
EfdDIUMIZR12EwVxgUagvzg=
=iM3D
-----END PGP SIGNATURE-----