ghc -fasm declared not too shabby

2007-02-28 Thread Donald Bruce Stewart
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 the imaginary class: one

Linker error when building GHC HEAD on Mac OS

2007-02-28 Thread Stefan Holdermans
I'm trying to build GHC HEAD on Mac OS 10.4.8 (PowerPC), but end up with a linker error: ../compiler/stage1/ghc-inplace -o stage2/ghc-6.7.20070228 -H16m -O -package ghc -Istage2 -cpp -fglasgow-exts -fno-generics -Rghc-timing - I. -IcodeGen -InativeGen -Iparser -Rghc-timing -DGHCI -DDEBUGG

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread Jeremy Shaw
Hello, Here is a simplified example that seems to exhibit the same behaviour, unless I screwed up: ---> module Main where import System.Posix import System.IO import System.Exit main = do putStrLn "running..." (stdinr, stdinw) <- createPipe (stdoutr, stdoutw) <- createPipe

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread Jeremy Shaw
Hello, Hrm, setting the LineBuffering mode had the side-effect of setting the underlying file description to non-blocking mode. When the executeFile process took over, it would die with an error about 'standard input temporarily unavailable'. So, ignore that. j. At Wed, 28 Feb 2007 15:23:53 -060

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread John Goerzen
On Wed, Feb 28, 2007 at 01:06:25PM -0800, Jeremy Shaw wrote: > Hello, > > Your first problem is just a line buffering issue. You need to > explicitly set the line buffer inside the child processes: > > redir fstdin stdInput > hSetBufferi

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread Jeremy Shaw
Hello, Your first problem is just a line buffering issue. You need to explicitly set the line buffer inside the child processes: redir fstdin stdInput hSetBuffering stdin LineBuffering redir fstdout stdOutpu

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread John Goerzen
On Wed, Feb 28, 2007 at 10:40:18AM -0800, Jeremy Shaw wrote: > At Wed, 28 Feb 2007 11:15:04 -0600, > John Goerzen wrote: > > > You can see my test case with: > > > > darcs get '--tag=glasgow ml' http://darcs.complete.org/hsh > > ghc -fglasgow-exts --make -o test2 test2.hs > > I get an erro when

Re: ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread Jeremy Shaw
At Wed, 28 Feb 2007 11:15:04 -0600, John Goerzen wrote: > You can see my test case with: > > darcs get '--tag=glasgow ml' http://darcs.complete.org/hsh > ghc -fglasgow-exts --make -o test2 test2.hs I get an erro when I use that darcs command-line, and test2.hs does not appear to be in the direct

ghci and ghc -threaded broken with pipes & forking

2007-02-28 Thread John Goerzen
Hi, I've been hitting my head against a wall for the past couple of days trying to figure out why my shell-like pipeline code kept hanging. I found fd leakage (file descriptors not being closed), which disrupts EOF detection and can lead to deadlocks. I just couldn't find the problem. I finally

Re: How to debug a segfault.

2007-02-28 Thread David Brown
David Brown wrote: > Hmm. I recompiled 'zlib' with some extra tracing and now the problem > doesn't happen. Even without the tracing it is fine. Must have been > something wrong with the compiled library. Scary. But, everything is > working fine now. I figured out what the problem is. I've

Re: How to debug a segfault.

2007-02-28 Thread David Brown
David Brown wrote: > I discovered it isn't just x86, but appears to be this particular > machine. My other machines work fine. There might be a library > difference between the machines, or something like that. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -121

Re: How to debug a segfault.

2007-02-28 Thread David Brown
Simon Marlow wrote: > David Brown wrote: > >> 0x080b45b8 in s2EI_info () > > Fortunately I wrote a wiki page on just this subject, mainly so that > I can say RTFM :-) After reading the FM, if you're still having > difficulties then post a followup and we'll try to help if we can. > > http:/

TFP 2007: Last Call for Participation

2007-02-28 Thread TFP 2007
Dear Colleagues, The deadline to register for TFP 2007 is quickly approaching. You may register at: http://cs.shu.edu/tfp2007/registration.html . Also, please be advised that the deadline to make hotel reservations at the guaranteed rate for TFP 2007 participants is also quickly approaching. Ho

Re: How to debug a segfault.

2007-02-28 Thread Matthias Neubauer
Simon Marlow <[EMAIL PROTECTED]> writes: > Fortunately I wrote a wiki page on just this subject, mainly so that I > can say RTFM :-) After reading the FM, if you're still having > difficulties then post a followup and we'll try to help if we can. > >http://hackage.haskell.org/trac/ghc/wiki/De

Re: How to debug a segfault.

2007-02-28 Thread Simon Marlow
David Brown wrote: I'm developing a program with GHC-6.6. I've been on amd64, and haven't had problems, but now when I run the program on on x86 (after cleaning and recompiling), I'm getting a segfault. gdb isn't very helpful at all: Program received signal SIGSEGV, Segmentation fault.

Re: using a stage1 as a compiler for a later ghc?

2007-02-28 Thread Simon Marlow
Isaac Dupree wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm on a system with main ghc = 6.4.2. I've built a ghc 6.6 stage1. Is there any problem using that ghc-inplace as a compiler for GHC HEAD? (which is done e.g. by ./configure - --with-ghc=/home/isaac/hardly-mine-at-all/build/ghc-6