Changes between Version 19 and Version 20 of Plugins/ReinitializeGlobals


Ignore:
Timestamp:
Jul 12, 2013 8:15:40 PM (20 months ago)
Author:
nfrisby
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Plugins/ReinitializeGlobals

    v19 v20  
    111111My only general concern is that I imagine we would like to keep the set of pointers maintained by Globals.c to a minimum? 
    112112 
    113 The slight wrinkle is that the stage=1 compiler must not use the foreign import, since the stage1 compiler links in the stage0 RTS (ie previous version), which does not necessarily export the (new) `getOrSetLibHSghcFastStringTable` symbol. Since the stage=1 compiler probably isn't going to load any plugins, this is probably not a big concern. 
     113The slight wrinkle is that the stage=1 compiler must not use the foreign import, since the stage1 compiler links in the stage0 RTS (ie previous version), which does not necessarily export the (new) `getOrSetLibHSghcFastStringTable` symbol. Since the stage=1 compiler probably isn't going to load any plugins, this is probably not a big concern. [[http://www.haskell.org/pipermail/ghc-devs/2013-July/001652.html]] 
    114114 
    115115=== Solution 2: use a dynamically linked compiler ===