delta/haskell.git, branch wip/static-pointers gitlab.haskell.org: ghc/ghc.git Implement -XStaticValues. 2014-12-02T14:55:30+00:00 Facundo Domínguez facundo.dominguez@tweag.io 2014-01-29T14:43:03+00:00 79c87c039c47be0baf7a6dd33ecf5434daa1501c Contains contributions from Alexander Vershilov and Mathieu Boespflug. As proposed in [1], this extension introduces a new syntactic form `static e`, where `e :: a` can be any closed expression. The static form produces a value of type `StaticPtr a`, which works as a reference that programs can "dereference" to get the value of `e` back. References are like `Ptr`s, except that they are stable across invocations of a program. In essence the extension collects the arguments of the static form into a global static pointer table. The expressions can be looked up by a fingerprint computed from the package, the module and a fresh name given to the expression. For more details we refer to the users guide section contained in the patch. The extension is a contribution to the Cloud Haskell ecosystem (distributed-process and related), and thus has the potential to foster Haskell as a programming language for distributed systems. The immediate improvement brought by the extension is the elimination of remote tables from Cloud Haskell applications. Such applications contain table fragments spread throughout multiple modules and packages. Eliminating these fragments saves the programmer the burden required to construct and assemble the global remote table, a verbose and error-prone process, even with the help of Template Haskell, that moreover pollutes the export lists of all modules. [1] Jeff Epstein, Andrew P. Black, and Simon Peyton-Jones. Towards Haskell in the cloud. SIGPLAN Not., 46(12):118–129, September 2011. ISSN 0362-1340. 
Contains contributions from Alexander Vershilov and Mathieu Boespflug.

As proposed in [1], this extension introduces a new syntactic form
`static e`, where `e :: a` can be any closed expression. The static form
produces a value of type `StaticPtr a`, which works as a reference that
programs can "dereference" to get the value of `e` back. References are
like `Ptr`s, except that they are stable across invocations of a
program.

In essence the extension collects the arguments of the static form into
a global static pointer table. The expressions can be looked up by a
fingerprint computed from the package, the module and a fresh name
given to the expression. For more details we refer to the users guide
section contained in the patch.

The extension is a contribution to the Cloud Haskell ecosystem
(distributed-process and related), and thus has the potential to foster
Haskell as a programming language for distributed systems.

The immediate improvement brought by the extension is the elimination of
remote tables from Cloud Haskell applications. Such applications contain
table fragments spread throughout multiple modules and packages.
Eliminating these fragments saves the programmer the burden required to
construct and assemble the global remote table, a verbose and
error-prone process, even with the help of Template Haskell, that
moreover pollutes the export lists of all modules.

[1] Jeff Epstein, Andrew P. Black, and Simon Peyton-Jones. Towards
Haskell in the cloud. SIGPLAN Not., 46(12):118–129, September 2011. ISSN
0362-1340.
Update validate settings now that containers and process have been 2014-11-17T02:29:58+00:00 David Terei code@davidterei.com 2014-11-17T02:29:58+00:00 a2c0a8dd15de2023e17078fa5f421ba581b3a5fa updated to handle `-fwarn-trustworthy-safe`. 
updated to handle `-fwarn-trustworthy-safe`.
Fix compilation of `integer-gmp2` with `-O0` 2014-11-15T17:11:17+00:00 Herbert Valerio Riedel hvr@gnu.org 2014-11-15T17:05:58+00:00 c45e2e29dee8c38fc852388289d700605132278f At optimization level `-O0` `wordToInteger` wasn't inlined, and this caused a `__integer` literal to turn up in final Core, which would trigger the GHC panic ghc-stage1: panic! (the 'impossible' happened) (GHC version 7.9.20141114 for x86_64-unknown-linux): Can't use Integer in integer-* By forcing inlining via `inline` this is avoided. This should hopefully address #9800. 
At optimization level `-O0` `wordToInteger` wasn't inlined, and this caused a
`__integer` literal to turn up in final Core, which would trigger the GHC panic

  ghc-stage1: panic! (the 'impossible' happened)
    (GHC version 7.9.20141114 for x86_64-unknown-linux):
	Can't use Integer in integer-*

By forcing inlining via `inline` this is avoided.
This should hopefully address #9800.
Update to (unreleased) `deepseq-1.4.0.0` 2014-11-15T11:20:03+00:00 Herbert Valerio Riedel hvr@gnu.org 2014-11-15T11:16:38+00:00 609cd28a1a8616f4076088c87e443850d807ba7d This pulls in the new `Generic`-based `-XDefaultSignature`-based default implementation for `rnf`[1], and will be interesting to use in combination with the soon to be merged `-XDeriveAnyClass` extension. This requires updating several other submodules as well in order to relax the upper bound on `deepseq` and/or in a few cases to avoid relying on the default method implementation of `rnf`: - `Cabal` - `bytestring` - `containers` - `parallel` - `process` - `time` [1]: http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/23031 
This pulls in the new `Generic`-based `-XDefaultSignature`-based default
implementation for `rnf`[1], and will be interesting to use in combination
with the soon to be merged `-XDeriveAnyClass` extension.

