#1876: Complete shared library support
------------------------------+---------------------------------------------
Reporter: simonmar | Owner: clemens
Type: task | Status: assigned
Priority: high | Milestone: 6.10 branch
Component: Compiler | Version: 6.8.1
Severity: normal | Resolution:
Keywords: | Difficulty: Difficult (1 week)
Testcase: | Architecture: Unknown/Multiple
Os: Unknown/Multiple |
------------------------------+---------------------------------------------
Comment (by simonmar):
Some issues to resolve before we can deploy shared libraries. Some of
these are probable just questions to be answered, but hint at
documentation that we need to write.
* Do GHC distributions contain both shared and static libraries?
* Will Cabal build both shared and static libraries by default?
* Can a module built with `-dynamic` link against static libraries, if
the dynamic versions are not available?
* If modules are compiled with `-fPIC` and/or `-dynamic`, can they then
be linked statically? On which platforms? If not, what goes wrong if you
try this?
* On x86_64 we should have `-dynamic` turned on by default, for loading
modules into GHCi, otherwise data references to shared libraries will only
have 32-bit relocations and thus will break.
* Using `-static` at compile-time on x86_64 should therefore come with a
warning that the modules cannot be loaded into GHCi. Can we detect this
and report an error in GHCi?
* What is the performance overhead of turning on `-dynamic` by default on
x86_64?
* What is the performance overhead (and code-size overhead) of shared
libraries in general?
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1876#comment:11>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
