Including ghc-users. On Sat, Mar 6, 2010 at 11:57 AM, Joachim Breitner <[email protected]> wrote: > Hi, > > in Debian, we are having some problems building large libraries (such as > agda, highlighting-kate, xmonad-contrib) on weaker architectures (sparc, > armel, s390) which compile with -fvia-C, especially when building the > profiling libraries. > > In the case of highlighting-kate, there were really issues with the > code: A huge list of words which ghc seemed to try to inline caused it > consuming a lot of memory. > > But in the case of agda, it even fails with relatively small modules: > https://buildd.debian.org/fetch.cgi?pkg=agda&arch=sparc&ver=2.2.6-3&stamp=1267334936&file=log&as=raw > > Now, looking at the memory gauge on my computer while compiling such a > program with Cabal (which compiles all modules in one ghc call), it > looks like it is steadily increasing. I’d expect ghc to free a lot of > memory when it is done with a module, but this does not seem to be the > case. > > Is this a bug (i.e. memory leak) in ghc or expected behavior? > > Is there a way to make Cabal build each module on its own? > > Are there any fixes or work-arounds? > > Greetings, > Joachim > > -- > Joachim "nomeata" Breitner > Debian Developer > [email protected] | ICQ# 74513189 | GPG-Keyid: 4743206C > JID: [email protected] | http://people.debian.org/~nomeata > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe > >
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
