GitLab

Note: the .gitignore pattern rules are not that obvious
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

This adapts the top-level .gitignore file to match the new situation of
base.git, ghc-prim.git, integer-gmp.git, integer-simple.git, and
template-haskell.git being folded into ghc.git
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Signed-off-by: Austin Seipp <austin@well-typed.com>

When printing allocated bytes (`:set +s` in ghci), separate thousands
to make it easier to read large allocations sizes, e.g. “1,200,000
bytes”.
Signed-off-by: Austin Seipp <austin@well-typed.com>

This is ArchUnknown for now, as it requires some porting work over and
above powerpc64 due to such things as the different function calling
sequence in the ELFv2 ABI.  For now, an unregisterised port is better
than nothing.
Signed-off-by: Colin Watson <cjwatson@debian.org>
Signed-off-by: Austin Seipp <austin@well-typed.com>

GHC's generated C code uses dummy prototypes for foreign imports.  At the
moment these all claim to be (void), i.e. functions of zero arguments.  On
most platforms this doesn't matter very much: calls to these functions put
the parameters in the usual places anyway, and (with the exception of
varargs) things just work.

However, the ELFv2 ABI on ppc64 optimises stack allocation
(http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01149.html

): a call to a
function that has a prototype, is not varargs, and receives all parameters
in registers rather than on the stack does not require the caller to
allocate an argument save area.  The incorrect prototypes cause GCC to
believe that all functions declared this way can be called without an
argument save area, but if the callee has sufficiently many arguments then
it will expect that area to be present, and will thus corrupt the caller's
stack.  This happens in particular with calls to runInteractiveProcess in
libraries/process/cbits/runProcess.c.

The simplest fix appears to be to declare these external functions with an
unspecified argument list rather than a void argument list.  This is no
worse for platforms that don't care either way, and allows a successful
bootstrap of GHC 7.8 on little-endian Linux ppc64 (which uses the ELFv2
ABI).

Fixes #8965
Signed-off-by: Colin Watson <cjwatson@debian.org>
Signed-off-by: Austin Seipp <austin@well-typed.com>

Signed-off-by: Austin Seipp <austin@well-typed.com>

This removes the following, now defunct flags, which will not be
recognized by GHC 7.10:

  -fwarn-lazy-unlifted-bindings
  -pgmm and -optm (used for the Mangler, long dead)
  -keep-raw-s-file & -keep-raw-s-files
  -monly[432]-reg-only
Signed-off-by: Austin Seipp <austin@well-typed.com>

