- Glasgow-haskell-users

RE: 5.04 ?
by Simon Peyton-Jones 01 Oct '01

01 Oct '01

Simon is going to look into the storage management bug. I believe that it does not show up if you do not use the (new) compacting garbage collector, correct? We'll produce 5.02.1 when we know what the cause is; meanwhile, can you just switch off compacting GC? (Admittedly, that would be easier to do if you could specify some run-time flags at link time, which is something we've been thinking about.) Simon | -----Original Message----- | From: S.D.Mechveliani [mailto:mechvel@math.botik.ru] | Sent: 29 September 2001 13:46 | To: glasgow-haskell-users(a)haskell.org | Cc: Simon Marlow | Subject: 5.04 ? | | | Dear GHC, | | I have tested ghc-5.02 | on various examples of computer algebra, with -O too. | | All tests are all right, | | except it shows a bug in memory management (Simon Marlow | wrote of), visible in subtly chosen cases. | | The impression is that 5.02 saves much memory and gains performance | in situations involving garbage collections (most practicable case). | | But due to the above bug, would 5.04 appear soon as a stable | release? | For I need to mention some newest stable GHC release in DoCon | program documentation. | | Regards, | | ----------------- | Serge Mechveliani | mechvel(a)botik.ru | | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users(a)haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-| haskell-users |

1 0

5.04 ?
by S.D.Mechveliani 29 Sep '01

29 Sep '01

Dear GHC, I have tested ghc-5.02 on various examples of computer algebra, with -O too. All tests are all right, except it shows a bug in memory management (Simon Marlow wrote of), visible in subtly chosen cases. The impression is that 5.02 saves much memory and gains performance in situations involving garbage collections (most practicable case). But due to the above bug, would 5.04 appear soon as a stable release? For I need to mention some newest stable GHC release in DoCon program documentation. Regards, ----------------- Serge Mechveliani mechvel(a)botik.ru

1 0

Re: enormous executable
by S.D.Mechveliani 29 Sep '01

29 Sep '01

Willem Robert van Hage <wrvh(a)xs4all.nl> writes > [..] > So I tried a simple hello world example exactly like the one > I saw somewhere on the GHC pages that compiled to a binary of 6kb > and I was surprised to see that even after stripping the binary > it still takes up 140kb. > > -rwxr-xr-x 1 willem users 201453 Sep 29 09:55 hello > -rw-r--r-- 1 willem users 51 Sep 29 09:54 hello.hs > -rw-r--r-- 1 willem users 1468 Sep 29 09:55 hello.o It shows that source program takes 51 bytes, compiled object program - 1468 bytes. This is not mauch. Probably, the executable hello is 1000 times larger than object one because some piece of library (including binary code for outputting a string) is linked to it. In small user programs the library code is usually the larger part. In large user programs, it will be the smaller part. Regards, ----------------- Serge Mechveliani mechvel(a)botik.ru

2 1

compiling hmake
by Colin Paul Adams 29 Sep '01

29 Sep '01

Can anyone tell me what options to pass to configure when trying to compile hmake with ghc 5.02? -- Colin Paul Adams Preston Lancashire

1 0

Telling ghc where to start
by George Russell 28 Sep '01

28 Sep '01

There are various reasons why one might have a Haskell file which doesn't have the expected "Module.hs" filename, in particular when putting ghc into some larger system which does its own thing with files. I may well want this as part of UniForM in the next few months. However ghc doesn't provide anyway support for this, and while you could create a symbolic link with a name ghc approves of to the real file, that seems somewhat messy. gcc has an option which allows you to specify that the input is, say, a C program (even though it's called "hello.txt") but it's rather messy and might take too long to implement. I suggest instead a new option called -virtual-name or something similar, so that ghc -virtual-name Module.hs /blah/horrible932 will compile the contents of /blah/horrible932, but treat it as if it were called "Module.hs".

1 0

Happy 1.11 InstallShield released
by Reuben Thomas 28 Sep '01

28 Sep '01

A Happy 1.11 InstallShield is now available (including the post hoc bug fix!). -- http://sc3d.org/rrt/ | competent, a. underpromoted

1 0

RE: Non blocking versions of hGetBuf and hPutBuf
by Simon Marlow 28 Sep '01

28 Sep '01

> Are they removed in GHC-5.02? Yes, I'm afraid so. I can implement them again for the new I/O library if necessary, but would it be possible for you to use the Posix library instead? Cheers, Simon

1 0

Why have file names with 3 components?
by George Russell 28 Sep '01

28 Sep '01

This looks like a bug, but please don't change it! If you have a file A.blah.hs containing a module A, ghc5.02 compiles it, producing A.hi and A.blah.o. I have an application for this, since I have just, for the first time, been reluctantly compelled to introduce recursive modules. Rather than writing .hi-boot files (which might have to be rewritten for ghc5.03) I have instead written .boot.hs files, which yield .hi files, which then get moved to .hi-boot. Thus a module A has two sources, the real source A.hs, but also the source for the .hi-boot file, A.boot.hs.

2 1

Non blocking versions of hGetBuf and hPutBuf
by Koen Claessen 28 Sep '01

28 Sep '01

Are they removed in GHC-5.02? /Koen

1 0

Re: Exporting a String
by Marcin 'Qrczak' Kowalczyk 28 Sep '01

28 Sep '01

Fri, 28 Sep 2001 08:20:08 +0200, Sven Eric Panitz <sep(a)softwareag.com> pisze: > xs <- peekCString cxs > ys <- peekCString cys > erg <- return (xs++ys) The last line can be written: let erg = xs++ys and you can also directly write (xs++ys) instead of erg below. > newCString erg All OK, except that you leak memory. This string is allocated using malloc and should be freed using free when no longer needed (either C free or Haskell free). > //calling Haskell function > test=cAppend("the world"," is my oyster"); > > //printing its result > printf("%s\n", test); And then: free(test); BTW, there is less boilerplate (no startupHaskell etc.) when the main program is in Haskell instead of C (of course sometimes this is not what we want). -- __("< Marcin Kowalczyk * qrczak(a)knm.org.pl http://qrczak.ids.net.pl/ \__/ ^^ SYGNATURA ZASTÊPCZA QRCZAK

1 0