Probably, building an optimized stage1, skip building stage2 and
get nofib to be compiled with the stage1 compiler. I'm not sure
off the top of my head how to do the last step.
Edward
Excerpts from David Feuer's message of 2014-08-19 03:21:49 +0100:
I'd like to try out a bunch of little
Hello Simon,
On 2014-08-19 at 00:01:17 +0200, Simon Peyton Jones wrote:
[...]
But you can probably write the code in such a way as to be mostly
independent (eg explicit UNPACK rather than rely on
-funbox-strict-fields), or assume that some things won't happen
(e.g. souce module will not be
Hello *,
Sorry for the scatter-brained-ness of my update. But without further
ado, here are some things that have been going on:
- I was going to land AMP, but I've gotten stuck again! It seems that
now, Haddock infinite loops, but this one I really can't figure out.
See my comment on the
Edward, and core library colleagues,
Any views on this? It would be good to make progress.
Thanks
Simon
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Simon Peyton
Jones
Sent: 04 August 2014 16:01
To: core-libraries-commit...@haskell.org
Cc: ghc-devs@haskell.org
Subject: Core
Hi Simon,
If you don't mind the extra traffic in the ghc trac, I'm open to the plan
to work there.
I was talking to Eric Mertens a few days ago about this and he agreed to
take lead on getting us set up to actually build tickets for items that go
into the libraries@ proposal process, so we have
Yes, -O0 implies -fomit-interface-pragmas.
I still think that option 3 would a better avenue.
Simon
| -Original Message-
| From: Herbert Valerio Riedel [mailto:hvrie...@gmail.com]
| Sent: 19 August 2014 10:24
| To: Simon Peyton Jones
| Cc: ghc-devs@haskell.org
| Subject: Re: Wired-in
If you don't mind the extra traffic in the ghc trac, I'm open to the plan to
work there.
OK great.
Let’s agree that:
·The “owner” of a Core Libraries ticket is the person responsible for
progressing it – or “Core Libraries Committee” as one possibility.
·The “component”
Aaargh! My windows build is broken, again.
It's very painful that this keeps happening.
Can anyone help?
Simon
inplace/bin/ghc-stage1.exe -optc-U__i686 -optc-march=i686
-optc-fno-stack-protector -optc-Werror -optc-Wall -optc-Wall -optc-Wextra
-optc-Wstrict-prototypes -optc-Wmissing-prototypes
f9f89b7884ccc8ee5047cf4fffdf2b36df6832df is probably to blame.
Found by running `git log -SsetIOManagerControlFd`. The -S flag is a good
way to find when a symbol is added/removed.
On Wed, Aug 20, 2014 at 12:16 AM, Simon Peyton Jones simo...@microsoft.com
wrote:
Aaargh! My windows build is