This requires updating several other submodules as well in order
to relax the upper bound on `deepseq` and/or in a few cases to
avoid relying on the default method implementation of `rnf`:

 - `Cabal`
 - `bytestring`
 - `containers`
 - `parallel`
 - `process`
 - `time`

 [1]: http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/23031
Workaround 452d6aa95b7 breaking TrustworthySafe03 2014-11-15T10:18:12+00:00 Herbert Valerio Riedel hvr@gnu.org 2014-11-15T10:18:12+00:00 185482524d4fa5954243476de1452219fb077228 This is only a temporary kludge until the issue workarounded by 452d6aa95b7 gets properly fixed 
This is only a temporary kludge until the issue workarounded by 452d6aa95b7
gets properly fixed
Generalize exposed-modules field in installed package database 2014-11-15T08:36:03+00:00 Edward Z. Yang ezyang@cs.stanford.edu 2014-11-15T08:08:53+00:00 e14a973215102cb3774e3b4370c64edcff0e10bc Summary: Instead of recording exposed-modules and reexported-modules as seperate fields in the installed package database, this commit merges them into a single field (exposed-modules). The motivation for this change is in preparation for the inclusion of *signatures* into the installed package database, which may also be reexported. Merging the representation means that we can treat reexports uniformly, no matter if they're a normal module or a signature. This commit adds a stub for signatures, but that code isn't wired up to anything yet. Contains Cabal submodule update to accommodate these changes. Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu> Test Plan: validate Reviewers: simonpj, duncan, austin Subscribers: thomie, carter, simonmar Differential Revision: https://phabricator.haskell.org/D421 
Summary:
Instead of recording exposed-modules and reexported-modules as seperate
fields in the installed package database, this commit merges them into
a single field (exposed-modules).  The motivation for this change is
in preparation for the inclusion of *signatures* into the installed
package database, which may also be reexported.  Merging the representation
means that we can treat reexports uniformly, no matter if they're a normal
module or a signature.

This commit adds a stub for signatures, but that code isn't wired up to
anything yet.

Contains Cabal submodule update to accommodate these changes.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Test Plan: validate

Reviewers: simonpj, duncan, austin

Subscribers: thomie, carter, simonmar

Differential Revision: https://phabricator.haskell.org/D421
Partially revert 475dd93efa 2014-11-14T17:51:33+00:00 Austin Seipp austin@well-typed.com 2014-11-14T17:51:31+00:00 452d6aa95b754a08e1e61800680ccbf6f968aef0 This introduces ./validate failures for Windows right now, so in the mean time let's just back this flag out as a default -Wall flag. Signed-off-by: Austin Seipp <austin@well-typed.com> 
This introduces ./validate failures for Windows right now, so in the
mean time let's just back this flag out as a default -Wall flag.

Signed-off-by: Austin Seipp <austin@well-typed.com>
Update .mailmap 2014-11-14T11:18:42+00:00 Thomas Miedema thomasmiedema@gmail.com 2014-11-08T12:44:57+00:00 fa75309456a30b097b1003fcd7b7aa073bab9314 [skip ci] 
[skip ci]
Implement amap/coerce for Array (re #9796) 2014-11-13T20:15:33+00:00 David Feuer David.Feuer@gmail.com 2014-11-13T20:12:05+00:00 603b7be7bd3abaf0e2c210e8d9015b1d613b4715 Implement an `amap`/`coerce` rule in `GHC.Arr` to match the `map`/`coerce` rule in GHC.Base. In order to do so, delay inlining `amap` until phase 1. To prevent the inlining delay from causing major inefficiencies due to missed list fusion, rewrite `amap` to avoid relying on list fusion. This has the extra benefit of reducing the size of the compiled amap code by skipping the impossible case of an array with a negative size. Reviewed By: nomeata Differential Revision: https://phabricator.haskell.org/D471 
Implement an `amap`/`coerce` rule in `GHC.Arr` to match the
`map`/`coerce` rule in GHC.Base.

In order to do so, delay inlining `amap` until phase 1.

To prevent the inlining delay from causing major inefficiencies due to
missed list fusion, rewrite `amap` to avoid relying on list fusion. This
has the extra benefit of reducing the size of the compiled amap code by
skipping the impossible case of an array with a negative size.

Reviewed By: nomeata

Differential Revision: https://phabricator.haskell.org/D471
When calling the success continuation of a matcher, pass existential tyvars 2014-11-13T15:38:39+00:00 Dr. ERDI Gergo gergo@erdi.hu 2014-11-13T09:47:18+00:00 638991114f9358ee78f32d5d5c98bb3001b52ec9 as type arguments, not value arguments 
as type arguments, not value arguments