Hi,
I found these:
https://github.com/ghc/ghc/blob/5f3c5384df59717ca8013c5df8d1f65692867825/includes/rts/Constants.h#L194
They go only 0-14, so there's some long chains of branches and stuff in hot
paths that could be cleaned up into single &-masked branches by changing
these into a set of flags.
20, 2014 at 4:43 AM, Jost Berthold <
berth...@mathematik.uni-marburg.de> wrote:
> Message: 2
>> Date: Sat, 19 Jul 2014 15:00:17 +1000
>> From: Kyle Van Berendonck
>> To: "ghc-devs@haskell.org"
>> Subject: Thread status constants
>> Message-ID:
>
I saw, which looked accidental...).
On Tue, Jul 22, 2014 at 5:32 AM, Simon Marlow wrote:
> On 19/07/2014 06:00, Kyle Van Berendonck wrote:
>
>> I found these:
>> https://github.com/ghc/ghc/blob/5f3c5384df59717ca8013c5df8d1f6
>> 5692867825/includes/rts/Constants.h#L19
-- Forwarded message --
From: Kyle Van Berendonck
Date: Sun, Apr 14, 2013 at 5:56 PM
Subject: Implemented getPageFaults for win32
To: ghc-devs@haskell.org
Author: Kyle Van Berendonck 2013-04-14 17:45:39
Committer: Kyle Van Berendonck 2013-04-14
17:45:39
Parent
text/plain; charset=us-ascii
>
> On Sun, Apr 21, 2013 at 09:34:31PM +0300, Sergei Trofimovich wrote:
> > > commit 310735e7adce0145c653386c21686b4a1b96aea9
> > >
> > > -r = ffi_prep_closure(cl, cif, (void*)wptr, hptr/*userdata*/);
> > > +r = ffi_prep_closure_loc(cl, c
Not sure if this applies here, but withSocketsDo is a huge gotcha.
It doesn't affect Linux, but all networking code on BSD(?)/Windows that
doesn't use it fails to boot with an unfriendly runtime error (and many
people leave it out).
A warning for this would be good.
Regards.
On Thu, May 23, 20
Hi,
I tried to build GHC on windows recently and for some reason it tries to
use a MinGW in repopath/inplace/mingw. I had to copy my entire mingw
installation there to get it to configure.
This isn't normal, right?
Regards.
___
ghc-devs mailing list
gh
Additionally, if you're using the latest MinGW it ships with GCC 4.7 and
fails with an error I reported and thoughtpolice replied here;
http://ghc.haskell.org/trac/ghc/ticket/7056#comment:9
There's a patch that (with some hacking, namely, fixing the missing
bracket) will bring GHC to build. It lat
Hi Simon,
I think this is a MinGW bug. If we're talking about the same bug (lockup,
no console output, task manager shows cpu but it doesn't produce files,
etc) I get it when building other projects with -j too and I don't think
its GHC's fault.
Regards,
Hi,
With the number of jobs. ie, on my laptops A8-3500M that's -j4.
On Wed, Aug 28, 2013 at 8:55 AM, Niklas Larsson wrote:
> Hi!
>
> Are you using make -j with or without number of jobs? I tried with make
> -j4 on my Windows 8 machine and it worked well.
>
> Niklas
&
A quick search reveals that this is valid ANSI C.
Regards,
Kyle
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
Hi,
It was suggested on #ghc we get a discussion going about #7143. We think
it's a good idea that `we should have a default value for lllc and opt
anyways ... even in[if] the host building system doesn't have it locally`.
Non-windows platforms seem to have one that's configured in aclocal.m4. I
The build/test system could be scaring away potential developers too.
Not to complain or anything, but I used to try building GHC (form scratch)
every 2 months or so and It would (usually) completely fail to build on
Windows and OSX, and when it does, there would be some problem with the
makefile
Hi,
I'm cutting my teeth on some constant folding for floats in the cmm.
I have a question regarding the ticket I'm tackling:
Should floats be folded with infinite precision (and later truncated to the
platform float size) -- most useful/accurate, or folded with the platform
precision, i.e. doub
ve a haskeller
>> numerical analyst scratching their head. For example, when doing these
>> floating point computations, what rounding modes will you use?
>>
>> On Monday, January 13, 2014, Kyle Van Berendonck wrote:
>>
>>> Hi,
>>>
>>> I
A couple of poor assumptions are made here.
The first is that the userbase of GHC on Windows is poor. This is false. In
fact, the poor state of Windows is mentioned on #haskell more frequently as
of late. In the last week I've talked almost every day to (different)
people who have had Windows woes
Hmm.
I just got flagged as a spambot trying to reply to a ticket too. It did
give me a captcha option though.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
17 matches
Mail list logo
