#11561: Have static ghci link against its own copy of its libraries -------------------------------------+------------------------------------- Reporter: rwbarton | Owner: Type: feature request | Status: new Priority: low | Milestone: Component: Runtime System | Version: 8.1 (Linker) | Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Runtime | Unknown/Multiple performance bug | Test Case: Blocked By: | Blocking: Related Tickets: #11238 | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by rwbarton): Replying to [comment:3 trommler]:
Replying to [comment:1 rwbarton]:
I don't know how this would interact with remote ghci. Badly, I guess. Why? Remote GHCi lives in its own process, so the way the parent process is linked does not matter at all. Am I missing something fundamental here?
I just thought that the pros would not apply since the Haskell libraries linked into the main ghc(i) process cannot be shared with the ones used by code loaded into the remote ghci process. But I didn't think about the fact that the remote ghci process also has its own set of Haskell libraries (assuming again that it is statically linked). So in fact the same benefits apply there; maybe reduced if ghc-iserv links against fewer Haskell libraries than ghc does. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/11561#comment:4 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler