Donald Bruce Stewart wrote:
Got some initial nobench numbers for ghc head -fvia-C versus -fasm, on
amd64:
http://www.cse.unsw.edu.au/~dons/nobench/x86_64/results.html
Overall all of nobench, ghc -fasm averages 3% slower. Not too shabby!
There's some wider variation on the microbenchmarks in
simonmarhaskell:
> Donald Bruce Stewart wrote:
> >Got some initial nobench numbers for ghc head -fvia-C versus -fasm, on
> >amd64:
> >
> >http://www.cse.unsw.edu.au/~dons/nobench/x86_64/results.html
> >
> >Overall all of nobench, ghc -fasm averages 3% slower. Not too shabby!
> >There's some wid
On Wed, 2007-02-28 at 09:32 -0800, David Brown wrote:
> However, what I missed is that the hsc2hs target files are placed
> alongside the source, not in the dist directory. I had been building
> zlib on x86 using the hs generated on an amd64 machine. The offsets
> in the structures were wrong.
Ok, what happens here is that in the forked process there is only a single
thread, the runtime kills all the other threads (as advertised). Unfortunately
this includes the I/O manager thread, so as soon as you do some I/O in the
forked process, you block.
It might be possible to fix this, but
On Thu, Mar 01, 2007 at 03:06:22PM +, Simon Marlow wrote:
> Ok, what happens here is that in the forked process there is only a single
> thread, the runtime kills all the other threads (as advertised).
> Unfortunately this includes the I/O manager thread, so as soon as you do
> some I/O in
John Goerzen wrote:
On Thu, Mar 01, 2007 at 03:06:22PM +, Simon Marlow wrote:
Ok, what happens here is that in the forked process there is only a single
thread, the runtime kills all the other threads (as advertised).
Unfortunately this includes the I/O manager thread, so as soon as you do
It looks like you're running into the problem of apple's readline
not actually being readline at all (it's a link to some other library
that is almost, but not quite, readline).
See http://cvs.haskell.org/trac/ghc/wiki/Building/MacOSX
for instructions on how to install readline and how
to tell gh
On Thu, Mar 01, 2007 at 04:21:45PM +, Simon Marlow wrote:
> >Between that and the lack of support for forkProcess in Hugs, this
> >renders anything that needs to fork and then do I/O as being usable only
> >in GHC-compiled code. Which is sub-optimal, but livable anyway.
>
> I guess I'm really
At Thu, 1 Mar 2007 11:38:54 -0600,
John Goerzen wrote:
>
> On Thu, Mar 01, 2007 at 04:21:45PM +, Simon Marlow wrote:
> > >Between that and the lack of support for forkProcess in Hugs, this
> > >renders anything that needs to fork and then do I/O as being usable only
> > >in GHC-compiled code.
On Thu, 2007-03-01 at 11:04 -0800, Jeremy Shaw wrote:
> Some open questions are:
>
> a) how do you detect that you are running in the threaded RTS
Currently the nearest approximation is:
Control.Concurrent.rtsSupportsBoundThreads :: Bool
Duncan
__
10 matches
Mail list logo
