- Mar 23, 2014
-
-
Herbert Valerio Riedel authored
This should help contribute content to https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git/Submodules Signed-off-by:
Herbert Valerio Riedel <hvr@gnu.org>
-
kgardas authored
The patch provided by Christian Maeder <Christian.Maeder@dfki.de> Signed-off-by:
Karel Gardas <karel.gardas@centrum.cz> Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
Austin Seipp authored
This adds a simple Vagrantfile to the root directory, which you can use to easily spin up RHEL/Debian/Ubuntu virtual machine in seconds to test GHC. For example, from the root of the GHC tree, you can say: $ vagrant up ubuntu1204-amd64 $ vagrant ssh ubuntu1204-amd64 This will give you access to a provisioned Ubuntu 12.04 virtual machine with all the necessary GHC dependencies installed (modulo a few things). Debian 7/CentOS 6.5/Ubuntu 12.04 only for now, in amd64/i386 configurations. In the future I plan to at least add FreeBSD and NixOS boxes where possible. Improvements are necessary of course. By default a box is given 4GB of RAM and 2 cores, and resolves DNS entries by routing through the host DNS configuration. Do not run 'vagrant up' unless you have lots of RAM as it will spawn *every* virtual machine. Hopefully, this should make it far easier for contributors to get started eventually. Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
kgardas authored
Both --with-ar and --with-ranlib are usable on non-GNU/Linux systems where GNU tools are usually installed (or possible to install), but not into standard location nor with standard name. Tested on Solaris 10. Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
Florian Weimer authored
Before this change, the END actions were executed even if the code throws an exception using "die". This resulted in very confusing error reporting when an invalid command line option was specified. Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
- Mar 22, 2014
-
-
Richard Eisenberg authored
FamInstEnv.normaliseTcApp should normalise arguments even when the top-level tycon isn't a type family. This was a regression from 7.6 -- not sure when it happened, but it was probably my fault. Fixed now, in any case.
-
Richard Eisenberg authored
-
Richard Eisenberg authored
Previously, the closed type family compatibility check was done even when type-checking an interface file. But interface files now store compatibility info, so this check was redundant.
-
Richard Eisenberg authored
-
Mikhail Glushenkov authored
Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
tibbe authored
The fix was to ghc-prim.
-
tibbe authored
-
Joachim Breitner authored
to keep validate working.
-
tibbe authored
The inline allocation version is 69% faster than the out-of-line version, when cloning an array of 16 unit elements on a 64-bit machine. Comparing the new and the old primop implementations isn't straightforward. The old version had a missing heap check that I discovered during the development of the new version. Comparing the old and the new version would requiring fixing the old version, which in turn means reimplementing the equivalent of MAYBE_CG in StgCmmPrim. The inline allocation threshold is configurable via -fmax-inline-alloc-size which gives the maximum array size, in bytes, to allocate inline. The size does not include the closure header size. Allowing the same primop to be either inline or out-of-line has some implication for how we lay out heap checks. We always place a heap check around out-of-line primops, as they may allocate outside of our knowledge. However, for the inline primops we only allow allocation via the standard means (i.e. virtHp). Since the clone primops might be either inline or out-of-line the heap check layout code now consults shouldInlinePrimOp to know whether a primop will be inlined.
-
- Mar 21, 2014
-
-
foxnorth authored
Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
awson authored
Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
Austin Seipp authored
Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
Austin Seipp authored
Signed-off-by:
Austin Seipp <austin@well-typed.com>
-
Joachim Breitner authored
(I recall that this was needed in some cases in the past, and might fix the validate error on travis.)
-
- Mar 20, 2014
-
-
tibbe authored
gcptr should only be used for pointers that the GC should follow. While this didn't cause any bugs right now, since these variables aren't live over a GC, it's clearer to use the right type.
-
- Mar 19, 2014
-
-
Gergő Érdi authored
interface contents
-
Gergő Érdi authored
This is so that generated names like e.g. workers don't show up as infix operators when using something like -ddump-simpl.
-
Iavor S. Diatchki authored
This is done with two built-in type families: `CmpNat and `CmpSymbol`. Both of these return a promoted `Ordering` type (EQ, LT, or GT).
-
- Mar 18, 2014
-
-
Simon Peyton Jones authored
For DFunUnfoldings we were failing to occurrence-analyse the unfolding, and that meant that a loop breaker wasn't marked as such, which in turn meant it was inlined away when it still had occurrence sites. See Note [Occurrrence analysis of unfoldings] in CoreUnfold. This is a pretty long-standing bug, happily nailed by John Lato.
-
Herbert Valerio Riedel authored
Signed-off-by:
Herbert Valerio Riedel <hvr@gnu.org>
-
Iavor S. Diatchki authored
I moved the "promoted literals" sub-section into a separate section, as many folks were not finding the docs. I also added some additional paragraphs describing the current state of the feature.
-
- Mar 17, 2014
-
-
Joachim Breitner authored
-
Simon Peyton Jones authored
-
Simon Peyton Jones authored
-
Simon Peyton Jones authored
-
Joachim Breitner authored
-
Simon Peyton Jones authored
We don't yet understand WHY commit ad15c2, which is to do with CmmSink, causes seg-faults on Windows, but it certainly seems to. So reverting it is a stop-gap, but we need to un-block the 7.8 release. Many thanks to awson for identifying the offending commit.
-
Simon Peyton Jones authored
There was even a comment to warn about this possiblity, and it finally showed up in practice! This patch fixes it quite nicely, with commens to explain.
-
- Mar 16, 2014
-
-
Joachim Breitner authored
This partly reverts commit e239753c. Since Coercible is exported via GHC.Types, so "primclass" is no longer needed. The support for => in primops.pp is still required for coerce.
-
Joachim Breitner authored
so do not export it in GHC.Prim, and also have the pseudo-code for GHC.Prim import GHC.Types, so that haddock is happy.
-
Joachim Breitner authored
(Unchecked comment-only commits should better use the right commenting style...)
-
Joachim Breitner authored
This prepares against future breakage, especially if #8894 is tackled.
-
- Mar 14, 2014
-
-
Richard Eisenberg authored
This is a followup to the fix for #8827, and should be merged with that change.
-
Joachim Breitner authored
-
Joachim Breitner authored
Even if the recursion is a nice tail-call only recusion, we'd stil be calling the thunk multiple times and eta-expansion would be wrong. Includes a [Note]. (Also shows the disadvantage of unit tests: They had the same bug.)
-