On 26/06/2012 00:42, Ryan Newton wrote:
However, the parallel GC will be a problem if one or more of your
cores is being used by other process(es) on the machine. In that
case, the GC synchronisation will stall and performance will go down
the drain. You can often see this on a
Hi,
I hope this is the correct list to ask this question.
I am trying to compile the ghcjs compiler. I am on ubuntu 12.04 and have
ghc-7.4.1 installed (via apt-get).
I am following the instruction I found here: https://github.com/ghcjs/ghcjs
The first trouble comes with git pull ghcjs. I get:
On Tue, Jun 26, 2012 at 04:30:02PM -0700, Johan Tibell wrote:
I just want to see things changed. :)
We're happy to try to improve things, but I'm not sure what change you
want exactly.
We could change the default for GHC stable branches to:
* Use the tag for the latest release, unless that
On Wed, Jun 27, 2012 at 3:20 AM, Paolo Capriotti p.caprio...@gmail.com wrote:
On Wed, Jun 27, 2012 at 12:30 AM, Johan Tibell johan.tib...@gmail.com wrote:
* Some libraries will need to have version bumps, which means that other
libraries will need to loosen their dependencies, which means
On Wed, Jun 27, 2012 at 8:12 AM, Ian Lynagh i...@well-typed.com wrote:
On Tue, Jun 26, 2012 at 04:30:02PM -0700, Johan Tibell wrote:
I just want to see things changed. :)
We're happy to try to improve things, but I'm not sure what change you
want exactly.
I want GHC to stop releasing other
On Wed, Jun 27, 2012 at 11:42:24AM -0700, Johan Tibell wrote:
On Wed, Jun 27, 2012 at 8:12 AM, Ian Lynagh i...@well-typed.com wrote:
On Tue, Jun 26, 2012 at 04:30:02PM -0700, Johan Tibell wrote:
I just want to see things changed. :)
We're happy to try to improve things, but I'm not sure
Hi,
On Wed, Jun 27, 2012 at 12:53 PM, Ian Lynagh ig...@earth.li wrote:
If a GHC release needs an unreleased change in one of the libraries, and
the maintainer (for whatever reason) is not responding to e-mails,
should the GHC release be held up indefinitely?
Again, note that GHC is no
On 6/27/12 6:06 PM, Johan Tibell wrote:
This is not a theoretical issue. We have had all of the following
problems happen in the past due to the current process:
* patches never making it upstream
* releases of libraries without knowledge of the maintainer (who
finds out by finding a new
