On 2014-10-13 at 23:33:13 +0200, Austin Seipp wrote:
[...]
Also, if any other developers (like Andreas, Johan, Bryan, etc) in
this space want a big machine to test it on, I can probably equip you
with one (or several). Since Rackspace is so gracious to us, we can
immediately allocate
Hi devs,
I have what I hope is a simple request: that patch submissions contain a road
map describing the patch. I'll illustrate via example: I just took a quick
look at D323, about updating the design of Uniques. Although this patch was
fairly straightforward, I would have been helped by a
I frequently find myself asking for a different kind of road map: a wiki page
saying
- what is the problem we are trying to solve
- what is the general approach for solving it
- what is the specification for what a GHC user (or maybe a GHC API client,
depending) would see?
- what is a road map
This is awesome. I'd like to try to recreate some of the evaluations for
the multicore IO manager paper on that 40 core system at backspace. How can
I get access to this? I'll jump on IRC - maybe it is easier to chat in
realtime.
On Mon, Oct 13, 2014 at 5:33 PM, Austin Seipp aus...@well-typed.com
Hey Andreas,
The basic rundown is that if we equip you with an account, you can
just do it yourself. Although we'd like to restrict access a bit more;
I'll figure something out.
Yeah, if you hop on IRC, we can chat quickly about it and work
something out in the mean time.
On Tue, Oct 14, 2014
Andreas Voellmy andreas.voel...@gmail.com writes:
This is awesome. I'd like to try to recreate some of the evaluations for
the multicore IO manager paper on that 40 core system at backspace. How can
I get access to this? I'll jump on IRC - maybe it is easier to chat in
realtime.
Do you
Yes, I'll try to describe it and script it so that others can understand
the benchmarks and run it easily as well.
On Tue, Oct 14, 2014 at 1:23 PM, Ben Gamari bgamari.f...@gmail.com wrote:
Andreas Voellmy andreas.voel...@gmail.com writes:
This is awesome. I'd like to try to recreate some of
I believe I've just pushed a fix for this, let me know if you still have
problems.
Cheers,
Simon
On 10/10/2014 13:47, Carter Schonwald wrote:
likewise, 32bit OS X seems to be broken on HEAD too
http://lpaste.net/112412 is the relevant bit
make[5]: Nothing to be done for `all'.
Simon, did you see this?
Simon
-Original Message-
From: Glasgow-haskell-users [mailto:glasgow-haskell-users-boun...@haskell.org]
On Behalf Of Bulat Ziganshin
Sent: 14 October 2014 18:09
To: glasgow-haskell-us...@haskell.org
Subject: optimizing StgPtr allocate (Capability *cap, W_ n)
Hello,
i'm looking a the
https://github.com/ghc/ghc/blob/23bb90460d7c963ee617d250fa0a33c6ac7bbc53/rts/sm/Storage.c#L680
if i correctly understand, it's speed-critical routine?
i think that it may be improved in this way:
StgPtr allocate (Capability *cap, W_ n)
{
bdescr *bd;
StgPtr p;
Hello,
Would it be better to organize proposals under one namespace? Right now
they belongs to root namespace, so title index
( https://ghc.haskell.org/trac/ghc/wiki/TitleIndex ) is hard to use.
I was going to start new page describing language extension, but I don't
want do increase entropy
Hello Mikolaj,
Wednesday, October 15, 2014, 2:07:35 AM, you wrote:
i'm sorry, it's the same
Hi Bulat!
Is this exactly the same email you posted to
glasgow-haskell-users@ previously (I'm asking to know
if I need to reread)? It was already forwarded here by none
other but SPJ. :)
Hi,
Am Mittwoch, den 15.10.2014, 01:12 +0300 schrieb Yuras Shumovich:
Would it be better to organize proposals under one namespace? Right now
they belongs to root namespace, so title index
( https://ghc.haskell.org/trac/ghc/wiki/TitleIndex ) is hard to use.
I was going to start new page
13 matches
Mail list logo