Welcome to the GHC Developer Wiki

This is the home for GHC developers, one place for all the resources related to developing GHC. If you're only interested in using GHC, then you probably want  The GHC home page instead.

Please help us improve the information here. You can easily do this by editing the wiki directly. Just log in as user guest with password guest. The "Help/Guide" link at the top of every page gives a good description of the markup language etc.

For a complete list of local wiki pages, see TitleIndex.

Release cycle status

• 6.4.2 is now in release candidate mode. The release is due in approximately 2 weeks (around 10 April). Please test the nightly snapshots.

• The STABLE branch is ghc-6-4-branch in CVS. Bugfixes (only) are being merged in from the HEAD. We are using CVS for this branch, the next STABLE branch will be a darcs repository.

• The HEAD is in darcs now (see below). We will be branching the HEAD for version 6.6 at some point, still to be decided, but probably around Spring 2006.

Downloading snapshots

• Download snapshots here. This link also gets you to a typeset user manual for the current snapshot.

The bug tracker

• Create a new bug report
• Create a new task
• Create a new feature request

• View open bug reports
• View tasks
• View feature requests

• View my tickets

• View tickets scheduled for 6.4.2
• View tickets scheduled for 6.6

The Code

Our source code is kept in a collection of  darcs repositories.

• Getting the sources

We recently transitioned from using CVS as our revision control system to darcs. The darcs repositories have full history, but in case you need to look at the CVS trees:

•  Browse the CVS repository online
• Accessing the CVS repository

Getting Started

How to get started with hacking on GHC:

• Pick an easy bug report or task to work on
• Grab the latest sources
•  Set up your build tree
• Useful information about GHC's architecture is in the  commentary
• Hack away... ask questions on  the cvs-ghc mailing list
• Submit patches back, using darcs send is the recommended way.

Mailing lists

GHC developers hang out on the  cvs-ghc mailing list. This list also receives the following:

• checkins on the main ghc repository
• patches sent by darcs send
• nightly build reports

The traffic level varies quite a bit depending on how much activity there is.

Checkins for packages are reported on the  cvs-libraries mailing list. To get mail from all the cvs-* lists, subscribe to the  cvs-all mailing list (but don't post there, please).

Developer Documentation

• The Building Guide: Information on how to build GHC from sources and port GHC to a new platform.
• DebuggingGhcCrashes: how to use gdb to debug a crash in GHC-compiled code.
• AddingNewPrimitiveOperations: How to add new primitive operations to GHC Haskell.
•  The GHC Commentary: Information on the internals of GHC, in various states of up-to-dateness.
• GhcPapers: papers and pointers to other documents that relate to the inner workings of GHC.

Contributors

• The GHC Team