Mirror of the Glasgow Haskell Compiler. Patches are best submitted to GHC's Phabricator (https://phabricator.haskell.org/), bugs and feature-requests are best filed to GHC's Trac (https://ghc.haskell.org/trac/ghc), or sent to the mailing list (ghc-devs@haskell.org). First time contributors are encouraged to get started by just sending a Pull Req…
Haskell C Makefile Terra Logos C++ Other
Latest commit c0af206 Feb 27, 2017 @alanz alanz Explicitly capture whether a splice has a dollar prefix
A top-level splice can be written

    $splice

or

    splice

For accurate pretty-printing, and for ghc-exactprint, capture in the hsSyn AST
which variant was parsed.
Permalink
Failed to load latest commit information.
.arc-linters check-cpp.py: change rb'foo' to br'foo' for Python 3.2 compatibility Jan 20, 2017
bindisttest Rework CC/CC_STAGE0 handling in `configure.ac` Apr 16, 2016
compiler Explicitly capture whether a splice has a dollar prefix Feb 27, 2017
distrib Pass -no-pie to GCC Nov 11, 2016
docs Add -fspec-constr-keen Feb 27, 2017
driver Don't use the splitter on Darwin Jan 10, 2017
ghc Have --backpack complain if multiple files are passed. Feb 23, 2017
includes JSON profiler reports Feb 23, 2017
inplace Testsuite: suggest quoting $(TEST_HC) Oct 30, 2015
iserv fix build failure on Solaris caused by usage of --export-dynamic Oct 18, 2016
libffi-tarballs @ ec37a68 Update libffi-tarballs submodule to libffi 3.1 (re #10238) Dec 8, 2015
libffi Build system: temp solution for parallelisation bug (#11960) May 22, 2016
libraries tests: remove extra_files.py (#12223) Feb 26, 2017
mk build.mk: Add option for debug symbols Feb 21, 2017
nofib @ 3ac6f2d Bump nofib submodule Feb 18, 2017
rts rts: Usage message wibbles Feb 26, 2017
rules Set $1_$2_SplitSections in distdir-opts.mk not build-package.mk Feb 23, 2017
testsuite Explicitly capture whether a splice has a dollar prefix Feb 27, 2017
utils Add support for concurrent package db access and updates Feb 26, 2017
.arcconfig Reenable external-json linters Mar 29, 2016
.arclint Use python3 for linters Dec 23, 2016
.gitignore Remove very broad ignore. [ci skip] Feb 1, 2017
.gitmodules Turn libraries/integer-gmp/gmp/tarball into a submodule Jan 30, 2017
.mailmap Update .mailmap [skip ci] Feb 14, 2017
.travis.yml Travis: Add dependency on python3 Dec 2, 2016
ANNOUNCE ANNOUNCE: Mention powerpc code generator Jan 15, 2016
HACKING.md Make configure error out on missing ghc-tarballs on Windows Jul 30, 2015
INSTALL.md INSTALL.md: Mention -j and other wibbles Jan 14, 2016
LICENSE Reorganisation of the source tree Apr 7, 2006
MAKEHELP.md Fix links to building guides in MAKEHELP.md Jan 30, 2017
Makefile configure.ac: Remove checks for bug 9439 Aug 6, 2016
README.md README: Mention acceptability of pull requests Jan 31, 2017
Vagrantfile vagrant: move files around Jul 20, 2014
aclocal.m4 Typos and grammar in manual/comments Jan 23, 2017
boot Unset GREP_OPTIONS in build system Feb 9, 2016
config.guess Update config.{guess,sub} to GNU automake 1.14.1 Sep 16, 2014
config.sub Update config.{guess,sub} to GNU automake 1.14.1 Sep 16, 2014
configure.ac Rename compact to ghc-compact. Feb 26, 2017
ghc.mk build system: Persist CrossCompiling in binary distributions Feb 26, 2017
install-sh Update aux files `config.{guess,sub}` and `install-sh` Nov 7, 2013
packages Rename compact to ghc-compact. Feb 26, 2017
settings.in Testsuite: Skip failing tests on PowerPC 64-bit Dec 27, 2016
validate validate: Allow user to override Python interpreter Oct 17, 2016

README.md

The Glasgow Haskell Compiler

Build Status

This is the source tree for GHC, a compiler and interactive environment for the Haskell functional programming language.

For more information, visit GHC's web site.

Information for developers of GHC can be found on the GHC Trac.

Getting the Source

There are two ways to get a source tree:

  1. Download source tarballs

    Download the GHC source distribution:

      ghc-<version>-src.tar.bz2
    

    which contains GHC itself and the "boot" libraries.

  2. Check out the source code from git

    $ git clone --recursive git://git.haskell.org/ghc.git
    

    Note: cloning GHC from Github requires a special setup. See Getting a GHC repository from Github.

    See the GHC team's working conventions regarding how to contribute a patch to GHC. First time contributors are encouraged to get started by just sending a Pull Request.

Building & Installing

For full information on building GHC, see the GHC Building Guide. Here follows a summary - if you get into trouble, the Building Guide has all the answers.

Before building GHC you may need to install some other tools and libraries. See, Setting up your system for building GHC.

NB. In particular, you need GHC installed in order to build GHC, because the compiler is itself written in Haskell. You also need Happy, Alex, and Cabal. For instructions on how to port GHC to a new platform, see the GHC Building Guide.

For building library documentation, you'll need Haddock. To build the compiler documentation, you need Sphinx and Xelatex (only for PDF output).

Quick start: the following gives you a default build:

$ ./boot
$ ./configure
$ make         # can also say 'make -jX' for X number of jobs
$ make install

On Windows, you need an extra repository containing some build tools. These can be downloaded for you by configure. This only needs to be done once by running:

$ ./configure --enable-tarballs-autodownload

(NB: Do you have multiple cores? Be sure to tell that to make! This can save you hours of build time depending on your system configuration, and is almost always a win regardless of how many cores you have. As a simple rule, you should have about N+1 jobs, where N is the amount of cores you have.)

The ./boot step is only necessary if this is a tree checked out from git. For source distributions downloaded from GHC's web site, this step has already been performed.

These steps give you the default build, which includes everything optimised and built in various ways (eg. profiling libs are built). It can take a long time. To customise the build, see the file HACKING.md.

Filing bugs and feature requests

If you've encountered what you believe is a bug in GHC, or you'd like to propose a feature request, please let us know! Submit a ticket in our bug tracker and we'll be sure to look into it. Remember: Filing a bug is the best way to make sure your issue isn't lost over time, so please feel free.

If you're an active user of GHC, you may also be interested in joining the glasgow-haskell-users mailing list, where developers and GHC users discuss various topics and hang out.

Hacking & Developing GHC

Once you've filed a bug, maybe you'd like to fix it yourself? That would be great, and we'd surely love your company! If you're looking to hack on GHC, check out the guidelines in the HACKING.md file in this directory - they'll get you up to speed quickly.

Contributors & Acknowledgements

GHC in its current form wouldn't exist without the hard work of its many contributors. Over time, it has grown to include the efforts and research of many institutions, highly talented people, and groups from around the world. We'd like to thank them all, and invite you to join!