[[project @ 2001-03-22 12:12:23 by simonmar] simonmar**20010322121223 Move the bug reporting section earlier, and mention the SourceForge bug tracker. Update the release notes. I think I'm just about done in here... ] { hunk ./ghc/docs/users_guide/5-00-notes.sgml 8 - GHCi added + GHCi, the new interactive environment on top of GHC, has + been added (). hunk ./ghc/docs/users_guide/5-00-notes.sgml 12 - flag added + New flag added (). hunk ./ghc/docs/users_guide/5-00-notes.sgml 16 - dynamic vs. static options + The native code generator now supports Sparc in addition + to x86. hunk ./ghc/docs/users_guide/5-00-notes.sgml 20 - NCG support for Sparc + We now make it clear which options can be placed in an + OPTIONS pragma. See . hunk ./ghc/docs/users_guide/5-00-notes.sgml 25 - hsc2hs added + no longer implies + . + + + is no more. + + + and are no more. + + + The concept of “packages” has been + generalised and extended. Packages may be installed or + removed from an existing GHC installation using the new + ghc-pkg tool. See . + + + Initial unicode support: the Char + type is now 31 bits. We don't yet have support for unicode + I/O. + + + now takes an optional numeric + argument indicating the level of verbosity (). has + been removed. + + + Parallel list comprehensions added. + + + Profiling: please use + {-# SCC ".." #-} + rather than _scc_ "...". The latter + will be phased out in due course. + + + A new experimental optimisation, SpecConstr, is turned + on with -O2. + + + Please report bugs using the SourceForge bug + tracker instead of + glasgow-haskell-bugs@haskell.org if + possible. + + + Documentation changes: there's now a useful Flag + Reference section, see . + + + Many, many, bugfixes. + + + + + + New experimental features + + + + A “front panel” for GHC-compiled programs + displays real-time graphs of memory behaviour in a GTK+ + window. You need to recompile the RTS with front panel + support to use this. + + + + + + FFI changes + + + hsc2hs added (). + + + FFI libraries have been updated to the latest proposal + from the FFI task force. Too many changes to list here, see + the docs: . hunk ./ghc/docs/users_guide/5-00-notes.sgml 113 - FFI libraries enhanced, lots of deprecations. + putMVar now blocks if the + MVar is already full. The + PutFullMVar exception no longer exists. A + non-blocking version of putMVar, + tryPutMVar, has been added (). + + + The Integer type now has an instance + of Bits (). + + + Package hssource has been added. It + contains a Haskell 98 abstract syntax, parser, lexer and pretty + printer. No documentation yet. + + + + + + Build system changes + + + + The WithGhcHc setting in + build.mk has been replaced by the + --with-ghc=ghc + option to configure. The new option + must be used if you intend to use + anything except “ghc” to + bootstrap GHC, in order that the build system can figure out + what version of GHC you're using. + + + Source distributions are now made by doing make + distclean in a build tree, instead of requiring a + linked build tree. hunk ./ghc/docs/users_guide/5-00-notes.sgml 158 + Many internal compiler changes: too many to list + here. + + hunk ./ghc/docs/users_guide/5-00-notes.sgml 165 + + We now use GMP 3 instead of GMP 2 for + arbitrary-precision integer support. + hunk ./ghc/docs/users_guide/gone_wrong.sgml 11 -may have found a bug—please report it! See for a -list of things we'd like to know about your bug. If in doubt, send a -report—we love mail from irate users :-! +may have found a bug—please report it! See + for details on how to report a bug and +a list of things we'd like to know about your bug. If in doubt, send +a report—we love mail from irate users :-! hunk ./ghc/docs/users_guide/gone_wrong.sgml 157 - -“What's a `consistency error'?” - - -(These are reported just after linking your program.) - hunk ./ghc/docs/users_guide/gone_wrong.sgml 158 - -You tried to link incompatible object files, e.g., normal ones -(registerised, Appel garbage-collector) with profiling ones (two-space -collector). Or those compiled by a previous version of GHC -with an incompatible newer version. - - - -If you run nm -o *.o | egrep 't (cc|hsc)\.' (or, on -unregisterised files: what *.o), you'll see all the consistency -tags/strings in your object files. They must all be the same! -(ToDo: tell you what they mean…) - - - hunk ./ghc/docs/users_guide/gone_wrong.sgml 269 -This is definitely caused by a bug in GHC. Please report it. +This is definitely caused by a bug in GHC. Please report it (see ). hunk ./ghc/docs/users_guide/gone_wrong.sgml 291 - -How to report a bug in the GHC system - - - -bug reports - - - -Glasgow Haskell is a changing system so there are sure to be bugs in -it. Please report them to -glasgow-haskell-bugs@haskell.org! (However, please -check the earlier part of this section to be sure it's not a known -not-really-a problem.) - - - -The name of the bug-reporting game is: facts, facts, facts. -Don't omit them because “Oh, they won't be interested…” - - - - - - - - -What kind of machine are you running on, and exactly what version of -the operating system are you using? (uname -a or -cat /etc/motd will show the desired information.) - - - - - - - What version of GCC are you using? gcc -v will tell you. - - - - - - - Run the sequence of compiles/runs that caused the offending -behaviour, capturing all the input/output in a “script” (a UNIX -command) or in an Emacs shell window. We'd prefer to see the whole -thing. - - - - - - - Be sure any Haskell compilations are run with a (verbose) -flag, so we can see exactly what was run, what versions of things you -have, etc. - - - - - - - What is the program behaviour that is wrong, in your opinion? - - - - - - - If practical, please send enough source files for us to duplicate the - problem. - - - - - - - If you are a Hero and track down the problem in the -compilation-system sources, please send us patches relative to a known -released version of GHC, or whole files if you prefer. - - - - - - - - - - hunk ./ghc/docs/users_guide/gone_wrong.sgml 301 -report, as outlined in previous sections. +report, as outlined in . hunk ./ghc/docs/users_guide/intro.sgml 214 + + + Reporting bugs in GHC + bugsreporting + + reporting bugs + + + Glasgow Haskell is a changing system so there are sure to be + bugs in it. + + To repot a bug, either: + + + + Go to the SoureForge GHC + page, go to the bugs section, click on + submit, and enter your bug report. You can also + check the outstanding bugs here to make sure it hasn't already + been reported. Or: + + + Email your bug report to + glasgow-haskell-bugs@haskell.org. + + + + + What to put in a bug report + bug reportscontents + + The name of the bug-reporting game is: facts, facts, + facts. Don't omit them because “Oh, they won't be + interested…” + + + + What kind of machine are you running on, and exactly + what version of the operating system are you using? + (on a Unix system, uname -a or cat + /etc/motd will show the desired information.) + + + + What version of GCC are you using? gcc + -v will tell you. + + + + Run the sequence of compiles/runs that caused the + offending behaviour, capturing all the input/output in a + “script” (a UNIX command) or in an Emacs shell + window. We'd prefer to see the whole thing. + + + + Be sure any Haskell compilations are run with a + (verbose) flag, so we can see exactly + what was run, what versions of things you have, etc. + + + + What is the program behaviour that is wrong, in your + opinion? + + + + If practical, please send enough source files for us + to duplicate the problem. + + + + If you are a Hero and track down the problem in the + compilation-system sources, please send us patches relative + to a known released version of GHC, or whole files if you + prefer. + + + + hunk ./ghc/docs/users_guide/using.sgml 1545 - ./a.out +RTS -qP -qp8 - grs2gr *.???.gr > temp.gr # combine the 8 .gr files into one - gr2ps -O temp.gr # cvt to .ps; output in temp.ps - ghostview -seascape temp.ps # look at it! +$ ./a.out +RTS -qP -qp8 +$ grs2gr *.???.gr > temp.gr # combine the 8 .gr files into one +$ gr2ps -O temp.gr # cvt to .ps; output in temp.ps +$ ghostview -seascape temp.ps # look at it! hunk ./ghc/docs/users_guide/using.sgml 1657 -