Build description = STABLE on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Thu Mar 11 18:10:01 GMT 2010.
checki
Build description = STABLE on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx
Nightly build started on cam-04-unx at Thu Mar 11 19:10:02 GMT 20
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Thu Mar 11 18:00:01 GMT 2010.
checking out
Build description = HEAD on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Thu Mar 11 19:00:01 GMT 2010.
**
igloo-windows, build 3
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/igloo-windows/3.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting | Success
Parsers are relevant to *a* compiler, but this discussion is not
specific to the compiler GHC. GHC has a working and efficient enough
parser for Haskell and all the GHC-supported extensions.
This list is for discussing issues specific to GHC *development*.
Other matters should therefore be discus
simonmar-win32-stable, build 2
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-stable/2.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Failure: 256
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar
You/we are talking about parser performance and parsing libraries in
general, not about GHC development. I agree that this conversation
should continue on haskell-cafe.
On 11 March 2010 16:22, John D. Earle wrote:
> How is it off topic? Am I not following the instructions that were given on
> th
Thu Mar 11 04:06:46 PST 2010 Simon Marlow
* do the throwto tests in a validate run
M ./tests/ghc-regress/concurrent/should_run/all.T -5 +5
View patch online:
http://darcs.haskell.org/testsuite/_darcs/patches/20100311120646-12142-287f6544d42bf4daa74938edf0d549cf2fcf6d5a.gz
___
Thu Mar 11 04:02:31 PST 2010 Simon Marlow
* Add some tortuous throwTo tests
M ./tests/ghc-regress/concurrent/should_run/all.T +5
A ./tests/ghc-regress/concurrent/should_run/throwto001.hs
A ./tests/ghc-regress/concurrent/should_run/throwto002.hs
A ./tests/ghc-regress/concurrent/
Thu Mar 11 04:37:05 PST 2010 Simon Marlow
* Fix a couple of bugs in the throwTo handling, exposed by conc016(threaded2)
M ./rts/HeapStackCheck.cmm -2 +6
M ./rts/RaiseAsync.c -8 +11
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20100311123705-12142-f8262883d6403581a698
How is it off topic? Am I not following the instructions that were given on
the GHC Developer Wiki?
--
From: "Ian Lynagh"
Sent: 11 Thursday March 2010 0850
To: "John D. Earle"
Cc: "cvs-ghc"
Subject: Re: Fast Haskell Parser
Hi all,
This discu
Hi all,
This discussion is off-topic here. Can you please take it to the
haskell-cafe list?
Thanks
Ian
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Thank you very much for the link Thomas. It does give some clarity on the
matter. None of the combinator parsers performed well including Attoparsec.
This is apparent when you look at the numbers next to the bar graph. C took
roughly half as long as Attoparsec. Attoparsec, however, is sufficient
igloo-windows, build 2
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/igloo-windows/2.html
darcs checkout | Failure: 1
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/igloo-windows/2.html
___
Cvs-ghc mailing list
No, it's not lazy vs. strict. Parsec's "try" switches the default
LL(1) parser to an LL(N) parser. Happy is always LALR(1), which is
somewhere in the middle. ReadP is always LL(N) but is efficient by
using a breadth-first search instead of depth-first search. The
efficiency of ReadP depends on
Simon Marlow: Personally I find Parsec and the other parser combinator
libraries quite difficult to use when it comes to deciding where to put
'try'; ReadP is the exception here, because it does general backtracking and
doesn't make you decide where to use 'try'.
John D. Earle: I bet this has
igloo-windows, build 1
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/igloo-windows/1.html
darcs checkout | Failure: 2
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/igloo-windows/1.html
___
Cvs-ghc mailing list
Simon,
Happy is a domain specific language (DSL) and as such it would likely make
stating the problem simpler. A Turing complete language will admit
pathological cases and convoluted expression, both of which are forms of
pathology as automation is concerned. So what you said makes sense to me
simonmar-win32-head, build 4
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-head/4.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Failure: 256
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32
Thu Mar 11 01:57:44 PST 2010 Simon Marlow
* Use message-passing to implement throwTo in the RTS
This replaces some complicated locking schemes with message-passing
in the implementation of throwTo. The benefits are
- previously it was impossible to guarantee that a throwTo from
Thu Mar 11 01:36:32 PST 2010 Simon Marlow
* fix bug in discardTasksExcept() that broke forkProcess
M ./rts/Task.c -2 +3
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20100311093632-12142-97f1381e4cdb1099fd4f0e327ab9605a4acd55fb.gz
Mon Nov 23 03:04:16 PST 2009 Simon Marlow
* disable a false assertion, add a comment to explain why
M ./rts/sm/Scav.c -3 +5
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20091123110416-12142-54ef80f2a44599972d13a94ca42d54bb3773e153.gz
Simon, one of your perhaps?
=> spec-inline(optc) 595 of 2470 [0, 0, 0]
cd ./simplCore/should_compile &&
'/64playpen/simonmar/validate/bindisttest/install dir/bin/ghc'
-fforce-recomp -dcore-lint -dcmm-lint -no-user-package-conf
-dno-debug-output -c spec-inline.hs -O -fvia-C -O2 -ddump-simpl
On 11/03/2010 01:25, John D. Earle wrote:
Hi, Ben! Thanks for the input. I went to the Parsec and Attoparsec
parser links. Attoparsec was new to me. From the Parsec link:
Combinator parsers are written and used within the same programming
language as the rest of the program. The parsers are firs
simonmar-win32-stable, build 1
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-stable/1.html
darcs checkout | Success
create mk/build.mk | Success
get subrepos | Failure: 1
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-w
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Wed Mar 10 18:00:02 GMT 2010.
checking out
Build description = STABLE on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Wed Mar 10 18:10:02 GMT 2010.
checki
On 11/03/2010 00:49, David Terei wrote:
> r98212 | lattner | 2010-03-11 11:22:57 +1100 (Thu, 11 Mar 2010)
> add support, testcases, and dox for the new GHC calling
> convention. Patch by David Terei!
The new calling convention in LLVM needed by GHC has just been
committed! Unfortunately it m
29 matches
Mail list logo