[Boost-bugs] [Boost C++ Libraries] #8820: Reduce debug symbols size

Subject: [Boost-bugs] [Boost C++ Libraries] #8820: Reduce debug symbols size
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-07-14 18:08:47

#8820: Reduce debug symbols size
 Reporter: andysem | Owner: djowel
     Type: Bugs | Status: new
Milestone: To Be Determined | Component: spirit
  Version: Boost 1.54.0 | Severity: Problem
 Keywords: |
 There is [http://thread.gmane.org/gmane.comp.lib.boost.devel/242660 this ]
 discussion on Boost developers mailing list concerning Boost.Log compiled
 binary sizes. The problem by a large degree is caused by Boost.Spirit
 generating lots of debug info in the compiled libraries. I came to this
 conclusion by analyzing the object file sizes of Boost.Log (I've presented
 the object sizes in
 [http://article.gmane.org/gmane.comp.lib.boost.devel/242699 this] post,
 and you can see that the most part if the libboost_log_setup-vc110-mt-gd-
 1_55.lib library is occupied by parsers).

 The parsers in question are implemented in libs/log/src/filter_parser.cpp
 and formatter_parser.cpp. I'm not sure if there's anything I can do on
 Boost.Log side to mitigate the problem, other than to just rewrite them
 without Boost.Spirit. However, this example and my other general
 experience with Boost.Spirit indicates that Boost.Spirit tends to generate
 lots of debug info even for parsers of moderate complexity (like the ones
 in Boost.Log). I would really like something to be done about this.

Ticket URL: <https://svn.boost.org/trac/boost/ticket/8820>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:13 UTC