Haskell: unnecessary binary growth with module imports

Question

When i import a (big) module into a Main module in one of the following ways:

import Mymodule
import qualified Mymodule as M
import Mymodule (MyDatatype)

the compiled binary grows the same huge amount compared to when i don't import that module. This happens regardless of whether i use anything inside that module or not in the Main module. Shouldn't the compiler (i am using GHC on Debian Testing) only add into the binary what is needed to run it?

In my specific case i have a huge Map in Mymodule which i don't use in the Main module. Selectively importing what i really need, did not change the growth of the compiled binary.

chwarr · Accepted Answer · 2018-02-17 10:59:31Z

17

As far as GHC is concerned, import lists are only there for readability and avoiding name clashes; they don't affect what's linked in at all.

Also, even if you did only import a few functions from a library, they might still depend on the bulk of the library internally, so you shouldn't necessarily expect to see a size decrease from only using some of an available interface in general.

By default, GHC links in entire libraries, rather than only the pieces you use; you could avoid this by building libraries with the -split-objs option to GHC (or put split-objs: True in your cabal-install configuration file (~/.cabal/config on Unix)), but it slows down compilation, and is seemingly not recommended by the GHC developers:

-split-objs

Tell the linker to split the single object file that would normally be generated into multiple object files, one per top-level Haskell function or type in the module. This only makes sense for libraries, where it means that executables linked against the library are smaller as they only link against the object files that they need. However, assembling all the sections separately is expensive, so this is slower than compiling normally. Additionally, the size of the library itself (the .a file) can be a factor of 2 to 2.5 larger. We use this feature for building GHC’s libraries.

— The GHC manual

This will omit unused parts of libraries you use, regardless of what you import.

You might also be interested in using shared Haskell libraries.

edited Feb 17, 2018 at 10:59

chwarr

7,3802 gold badges34 silver badges58 bronze badges

answered Feb 8, 2012 at 17:16

ehird

40.9k3 gold badges184 silver badges184 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Josephine Over a year ago

Quoting ehird: "As far as GHC is concerned, import lists are only there for readability and avoiding name clashes; they don't affect what's linked in at all." That cannot be true, since the growth in size happens even if i only put an "import Mymodule" in the Main module without using anything inside that module.

ehird Over a year ago

"Import list" refers to the list of identifiers to import in parentheses after the module name, not the list of import statements at the top of a module.

Josephine Over a year ago

Right, that makes sense. Thanks for the clarification and the very informative answer!

SwiftsNamesake Over a year ago

The final link is dead

Collectives™ on Stack Overflow

Haskell: unnecessary binary growth with module imports

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related