Revert "Make the linker API thread-safe"
authorSimon Peyton Jones <simonpj@microsoft.com>
Tue, 2 Dec 2014 10:05:49 +0000 (10:05 +0000)
committerSimon Peyton Jones <simonpj@microsoft.com>
Tue, 2 Dec 2014 10:22:08 +0000 (10:22 +0000)
commit4b51194df4090d984f02c12128e868077660fb8b
tree235ac9eb29821b9560fb9caabb2c90de73e85678
parent7932b2adaecac6c86038176d909c20ad1b1f9604
Revert "Make the linker API thread-safe"

This reverts commit b5e8b3b162b3ff15ae6caf1afc659565365f54a8.

I reverted it because one of these two patches
  9e6e4796437a7fc23e83605a45db9b2663570123 Add purgeObj()
  b5e8b3b162b3ff15ae6caf1afc659565365f54a8 Make the linker API thread-safe

causes a seg-fault on Windows.  The seg-fault happens immediately
the linker is invoked, in ghci or in Template Haskell.

I believe that it is the "linker API thread-safe" commit that causes
the seg-fault; it happens even if the "purgeObj" commit alone is
reverted.  But since the two patches mess with the same code, to
revert the "linker API" patch I had revert both.
docs/users_guide/7.10.1-notes.xml
rts/CheckUnload.c
rts/Linker.c
rts/LinkerInternals.h
testsuite/tests/rts/Makefile
testsuite/tests/rts/T2615.hs
testsuite/tests/rts/rdynamic.hs