This is a follow-up to 77ea2eb0

 (re #9016) which added `die` with a
return type of `IO ()` even though all other functions in System.Exit have
the more general return type `IO a`. It is assumed this was an oversight in
the original proposal.
Acked-by: Edward Kmett <ekmett@gmail.com>
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

This clean-up is in a similiar spirit as 574ef429

.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Simon Hengel authored Apr 21, 2014 and Herbert Valerio Riedel committed Apr 21, 2014

The original proposal discussion can be found at

  http://thread.gmane.org/gmane.comp.lang.haskell.libraries/20872

Note this also updates the Haddock submodule to remove Hadock's local
`die` implementation.

Soon, System.Exit will export the new `die` (see #9016) which would clash with
Cabal's own `die` implementation. This commit provides forward-compatiblity.

This also updates the Cabal submodule which requires a similiar fix.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

GHC previously introduced a space here. However, this can in some cases
be interpreted as "-U __PIC__" - note that in shell, the -U would still
be recognized with an argument, but the argument would be " __PIC__",
with a space in front, as opposed to the single string '__PIC__'.

In practice most tools seem to handle this OK. But the Coverity Scan
analysis tool does not: it errors on the fact that ' __PIC__' is an
invalid CPP name to undefine.

With this, it seems the Coverity analysis tool can easily analyze the
entire GHC build.
Signed-off-by: Austin Seipp <austin@well-typed.com>

Signed-off-by: Austin Seipp <austin@well-typed.com>

Now that we're in development mode, Applicative will soon be a
superclass of Monad in HEAD. So let's go ahead and deprecate the
-fno-warn-amp flag, remove the checks, and tweak a few tests
Signed-off-by: Austin Seipp <austin@well-typed.com>

Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

GHC should now fully compliant with respect to the Applicative Monad
proposal (including all upstream libraries), and does not need to
suppress this warning anymore.
Signed-off-by: Austin Seipp <austin@well-typed.com>

This adapts the source-repository entries to match the new situation of
base.git, ghc-prim.git, integer-gmp.git, integer-simple.git, and
template-haskell.git being folded into ghc.git
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Update several old

  http://hackage.haskell.org/trac/ghc

URLs references to the current

  http://ghc.haskell.org/trac/ghc



URLs.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

The RealFloat data type context was dropped from Data.Complex some time
ago (see ea280135). However, the rest of
the API in that module was left as-is even though many of the accessors
in that module would work with much more general types now.

This change simplifies the signatures of the functions above, which in
the current API all unnecessarily take a RealFloat constraint that they
don't use (and which may cause to pass around superflous type-class
dictionaries):

    realPart  :: Complex a -> a
    imagPart  :: Complex a -> a
    conjugate :: Num a => Complex a -> Complex a
    mkPolar   :: Floating a => a -> a -> Complex a
    cis       :: Floating a => a -> Complex a

This was originally proposed by Edward Kmett in

  http://www.haskell.org/pipermail/libraries/2014-March/022358.html

Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

Curiously, 'aforesaid' has the same length as the word 'testsuite'...
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

bernalex authored Apr 18, 2014 and Herbert Valerio Riedel committed Apr 19, 2014

`sortOn` sorts a list by comparing the results of a key function applied to each
element.  `sortOn f` is equivalent to `sortBy . comparing f`, but has the
performance advantage of only evaluating `f` once for each element in the
input list.

Historical note: This was already proposed in 2008 as part of

  http://www.haskell.org/pipermail/libraries/2008-October/010797.html

It was, however, the recent re-attempt

  http://www.haskell.org/pipermail/libraries/2014-April/022489.html

that let `sortOn` make it into base at last. Maybe the other functions
mentioned in #2659 might be worth reconsidering as well.

bernalex authored Apr 17, 2014 and Herbert Valerio Riedel committed Apr 19, 2014

Add `&` as the reverse application operator with `infixl 1`, which allows
it to be nested in `$` (re #9008).

Approved by the core libraries committee on 2013-10-14.

This also bumps the `base` version number to 4.7.1.0

This checks that all the required extensions are enabled for the
inferred type signature.

Updates binary and vector submodules.

This adapts `sync-all` and `packages` to the recently folded-in Git
repositories

 - `base.git`
 - `ghc-prim.git`
 - `integer-gmp.git`
 - `integer-simple.git`
 - `template-haskell.git`

See #8545 as well as 5f54d678

 for more
details.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

At the time of merge, template-haskell.git was at
[9bcc122819a6f4a2ae7ad569717324b8368e801c/template-haskell]
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

At the time of merge, integer-gmp.git was at
[d7bff4dddfa10389156ca11f75a5a23e78cf3ab0/integer-gmp]

Note: All but the last/current GMP tarball were removed from the
      history to keep the Git history size at a minimum.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

At the time of merge, integer-simple.git was at
[9e8b924f68c4cdb6c7ae88f274baa3560aaa305e/integer-simple]
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

At the time of merge, base.git was at
[52c0b09036c36f1ed928663abb2f295fd36a88bb/base]
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

At the time of merge, ghc-prim.git was at
[ad9bf96815cb5a9bb4acc51c99eff20be3e50da3/ghc-prim]
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>

In the rather gnarly filterImports code, someone had forgotten
the AvailTC invariant:  in AvailTC n [n,s1,s2], the 'n' is itself
included in the list of names.

see also https://github.com/haskell/cabal/issues/1789

The testsuite reference output for ghcpkg01 needs to be adapted
since a "More diff friendly pretty printing of cabal files"
is now performed.

Fixes Trac #8987.  See Note [Exceptions in TH]

Thanks to Yuras Shumovich for doing this.

This corresponds to the RC of the soon-to-be Cabal 1.20 release

One noteworthy change is the removal of the `--with-ranlib` flag
requiring a small adaptation in the GHC build system.

Moreover two new licences were added, MPL and BSD2.

Due to https://github.com/haskell/cabal/issues/1622

 Cabal-1.20 now
allows to strip libraries as well, this doesn't work well with
`ghc-cabal copy` being fed a `":"` strip-command argument which was
simply ignored in the past. The current code tries to retain this
semantics as backward compat. However, this needs more investigation as
I'm not sure if/why the `test_bindist` step doesn't want the libraries
to be stripped on installation.
Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>