GitLab

The problem is that we install the client's CWD before calling
runStmt, but runStmt has to load modules before running the code.  We
need to install the CWD just before running the code instead, which
means it has to be done inside runStmt (and resume).

From #2951

In this version, I untag R1 before using it, and even enter R2 at the
end rather than simply returning it (which didn't work right when R2
was a thunk).

A real bug in the x86_64 native code gen: nice!

This bug would have been caught by -Wall, and I would have gone though
and Walled this file but I know Ben is hacking on this file quite
heavily and I don't want to create undue conflicts.  Ben: it would be
nice to enable -Wall here when you have time.

Solaris's patch can't apply them if the lines beginning "---" aren't
preceeded by a "diff -ur foo bar" line.

Fixes trac #2956

 * Fix loading of 64bit floats
 * Put SRT and other read only static data in the .text segment

  * Use BlockIds in branch instructions instead of Imms.
  * Assign FP values returned from C calls to the right regs
  * Fix loading of F32s
  * Add a SPARC version of the FreeRegs map to the linear allcator.

This makes about half the tests in codeGen/should_run work.

In RTS tracing code, need to untag the pointer before trying 
to load the info table in printClosure()

Linux defines PTHREAD_MUTEX_ERRORCHECK = PTHREAD_MUTEX_ERRORCHECK_NP
anyway, so there's no need to special-case it.

Otherwise ASSERT_LOCK_HELD will cause deadlocks

Sun Jan  4 19:24:43 GMT 2009  Matthias Kilian <kili@outback.escape.de>
    Don't check pthread_mutex_*lock() only on Linux and/or only if DEBUG
    is defined. The return values of those functions are well defined
    and should be supported on all operation systems with pthreads. The
    checks are cheap enough to do them even in the default build (without
    -DDEBUG).
    
    While here, recycle an unused macro ASSERT_LOCK_NOTHELD, and let
    the debugBelch part enabled with -DLOCK_DEBUG work independently
    of -DDEBUG.