Well, C in SS11 already used dwarf as the debug format so you may be comparing the same volume of data. The other possibility is that the C++ code ends up needing a larger volume of data when compared to a similar number of C lines of code.
You can switch formats with -xdebugformat=stabs, so you should be able to do the experiment. If you do that, also test with -xs to see the application size when the debug info is actually stored in the executable. Regards, Darrly. On 09/11/08 07:18 AM, hemachandran wrote: > Hi Darryl, > > Thanks, Why aren't we then not seeing size increases for the binaries > created from c code. Why is this happening only for C++ files ? > > -Regards > Hemachandran > > Darryl Gove wrote: >> Hi, >> >> Studio 12 C++ uses dwarf debug format which is stored in the >> executable. SS11 uses stabs which is stored in the object files >> (unless the flag -xs is specified). >> >> You might want to check the size of the stripped binaries. >> >> Regards. >> >> Darryl. >> >> >> On 09/10/08 07:05 AM, Hemachandran Namachivayam wrote: >>> Hi, >>> >>> I am comiling Suncluster code on SS12 and the generated debug binary >>> is 10 times bigger than the one they used to be on SS12. >>> >>> For e.g, here is am trying to generate clreslogicalhostname and one >>> of the CC command is >>> /ws/sc31u-tools/SUNWspro/SOS10/bin/CC -g -Qoption ccfe >>> -messages=no%anachronism -Qoption ccfe -features=no%conststrings >>> -xwe -DTEXT_DOMAIN=\"SUNW_SC_CMD\" >>> -DMESSAGE_DIR=\"/usr/cluster/lib/locale\" -DSOL_VERSION=200411 >>> -DOS_PLATFORM=Solaris >>> -I/workspace/hn154558/india/scal-dg+5.10+i386/proto/Sol_10/root_i386/usr/include >>> >>> -I/workspace/hn154558/india/scal-dg+5.10+i386/proto/Sol_10/root_i386/usr/cluster/include >>> >>> -I/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/usr >>> /include -I../../include >>> -I/workspace/hn154558/india/scal-dg+5.10+i386/usr/src/common/cl >>> -I../../include/xml >>> -I/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/usr/include/libxml2 >>> -L/workspace/hn154558/india/scal-dg+5.10+i386/proto/Sol_10/root_i386/usr/cluster/lib >>> >>> -L/workspace/hn154558/india/scal-dg+5.10+i386/proto/Sol_10/root_i386/usr/lib >>> >>> -L/workspace/hn154558/india/scal-dg+5.10+i386/proto/Sol_10/root_i386/lib >>> -L/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/usr/lib >>> -L/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/lib -Y >>> P,/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/usr/lib -Y >>> P,/ws/sc31u-tools/ref_proto/s10/s10u5_10/root_i386/lib >>> -R/usr/cluster/lib -DRS_LH -c clresource.cc >>> >>> The resulting executable file size on S11 is >>> du -sh clreslogicalhostname 324K clreslogicalhostname >>> >>> On S12 it is >>> du -sh clreslogicalhostname 3.5M clreslogicalhostname >>> >>> Any idea or suggestions ? >>> >>> -Thanks and Regards >>> Hemachandran >>> -- >>> This message posted from opensolaris.org >>> _______________________________________________ >>> tools-compilers mailing list >>> tools-compilers at opensolaris.org >> -- Darryl Gove Compiler Performance Engineering Blog: http://blogs.sun.com/d/ Book: http://www.sun.com/books/catalog/solaris_app_programming.xml
