Tue Aug 26 11:54:34 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Add a test for "bad flag" errors
M ./tests/ghc-regress/parser/should_fail/all.T +1
A ./tests/ghc-regress/parser/should_fail/read044.hs
A ./tests/ghc-regress/parser/should_fail/read044.stderr
View patch online:
http://dar
Tue Aug 26 11:32:23 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Fix some tests: T2310, T2486, FD2
M ./tests/ghc-regress/rename/should_fail/T2310.hs -1 +1
M ./tests/ghc-regress/simplCore/should_run/T2486.stderr -4 +4
M ./tests/ghc-regress/typecheck/should_compile/FD2.hs -1 +1
View pat
Tue Aug 26 11:56:41 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Give locations of flag warnings/errors
M ./compiler/basicTypes/SrcLoc.lhs +4
M ./compiler/ghci/InteractiveUI.hs -4 +4
M ./compiler/main/CmdLineParser.hs -12 +24
M ./compiler/main/DriverPipeline.hs -5 +4
M ./compil
Tue Aug 26 11:26:29 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Remove a now-redundant comment
M ./compiler/main/DynFlags.hs -1
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080826182629-3fd76-4104a6be898f3e0df1183c741ebacfba06005360.gz
___
Tue Aug 26 08:56:12 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Separate the static flag parser from the static global variables
This allows us to avoid a module import loop:
CmdLineParser -> SrcLoc -> Outputable -> StaticFlags -> CmdLineParser
M ./compiler/ghc.cabal +1
M ./compiler/m
Tue Aug 26 07:44:52 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Move pprFastFilePath from SrcLoc to Outputable
M ./compiler/basicTypes/SrcLoc.lhs -4
M ./compiler/utils/Outputable.lhs +5
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080826144452-3fd76-64b9f791351ed5c7c7
Simon Peyton-Jones:
| What's the objective here?
For me the objective is to say "make validate" and come back later
to find a list of things that need fixing. Stopping at the *first*
error is unhelpful, because it means there's an hour or two (and
therefore because of other constraints a
Simon Peyton-Jones:
There's been quite a bit of discussion about GHC's build system
recently, and in particular about the use of Cabal. Responding to
that discussion we now have a new plan, described here:
http://hackage.haskell.org/trac/ghc/wiki/Design/BuildSystem
If you've taken a
Tue Aug 26 20:03:50 EDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Fix typo and update shootout name; spotted by Don Stewart
M ./index.html -1 +1
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
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 Tue Aug 26 18:02:05 BST 2008.
checking out
On 26/08/2008, at 13:30, Simon Peyton-Jones wrote:
| E.g., the type below is generated for :DNum, the datacon of a Num
| dictionary.
| At least, this is what :print obtains from a tcLookupDatacon
on :DNum.
|
| :DNum ::(a -> a -> a)
| -> (a -> a -> a)
|
Friends
There's been quite a bit of discussion about GHC's build system recently, and
in particular about the use of Cabal. Responding to that discussion we now
have a new plan, described here:
http://hackage.haskell.org/trac/ghc/wiki/Design/BuildSystem
If you've taken an interest in
On Tue, 2008-08-26 at 14:45 +0100, Simon Marlow wrote:
> > We can hack it for the special case of base, or try and be slightly more
> > general and not complain when the two versions that get pulled in
> > directly depend on each other. In general there's no simple way for
> > Cabal to know if usi
Duncan Coutts wrote:
On Tue, 2008-08-26 at 09:40 +0100, Simon Marlow wrote:
Claus Reinke wrote:
Of course, warnings like
Configuring html-1.0.1.1...
Warning: This package indirectly depends on multiple versions of the
same
package. This is highly likely to cause a compile failure.
On Tue, 2008-08-26 at 09:40 +0100, Simon Marlow wrote:
> Claus Reinke wrote:
>
> > Of course, warnings like
> >Configuring html-1.0.1.1...
> >Warning: This package indirectly depends on multiple versions of the
> > same
> >package. This is highly likely to cause a compile failure.
> >
Tue Aug 26 05:21:21 PDT 2008 [EMAIL PROTECTED]
* Fix flaggery for RULES (cf Trac #2497)
This patch executes the plan described in the discussion in Trac #2497.
Specficially:
* Inside a RULE, switch on the forall-as-keyword in the lexer,
unconditionally. (Actually this is
Wed Aug 20 06:29:11 PDT 2008 Simon Marlow <[EMAIL PROTECTED]>
* always treat 'forall' and '.' as reserved keywords inside RULES pragmas
M ./compiler/parser/Lexer.x -12 +21
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080820132911-12142-18402efce334713fec4fbbb6956ef26ef5
Fri Aug 22 06:34:27 PDT 2008 [EMAIL PROTECTED]
* Fix a nasty float-in bug
This is a long-standing bug in FloatIn, which I somehow managed to
tickle (it's actually surprisingly hard to provoke which is why
it has not shown up before).
The problem was that we had a specialisation li
Thu Aug 21 05:31:00 PDT 2008 [EMAIL PROTECTED]
* Make rule printing wobble less
a) When generating specialisations, include the types in the name
of the rule, to avoid having rules with duplicate names.
(The rule name is used to put rules in canonical order for
fingerprinting
| E.g., the type below is generated for :DNum, the datacon of a Num
| dictionary.
| At least, this is what :print obtains from a tcLookupDatacon on :DNum.
|
| :DNum ::(a -> a -> a)
| -> (a -> a -> a)
| -> (a -> a -> a)
|
Hi Ben,
On Tue, Aug 26, 2008 at 01:21:25PM +1000, Ben Lippmeier wrote:
>
>
> -- it runs for a while then gives:
>
>
> checking for strspn... yes
> updating cache ./config.cache
> creating ./config.status
>
While modifying :print to further* show the representation of things,
I got stuck at reconstructing dictionaries and the data constructors
generated by GHC.
For the purpose of experimenting I am using a simple GADT to embed a
dictionary in a value:
data Dict a where
DictEq :: Eq x => x
Claus Reinke wrote:
Of course, warnings like
Configuring html-1.0.1.1...
Warning: This package indirectly depends on multiple versions of the
same
package. This is highly likely to cause a compile failure.
package html-1.0.1.1 requires base-3.0.3.0
package unique-0.1 requires ba
| What's the objective here?
For me the objective is to say "make validate" and come back later to find a
list of things that need fixing. Stopping at the *first* error is unhelpful,
because it means there's an hour or two (and therefore because of other
constraints a day or two) between itera
Build results:
fast486 stable: fail (failed darcs)
kgardas stable: fail (failed stage1)
malcolm stable: fail (failed darcs)
mnemosyne x86-64 Gentoo stable: pass
x86 Windows stable fast:pass pass pass pass
Old unexpected test failures:
Ty
Build results:
x86 Windows head fast: pass pass pass pass
tnaur PPC OSX head 2:pass
x86-64 Linux head unreg: fail (failed darcs)
Dropping unexpected test passes reports from builders not seen in 7 days:
malcolm head
Dropping unexpected test failures reports from builders not seen in 7
26 matches
Mail list logo
