On Mon, Aug 4, 2014 at 8:50 AM, Sven Panne <[email protected]> wrote: > 2014-08-04 14:59 GMT+02:00 Mikhail Glushenkov <[email protected]>: >> https://ghc.haskell.org/trac/ghc/wiki/GHC-7.8-FAQ > > Hmmm, this isn't very specific, it just says that there are probably > bugs, but that's true for almost all code. :-) Are there any concrete > issues with --enable-split-objs?
Sorry for the confusion; I just meant you *should not* enable split-objs in your cabal configuration - GHC uses it for its libraries, but in general users don't want it for arbitrary code (bugs, huge linking time and memory usage, etc). >> One of the problems is that split-objs is extremely slow, especially >> on Windows. I had to disable split-objs for OpenGL-related libraries >> when building the HP installer in the past because of this. > > I think it's perfectly fine if the the compilation of the library > itself takes ages if it pays off later: You compile the library once, > but link against it multiple times. Or do the link times against e.g. > OpenGL stuff suffer? My point is: Do we make the right trade-off here? > A quick search brought up e.g. > https://github.com/gentoo-haskell/gentoo-haskell/issues/169 which > seems to be a request to split everything. > >> Randy also said that libraries built with split-objs don't work well >> in ghci on Windows x64. > > Is there an issue for this? Yes, there should be a bug filed for this if there isn't one already. But problems with the GHC build itself are really more of the priority than arbitrary user facing code. Still, a ticket would be good. > _______________________________________________ > ghc-devs mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/ghc-devs > -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ _______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
