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

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8820: Reduce debug symbols size
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-07-15 03:48:41

#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
Resolution: | Keywords:

Comment (by andysem):

 Yes, *.pdb are a possibility but only for shared libraries, which are not
 much of a problem (the shared library boost_log_setup-vc110-mt-gd-1_55.dll
 is only around 3 MiB vs. 400 MiB of the static library). It's the static
 library I'm most concerned.

 As for the semantic actions, I used Boost.Bind to implement them, nothing
 fancy. I suppose, it shouldn't generate that much debug info, but I can
 try replacing it with hand-written function objects.

 By semantic-action free parsers you mean using the attributes? I'm not
 sure this is applicable to my case because the parsers are supposed to
 build filters and formatters as they parse the string. Filters and
 formatters themselves are based on Boost.Phoenix v3 but only phoenix::bind
 and logical operators are used to compose the filters as the parsers work.
 I already use type erasure to hide the actual parsed filters and
 formatters (which are compiled in separate translation units), so there
 shouldn't be a combinatorial explosion of phoenix::bind instantiations. I
 could try removing these bits of Boost.Phoenix but I'm not sure it'll help
 much. But thanks for the suggestion.

 Is there an estimate when Spirit X3 is ready? Is it API-compatible with
 Spirit v2? I could give it a try but I'm most interested in a short-term
 solution right now (i.e. for 1.55 - 1.56 release).

Ticket URL: <>
Boost C++ Libraries <>
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