RE: ANNOUNCE: GHC vesrion 5.04.3 released
Actually, I find it difficult to extract the sometimes drastic differences between releases from that document (just one example: does this release include last week's bugfixes in the Network module?). How do I find out about the various bugfixes between releases, to decide whether or not to upgrade (and whether or not upgrading will help with specific problems)?
After all, the reason for patchlevel releases is that you've fixed some bugs, so why be so secretive about what these fixes are?-)
The release notes doesn't contain bugfixes, and the reason we don't have a list of them is because I'm too lazy to keep track of what bug fixes have been merged in, sorry! The Network fix wasn't merged in (just too late). Ok, I'll take a look at the diffs and summarise the fixes... here goes: - Literal strings could be duplicated sometimes - fixes for deriving Eq/Enum on large datatypes in GHCi - -no-hs-main has a sensible meaning in --make mode now (it forces linking even if there's no Main) - Fix for avoiding recompilation when there are stub files around (didn't pick up the stubs properly before) - Fixes for FFI decls containing type variables - MacOS X fixes for GHCi - Filenames with spaces don't cause problems in GHCi now - GHCi doesn't get confused if your code installs a signal handler for ^C - -pgmL now works as advertised - specifying filenames without the trailing .hs/.lhs works again in --make and GHCi. - Fix for "class ops that do not introduce foralls" (a cause of crashes with certain kinds of class methods). - Fix a crash when a class op is used as a record selector - Fix for deriving on records with fields with names with leading underscores. - Fixes for passing/returning FunPtr in the FFI - hsc2hs works in a binary distribution - Fixes for crashes in the biographical and retainer profilers. - Some signals were inadvertently blocked by the RTS - Uninitialised variable in the storage manager causes crashes - Fix for hp2ps -c - hsc2hs should now work on Windows - Fix off-by-one in Data.PackedString.splitWithPS - uninitialised elements in UArrays are now filled with zero. - Integer divide by zero is now consistently a catchable exception (previously it could just result in SIGFPE). - Fix for terminal buffering on Solaris - System.Console.GetOpt fixes - Fix for converting Integer to Int64/Word64 - Network.accept doesn't fail if the host fails to reverse-lookup. Cheers, Simon
I notice the release notes say a few architectures should be possible to port to, in particular AIX/POWER. How possible is that, exactly? Has anybody done it with any success? Alternatively, is there any alternative Haskell compiler (I guess that would be NHC?) that works for this architecture? And does GHC or anybody else support 64bit address spaces? -kzm -- If I haven't seen further, it is by standing in the footprints of giants
I notice the release notes say a few architectures should be possible to port to, in particular AIX/POWER. How possible is that, exactly? Has anybody done it with any success? Alternatively, is there any alternative Haskell compiler (I guess that would be NHC?) that works for this architecture?
And does GHC or anybody else support 64bit address spaces?
GHC worked on Alpha recently (5.02.x), so our 64 bit support should be up to scratch. Check the porting section of the GHC building guide for information on porting: the bottom line is that there are various levels of porting, from a basic unregisterised port up to a full port with GHCi and a native code generator. http://www.haskell.org/ghc/docs/latest/html/building/sec-porting-ghc.htm l Cheers, Simon
There seems to be a 2Gb file limit when using GHC, I don't suppose there's any way to get around it, apart from manually splitting the contents over several smaller files? (I'm even unable to use writeFile on a file that's larger than 2Gb) -kzm -- If I haven't seen further, it is by standing in the footprints of giants
What OS? Some (like solaris, I believe) have 2gb limits on files. -- Hal Daume III | hdaume@isi.edu "Arrest this man, he talks in maths." | www.isi.edu/~hdaume On 8 May 2003, Ketil Z. Malde wrote:
There seems to be a 2Gb file limit when using GHC, I don't suppose there's any way to get around it, apart from manually splitting the contents over several smaller files? (I'm even unable to use writeFile on a file that's larger than 2Gb)
-kzm -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Hal Daume III
What OS? Some (like solaris, I believe) have 2gb limits on files.
Linux. No apparent limit here. (I.e. I had no problem constructing the file, only constructing it -- or for that matter, accessing it or overwriting it -- inside Haskell) -kzm -- If I haven't seen further, it is by standing in the footprints of giants
ketil@ii.uib.no (Ketil Z. Malde) writes:
I notice the release notes say a few architectures should be possible to port to, in particular AIX/POWER. How possible is that, exactly? Has anybody done it with any success? Alternatively, is there any alternative Haskell compiler (I guess that would be NHC?) that works for this architecture?
We fixed some small configuration issues with building nhc98 on a POWER3/AIX machine in Feb 2001. I have no reason to think that anything has broken since then. The Power architecture is somewhat similar to the PowerPC architecture as used on the Mac, for which GHC does have support.
And does GHC or anybody else support 64bit address spaces?
nhc98 definitely does not, and it would be a significant amount of work to make it possible. Regards, Malcolm
Alternatively, is there any alternative Haskell compiler (I guess that would be NHC?) that works for this architecture?
If Hugs doesn't work on your machine, please report it as a bug. [Hmmm, ok, let me restrict that to machines with at least 32-bit Ints, and at least 1Mb of memory.]
And does GHC or anybody else support 64bit address spaces?
I think Hugs does but it would be worth checking explicitly. I'd pay particular attention to the Ptr type in the ffi libraries. -- Alastair Reid alastair@reid-consulting-uk.ltd.uk Reid Consulting (UK) Limited http://www.reid-consulting-uk.ltd.uk/alastair/
participants (5)
-
Alastair Reid -
Hal Daume III -
ketil＠ii.uib.no -
Malcolm Wallace -
Simon Marlow