Re: -ddump-stg code

On 11/16/07, Guilherme Avelino <[EMAIL PROTECTED]> wrote: > Hi, > > I want to use the stg code generated by the ghc with a frontend for my > compiler. I´m using the flags -ddump-stg and -dppr-debug to obtain the STG > informations. However there are some things that I din´t understand. Are > ther

Re: -ddump-stg code

stefanor: > On Fri, Nov 16, 2007 at 05:14:08PM -0300, Guilherme Avelino wrote: > > Hi, > > > > I want to use the stg code generated by the ghc with a frontend for my > > compiler. I´m using the flags -ddump-stg and -dppr-debug to obtain the STG > > informations. However there are some things tha

Re: -ddump-stg code

On Fri, Nov 16, 2007 at 05:14:08PM -0300, Guilherme Avelino wrote: > Hi, > > I want to use the stg code generated by the ghc with a frontend for my > compiler. I´m using the flags -ddump-stg and -dppr-debug to obtain the STG > informations. However there are some things that I din´t understand.

Re: patch applied (ghc): GHCi debugger: added a new flag, -fno-print-binding-contents

An example is worth a thousand words. This is the kind of output we get now at a breakpoint: Stopped at Setup.lhs:24:27-65 _result :: IO () = _ iff :: InstallFlags = _ lbi :: LocalBuildInfo = LocalBuildInfo (InstallDirTemplates (Distribution.Simple.InstallDirs.PathTemplate [...])

patch applied (testsuite): fix this test for case sensitive filenames

Fri Nov 16 05:18:37 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * fix this test for case sensitive filenames M ./tests/ghc-regress/ghci.debugger/scripts/break027.script -1 +1 M ./tests/ghc-regress/ghci.debugger/scripts/break027.stdout -3 +3 ___

Re: validate breaks!

Claus Reinke wrote: ThreadDelay is a perfectly reasonable test: it tests that threadDelay doesn't wait for *less* time than was requested. Clearly something is wrong on your machine with either threadDelay or the way time is measured, but we haven't seen the same symptoms elsewhere so it's har

Re: mingw ghc globbing and getArgs

Claus Reinke wrote: but that does seem to be a bug in ghc-pkg-inplace.hs, so perhaps that should be fixed first, and then we could use '*' instead of '.' (even though it isn't full globbing, '*' is only interpreted at string ends). the problem is not specific to ghc-pkg-inplace, but is shared

Re: mingw ghc globbing and getArgs

So different commands can (and do) have different quoting and globbing semantics. Great huh? it does have its advantages, though. as i'm implementing a package globbing, i'd like to avoid file globbing being applied to these same parameters. We could have a -no-globbing link-time option, but

patch applied (ghc): Improve documentation of data type declarations (Trac #1901)

Fri Nov 16 00:18:41 PST 2007 [EMAIL PROTECTED] * Improve documentation of data type declarations (Trac #1901) M ./docs/users_guide/glasgow_exts.xml -14 +35 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-g

Re: Re[2]: mingw ghc globbing and getArgs

./main '*' -- this does not protect from globbing! "*" works afair. if you want to disable globbing completely, link it with gcc-lib\CRT_noglob.o (at least this works with 6.4-6.6) '*' works for cygwin bash "*" works for win32-self-globbing programs in cmd.exe but how do you protect * from

patch applied (ghc): Improve links from flag reference to the relevant section; and improve doc of RankN flags

Fri Nov 16 06:58:16 PST 2007 [EMAIL PROTECTED] * Improve links from flag reference to the relevant section; and improve doc of RankN flags M ./docs/users_guide/flags.xml -19 +19 M ./docs/users_guide/glasgow_exts.xml -6 +17 ___ Cvs-ghc mailin

patch applied (ghc): FIX Trac #1901: check no existential context in H98 mode

Fri Nov 16 06:56:09 PST 2007 [EMAIL PROTECTED] * FIX Trac #1901: check no existential context in H98 mode M ./compiler/typecheck/TcTyClsDecls.lhs -3 +14 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc

-ddump-stg code

Hi, I want to use the stg code generated by the ghc with a frontend for my compiler. I´m using the flags -ddump-stg and -dppr-debug to obtain the STG informations. However there are some things that I din´t understand. Are there any document where I can find informations about the stg generated?

patch applied (testsuite): small tidyups to thie Makefile

Fri Nov 16 05:19:14 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * small tidyups to thie Makefile M ./timeout/Makefile -5 +8 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc

patch applied (testsuite): 1603 depends on the gcc version, which we can't easily account for, so skip

Fri Nov 16 01:34:28 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * 1603 depends on the gcc version, which we can't easily account for, so skip M ./tests/ghc-regress/numeric/should_run/all.T -1 +1 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://w

patch applied (ghc): Attempt at fixing #1873, #1360

Fri Nov 16 07:21:48 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * Attempt at fixing #1873, #1360 I think I figured out a reasonable way to manage the GHCi context, comments welcome. Rule 1: external package modules in the context are persistent. That is, when you say 'import Data.Ma

patch applied (ghc): FIX BUILD (with GHC 6.2.x): update .hi-boot file

Fri Nov 16 02:12:27 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * FIX BUILD (with GHC 6.2.x): update .hi-boot file M ./compiler/parser/HaddockLex.hi-boot-6 -2 +2 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/c

patch applied (ghc): Wibble to fix Trac #1901 (shorten messsage slightly)

Fri Nov 16 07:03:41 PST 2007 [EMAIL PROTECTED] * Wibble to fix Trac #1901 (shorten messsage slightly) M ./compiler/typecheck/TcTyClsDecls.lhs -1 +1 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc

patch applied (testsuite): update to test #1873, #1360

Fri Nov 16 07:59:48 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * update to test #1873, #1360 A ./tests/ghc-regress/ghci/prog009/A3.hs M ./tests/ghc-regress/ghci/prog009/ghci.prog009.script -5 +15 M ./tests/ghc-regress/ghci/prog009/ghci.prog009.stderr +2 M ./tests/ghc-regress/ghci

patch applied (ghc): use "ghc-pkg latest --global" instead of "ghc-pkg list --simple-output"

Fri Nov 16 04:20:18 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * use "ghc-pkg latest --global" instead of "ghc-pkg list --simple-output" The former now does the right thing: it uses the global database only, and picks the most recent package with the given name. M ./compiler/Makefile -1

Re[2]: mingw ghc globbing and getArgs

Hello Simon, Friday, November 16, 2007, 12:31:05 PM, you wrote: >> the problem is not specific to ghc-pkg-inplace, but is >> shared by all ghc mingw programs using getArgs: >> >>./main '*' -- this does not protect from globbing! "*" works afair. if you want to disable globbing completely, l

patch applied (ghc): Disallow installing packages whose names differ in case only.

Fri Nov 16 04:11:53 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * Disallow installing packages whose names differ in case only. --force overrides. Requested by Duncan Coutts, with a view to treating package names as case-insensitive in the future. M ./utils/ghc-pkg/Main.hs -4 +12 _

patch applied (testsuite): Add -XExistentialQuantification flag (should have been there all along)

Fri Nov 16 07:43:37 PST 2007 [EMAIL PROTECTED] * Add -XExistentialQuantification flag (should have been there all along) M ./tests/ghc-regress/th/TH_genEx.hs -1 +1 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listin

patch applied (ghc): Change the command-line semantics for query commands

Fri Nov 16 05:20:46 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * Change the command-line semantics for query commands From the help text: Commands that query the package database (list, latest, describe, field) operate on the list of databases specified by the flags --user, --

patch applied (ghc): FIX #1828: installing to a patch with spaces in

Thu Nov 15 07:57:47 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * FIX #1828: installing to a patch with spaces in We have to pass the path to gcc when calling windres, which itself might have spaces in. Furthermore, we have to pass the path to gcc's tools to gcc. This means getting the qu

Re: [nightly] 15-Nov-2007 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com)

GHC Build Reports wrote: parser/HaddockParse.hs:9: Failed to find interface decl for `HaddockLex.String' from module `HaddockLex' parser/HaddockParse.hs:9: Failed to find interface decl for `HaddockLex.String' from module `HaddockLex' stage1/parser/HaddockLex.hi-boot-6:5: t

patch applied (ghc): on Windows, install to a directory with spaces (test for #1828)

Thu Nov 15 07:53:27 PST 2007 Simon Marlow <[EMAIL PROTECTED]> * on Windows, install to a directory with spaces (test for #1828) M ./bindisttest/Makefile -2 +11 M ./mk/config.mk.in -2 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.has

Daily report for head

Build results: x86-64 Linux head: pass x86 Windows head: pass x86 Windows head fast: pass pass pass pass pass pass kahl G5 Gentoo Linux head: pass x86-64 Linux head unreg: pass Old unexpected test passes: 1603 3 x86 Windows head New unexpected test failures: 167

Daily report for stable

Build results: gabor stable: pass kahl G5 Gentoo Linux stable:pass mnemosyne x86-64 Gentoo stable: pass tnaur PPC OSX stable: pass tnaur x86 Linux stable: fail (failed stage1) x86 Windows stable fast:pass pass pass pass pass pass x86-64 Linux stable: