Repository not in active maintenance?

[Tehnix]

I see there hasn't been an update in quite a while, and wanted to reach out because I was considering taking over maintenance if you don't find you have time for this anymore. This way we can get it on stackage etc :)

Let me know your thoughts!

[tonyday567]

That would be great - I'm in the process of learning about core and many roads lead here. I can imagine a lot of documentation could go in the readme etc.

[Tehnix]

@tonyday567 You can now find it in stackage nightly. I've taken up keeping the stackage maintainer handle at least for now :)

It might be worth to taking over the package on hackage later on if no updates occur. I can see several PRs and issues that haven't been responded to. Especially since I can see that the package was originally authored by Don Stewart, and I think this just put it on hackage.

[flip111]

Hi guys. I'm trying to inspect some ghc core output. I'm not even sure what file i should generate. There are just so many possible flags. It would be good to have a tabular description for each flag with the following columns:

• flag
• which step in ghc process (numerical)
• possible next step (i guess some steps go back to previous steps)
• what the step does (optimization or something else)
• why use this flag? Is it useful for debugging your own program? Useful to debug GHC? Both? Right now i have no idea what are the most important flags and what to pay attention to.

Maybe some of this information could be obtained from here https://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler

Anyway i used these commands to get some files:

stack clean --full
/usr/bin/time stack build --force-dirty --ghc-options="-fforce-recomp -ddump-ds -ddump-prep -ddump-simpl -ddump-to-file -j4 -O2 -fexcess-precision -optc-O3 -optc-ffast-math -rtsopts=none -no-rtsopts-suggestions"

(Contains some more flags than which is really relevant to dumping core files)

The gave the following files:

• filename.dump-simple
• filename.dump-prep
• filename.dump-ds

in:

.stack-work/dist/x86_64-linux/Cabal-1.24.2.0/build/myProject/myProject-tmp/src

(stack was on lts-9.21 for this one)

So i noticed that ghc-core also uses the -ddump-simple flag.

I tried to run ghc-core filename.dump-simple because i guess ghc-core can handle this type of file. But i get file format not recognized; treating as linker script. So it would be nice to have some more readme for ghc-core too.

Hopefully somebody finds this helpful on how to generate intermediate source files with stack. From there i'm still in the dark about how to read these files.