Hi,
although I have moved away from Karlsruhe three months ago, so far it
is still my office PC driving
https://perf.haskell.org/ghc/
But a new person is now using my desk and wants to use this machine, so
I should really really move this away from there now.
Sebastian Graf has been working on
Hi,
Am Montag, den 24.10.2016, 11:13 -0700 schrieb John Wiegley:
> JB> Maybe I should move the branch to archive/foobar, to make it clear that
> JB> this is not something actively worked on?
>
> As a side note: you could move them into a different ref spec entirely, which
> is not pulled by
> "JB" == Joachim Breitner writes:
JB> Maybe I should move the branch to archive/foobar, to make it clear that
JB> this is not something actively worked on?
As a side note: you could move them into a different ref spec entirely, which
is not pulled by default when
On Fri, Oct 21, 2016 at 4:04 PM Simon Marlow wrote:
> On 16 October 2016 at 14:03, Michal Terepeta
> wrote:
>
> Hi,
>
> I was looking at cleaning up a bit the situation with dataflow analysis
> for Cmm.
> In particular, I was experimenting with
Hi,
in https://ghc.haskell.org/trac/ghc/ticket/12618#comment:37
Simon raises a question that I was wondering about as well:
Where do we want to store feature branches that contain useful work
that might be picked up some time later (maybe much later¹)?
So far, I have left them as wip/foobar
Hi Iavor and Ryan,
One ticket on memory model issues is #12469.
At openSUSE we see several build failures only now because we recently switched
to parallel Cabal builds.
A compiled Cabal Setup that is called with -j sometimes segfaults on
PowerPC. Actually, if I
try building package OpenGL
Thanks for such a prompt reply -- I'll try that.
Simon
| -Original Message-
| From: Matthew Pickering [mailto:matthewtpicker...@gmail.com]
| Sent: 23 October 2016 00:13
| To: Simon Peyton Jones
| Cc: ghc-devs@haskell.org
| Subject: Re: Aarrgh! Windows build