GitLab

Add comment about Ctrl-C/Ctrl-Break issue

Support for Ctrl-C on Windows.

This works fine in a cmd.exe shell, but in a Cygwin bash shell you
have to press Ctrl-Break to get an interrupt.  There appears to be a
long thread on the cygwin mailing list back in 2002 about this, but
life is probably too short to investigate further.

  http://www.cygwin.com/ml/cygwin/2002-01/msg00163.html

Sanity check when configuring for mingw32: make sure that $CC is a
mingw gcc before proceeding.

--with-gcc: export the CC environment variable, so the setting gets
picked up by sub-configures.  Perhaps we should be advising people to use

  CC=c:/mingw/bin/gcc ./configure

because that works for all configure scripts, not just the top level one.

Background:

 - We want --with-gcc to do the right thing, because we don't want
   to require Cygwin users to put c:/mingw/bin first on their
   path: that would break their Cygwin environment.

 - The build system should work with *no* gcc on your PATH, as long
   as you use --with-gcc (equivalently, CC=... ./configure).

Darn!  Forgot this commit, which killed the nightly build

Comments only

Make ghc/lib/compat/Compat/Directory.hs use the C function
	__compat_long_path_size, rather than
	__hscore_long_path_size, as the libraries/ version does
And make ghc/lib/compat/cbits/directory.c define it.

In this way we avoid spurious duplicate-symbol errors when we
compile GHC with ghc6.2.1 etc.

Tidy the type of an interactively-bound Id before adding
it to the environment.  Generally speaking, top level
environments are assumed to be in tidied form, so we
don't tidy the types before printing.

comment

Comments only

stg_sel_##offset##_upd_entry: the ENTER() here is unnecessary, because
we know the closure in R1 will evaluate to a constructor, so we can
save some time by just entering it directly.

Undo bogus 1.4 commit

First commit for new Cmm code generation (branch)

Comments and asserts only

Fix bug #1073501: checkProddableBlock: invalid fixup in runtime linker

The bug manifested when trying to load an object with debugging info
(compiled with gcc -g) into GHCi.

The problem was that the object loader was ignoring the sections
containing debugging info, but then it was later trying to do
relocations for those sections, and its own sanity checking code
correctly detected that the relocations were in unknown parts of the
object file.

The fix is to ignore relocations whose target section isn't one of the
sections that we're interested in, using the same test in both cases
(the code to test section kind has been extracted).  The code could
probably benefit from more refactoring: it looks like the list of
sections we build up in the first phase isn't even used in the second
phase, instead we traverse the section table in the image again.  This
looks like cruft leftover from when the GC used to check whether an
address was in text or data space.

deleteThread: don't attempt to delete threads blocked in foreign calls.

Prevent any intermediate file deletion using

  .SECONDARY:

and remove now-unnecessary .PRECIOUS and .SECONDARY targets.
Suggestion from Ashley Yakeley.

---------------------
	Bug in specialisation
	---------------------

Laszlo managed to get a function like this:

	foo :: Enum a => (# a, Int #)

The specialiser specialised it, resulting in an unboxed tuple
binding, which Lint objected to.

This commit adds a dummy argument to the specialised function, 
very like the case for strictness analysis.  For example, at
type Char we'd get

	foo_char :: State# RealWorld -> (# Char, Int #)
 	foo_char = \_ -> ...

We use a State# type because it generates no argument-passing code 
at runtime.  (We should really have some other void type for this 
purpose, because State# is misleading, but this way avoids extra
types.)

------------------------------------
	Bug in loop detection in TcSimplify
	------------------------------------

The type-class context simplifier has been able to 
build recursive dictionaries for some time: co-induction.
That is, you can build a proof for constraint C by assuming
that C holds when proving the preconditions of C.

You need to be in -fallow-undecidable-instances land to 
make use of this: see comments with [RECURSIVE DICTIONARIES]
in TcSimplify.lhs.

Anyway, this is all fine, but I'd implemented it wrong!  You need
to be very careful with superclasses, or you can make a bogus
loop by mistake.  This commit fixes it; tests LoopOfTheDay{1,2,3}
will test it (thanks Ralf Laemmel).

Error message fixup

Moved GTK_CONFIG detection to ghc subdirectory (untested).

Nuked some outdated stuff

No need for --enable-hopengl anymore

Make Core Lint check for 1-tuples

Get rid of some `...' style quotes

Update TH import

distclean: clean config.mk only *after* doing the recursive cleaning.
Otherwise we don't clean properly in the subdirectories or sub-ways.

- Implement expose/hide
- fix parsing of package identifiers (forgot to commit this the other day)

A fix to kind signatures for GADT data type decls

TH refication for primitive TyCons

Support the --auto-ghci-libs option in conjuction with 'register'.

Mac OS X/Darwin/Mach-O:

Improve handling of object files without dynamic symbol tables.

Sorry for the fact that there are overlapping three commits in here...

1.  Make -fno-monomorphism-restriction 
    and -fno-implicit-prelude reversible, like other flags

2.  Fix a wibble in the new ImportAvails story, in RnNames.mkExportAvails

3.  Fix a Template Haskell bug that meant that top-level names created
    with newName were not made properly unique.

Trim imports

Missing include

Missing import on Windows

Update the excluded modules for libghccompat

Data.Version --> Distribution.Version

Data.Version -> Distribution.Version

Data.Version isn't necessary any more, the Version type is exported by
Distribution.Version.