#3843: Merge plugins into HEAD
---------------------------------+------------------------------------------
    Reporter:  dreixel           |        Owner:  simonpj     
        Type:  task              |       Status:  new         
    Priority:  normal            |    Milestone:  7.2.1       
   Component:  Compiler          |      Version:  6.13        
    Keywords:                    |     Testcase:              
   Blockedby:                    |   Difficulty:              
          Os:  Unknown/Multiple  |     Blocking:              
Architecture:  Unknown/Multiple  |      Failure:  None/Unknown
---------------------------------+------------------------------------------

Comment(by batterseapower):

 OK. The attached patches implement a fix for the plugins06 issue. Caveats:

   * This works on Windows and an earlier version (3483.zip) validated on
 Linux and OS X, but I have not specifically validated this version on
 those platforms. I'm pretty sure it should still work though.
   * A corresponding change needs to be made to the testsuite to mark
 plugins06 as passing on all platforms.
   * I don't think this patch works with a profiled/threaded GHC because
 I've hardcoded .a as the library suffix. Someone who knows more about the
 build system may know how to get _thr.a or _prof.a there instead?
   * If GHC changes to export just 200 more symbols a -O build of ghc-
 stage2 will start segfaulting in mysterious ways if you use GHCi due to
 strange Windows dynamic linker problems caused by DLLs with overflown
 export tables (due to my recent changes, ghc-stage2.exe only exports 65315
 symbols now, but the maximum is only 65536!)
   * There is some more opportunity to cut down on the number of exports
 from ghc-stage2.exe. I don't currently prevent libHSghc-prim, libHSbinary
 and the RTS from being exported from ghc.exe, because they are only
 depended on transitively. How can I get hold of their version numbers in
 ghc.mk?
   * There is a code size impact from applying this patch. I can't say
 exactly but I think the growth is less than 20%
   * I'm actually seeing some validate failures, though I don't think they
 are the fault of this patch since they are all related to FFI support:

 ~~~
 Unexpected failures:
    ffi/should_run  1679 [bad exit code] (normal)
    ffi/should_run  2469 [bad exit code] (normal)
    ffi/should_run  2594 [bad exit code] (normal)
    ffi/should_run  4038 [bad exit code] (normal)
    ffi/should_run  4221 [bad exit code] (normal)
    ffi/should_run  fed001 [bad exit code] (normal)
    ffi/should_run  ffi006 [bad exit code] (normal)
    ffi/should_run  ffi007 [bad exit code] (normal)
    ffi/should_run  ffi008 [bad exit code] (normal)
    ffi/should_run  ffi011 [bad exit code] (normal)
    ffi/should_run  ffi012 [bad exit code] (normal)
    ffi/should_run  ffi013 [bad exit code] (normal)
    ffi/should_run  ffi014 [bad exit code] (threaded1)
    ffi/should_run  ffi016 [bad exit code] (normal)
    ffi/should_run  ffi019 [bad exit code] (normal)
    rts             4850 [bad stdout] (normal)
    rts             5250 [bad exit code] (normal)
    rts             T4059 [bad exit code] (normal)
 ~~~

 Can anyone reproduce this? Are these in fact my fault?

 Please review the patch and advise on above points, particularly WRT to
 how to use the build system...

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3843#comment:43>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler

_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to