|Version 1 (modified by simonpj, 4 years ago) (diff)|
Profiling GHC itself
If GHC itself is running too slowly, you can profile the compiler itself. The way to do this is to add
to your build.mk file. This is more robust than trying things like GhcStage2HcOpts += -prof because there are several things to do: first we build the ghc library, then we build the ghc program, linked against the library.
Once you've done this, you should be able to run GHC to generate time and space profiles. For exmaple:
ghc +RTS -p -RTS