Skip to content
Mirror of ghc repository. DO NOT SUBMIT PULL REQUESTS HERE. Patches are best submitted to GHC's Trac (http://ghc.haskell.org/trac/ghc) or sent to the mailing list (ghc-devs@haskell.org)
Branch: explicit-dicts…
Clone or download
#1 Compare This branch is 210 commits ahead, 4706 commits behind ghc:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.arc-linters
.circleci
bindisttest
compiler
distrib
docs
driver
ghc
hadrian @ 63a5563
includes
inplace
iserv
libffi-tarballs @ 96d0280
libffi
libraries
mk
nofib @ ef4f8dc
rts
rules
testsuite
utils
.arcconfig
.arclint
.gitignore
.gitmodules
.mailmap
.travis.yml
ANNOUNCE
DictUtils.hs
HACKING.md
INSTALL.md
LICENSE
MAKEHELP.md
Makefile
README.md
Sample.hs
Vagrantfile
aclocal.m4
appveyor.yml
boot
build.nix.sh
config.guess
config.sub
configure.ac
ghc.mk
install-sh
llvm-targets
packages
settings.in
shell.nix
validate

README.md

Looking for Partial Type Signatures? Check out the partial-sigs branch.

Coherent Explicit Dictionary Application for Haskell

This is the prototype implementation of the design described in the paper "Coherent Explicit Dictionary Application for Haskell", submitted to Haskell Symposium 2018.

To build this branch, please see the instructions below.

See the file Sample.hs for the full code shown in the paper. After compiling this branch, the sample code can be compiled and run by executing the following commands in the root directory of the repository:

$ TOP="$(pwd)"
$ cabal install --with-compiler="$TOP/inplace/bin/ghc-stage2" --package-db="$TOP/inplace/lib/package.conf.d" QuickCheck mtl
$ inplace/bin/ghc-stage2 -package QuickCheck -package mtl Sample.hs

To start a GHCi session, add the --interactive flag to the last command.

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.

  1. 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!

You can’t perform that action at this time.