Advised Windows users to read the Windows installation notes for GHC before
trying to build anything.

Pointed out that Windows users should read the GHC installation guide before
trying to build anything.

increase the repeat count; this bug is pretty fragile

Add test for handle finalization bug, fixed in
  1.60      +1 -2      fptools/ghc/lib/std/PrelHandle.lhs
  1.15      +4 -10     fptools/ghc/lib/std/PrelIO.lhs

Fix bug reported by Hannah Schroeter: reading a file lazily using
hGetContents and then closing it using hClose can cause the program to
fall over with a deadlock.

The reason is that when closing the file in lazyRead{Block,Line,Char},
we set the foreign object in the handle to nullFile__, which causes
the finalizer to run (at some point in the future).  The finalizer
takes the MVar in the handle, frees the contents, but never puts the
MVar back.  hClose then tries to take the MVar, and deadlocks.

The solution is not to set the foreign object to nullFile__ in the
first place; I'm not sure why it was done this way, and in fact it
leads to a memory leak.  hClose itself has a similar problem, leading
to a leak of the fileObject.

giving the version number when asked for is NOT an error, therefore
output now goes to stdout (cf. Coding Standards)

update documentation to reflect changes in the format of a package spec.

Sigh, change the package definition again.  We weren't making a
distinction between libraries which need a suffix tag
(eg. libHSstd_p), and those that don't (eg. libHSstd_cbits).

The package spec now has two components for libraries, hs_libraries
(tagged) and extra_libraries (untagged).  The ordering of these
components is important: we specify that hs_libraries are linked
before extra_libraries.  This sounds problematic if you want to link
some plain C libraries before some Haskell libs, but in these cases it
should be possible to create separate packages for the two libs and
specify the dependencies explicitly.

Some changes to the way FFI decls are handled:

  - a foreign export dynamic which returns a newtype of
    an Addr now works correctly.  Similarly for foreign label.

  - unlifted types are not allowed in the arguments of a foreign
    export.  Previously we generated incorrect code for these cases.

Newtypes in FFI declarations now work everywhere they should, as far
as I can see.

These changes will be backported into 4.08.1.

Strictfp-like behaviour is the default now, which can be switched off
via -fexcess-precision. (Has anybody a better name for this option?)

Fix EXTINFO_RTS.

Add EXTINFO_RTS and use it (same as EXTFUN_RTS for info tables).

Changed ERTSF_ to EXTFUN_RTS.

Removed ERTSF_ and used EXTFUN_RTS instead, which does the same thing.

Make sure we *don't* try to make hsc_dll (as it will be identical to hsc).

Add dll as a fully-fledged way.

Make gmp.dll in DLL_PEN.

Make sure DLL_NAME only has DLL_PEN prepended if DLL_NAME has already been
set, i.e. a DLL is really to be built.

What's the story, Rory?

   My name's not Rory. Owing to circumstances not fully understood, the RTS
   used to work DLLized, even though it was largely broken. Unfortunately,
   this was recently fixed.

What used to happen?

   The EF_ macro from StgMacros.h was used to refer to primops &c.

Why was this a Bad Thing?

   Because you need to use EDF_ when building with DLLs.

What was the result?

   primops such as divExactInteger were compiled as _divExactInteger, rather
   than __imp__div_Exact_Integer, so they didn't refer to the DLL routines.

How on earth did it work?

   I'm not sure, but somehow the code for the relevant routines got linked
   into the import libraries (e.g. libHSrts_imp.a), and were thus linked
   statically into the final binary.

So that explains why the import libraries (supposedly just containing stubs)
were larger than the DLLs they were stubbing, or the static libraries, for
that matter?

   Perhaps.

Golly!

   Indeed.

What caused this code leakage?

   That's what I don't know. Perhaps a bug in the Cygwin DLL-building tools?
   I've upgraded from B20.1 to 1.1 recently.

So, what's the hack, Mac?

   My name's not Mac. I added a new macro, ERTSF_, which uses DLL_IMPORT_RTS
   to make sure that the Right Thing is always done (because you mustn't
   make DLL references to RTS routines when compiling the RTS).

Thanks for the chat, Matt!

   <punch>

4.07->4.08

Fixed a version-o.

> => >

Updated instructions for Windows install to reflect reality as of v4.08.

Added -dll option for dll way, now a proper way.

Target dlls directly into DLL_PEN so that they don't get rebuilt all the time.

Gave driver access to bash for running system calls under Windows by writing
command out to a temp file, then sending that as the argument to "sh -". Sigh.
This is #ifdefed on mingw32_TARGET_OS; saner OSs just use system as normal.

Stop doing all system calls via "sh -c", as this messed up quoting.

oops, ghc-inplace ain't an EXE.

Added a few EXE_SUFFIXes to get the driver going on Windows.

Changed ExeSuffix to exeext (which is what configure.in actually calls it).

remove hscpp

Add $(EXE_SUFFIX) to hp2ps and unlit

Move dlls to $(DLL_PEN) after generation.

Move DLLs to $(DLL_PEN) after generation.

Arrange that type signatures that have no "parent" signatures
work right.  For example

	   module A
	      f :: Int -> Int

The panic in RnEnv.lookupBndrRn becomes an error message.  Also
RnBinds.rnTopMonoBinds and rnMonoBinds were wrongly ignoring all
signatures altogether if there were no bindings!

fix finding of the usage message (again).

Add comment

Add type-sig test

Holding pen for dlls to stop them getting in the way of pre-compiled
dynamic programs.

Remove dead code: checkConstraints and univErr