Re: [boost] [build][msvc] create PDBs

The size difference is LTCG, not debug info. ________________________________ From: Daniela Engert Sent: 7/23/2013 9:40 AM To: boost@lists.boost.org Subject: Re: [boost] [build][msvc] create PDBs Am 23.07.2013 17:47, schrieb Andrey Semashev:
In many cases, your observed size relationship is true, but not in all of them. E.g.: libboost_exception-vc120-mt-1_54.lib 53.642 libboost_exception-vc120-mt-1_54.pdb 102.400 libboost_exception-vc120-mt-gd-1_54.lib 11.440 libboost_exception-vc120-mt-gd-1_54.pdb 102.400 To exhibit the size advantage of PDBs over 'old-style' debug info embedded into static libs, I've rebuilt Boost.Log with link=static debug-store=object. This is the result: libboost_log_setup-vc120-mt-1_54.lib 343.234.460 libboost_log_setup-vc120-mt-gd-1_54.lib 374.488.888 libboost_log-vc120-mt-1_54.lib 79.564.296 libboost_log-vc120-mt-gd-1_54.lib 59.539.544 Ciao Dani _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Am 24.07.2013 06:20, schrieb Ahmed Charles:
The size difference is LTCG, not debug info.
Sorry, I don't understand your comment - probably my fault. Which numbers do you refer to? You can't compare debug and release configurations because of different compile options for optimization, inlining and link-time code generation - unless you really want to observe the impact of those compile options. BTW, stock msvc.jam/.py has no clue about link-time code generation and how to enable it. Ciao Dani
participants (2)
-
Ahmed Charles
-
Daniela Engert