On 02/21/2011 04:37 PM, Hite, Christopher wrote: >> There is certainly more debug info generated by gcc 4.5.2. Are you > saying that your stripped binary went from 60MB to 1200MB without > counting any debug info? That seems difficult to understand. If that > is what happened you're >> going to need to track down the specific part of your program which > increased that much. Using nm --size-sort may help. > > No the stripped binary is with the old and new compiler is 60MB. That > seems to be the size of my code. So it's not an issue code bloat issue. > The binary with debug info goes from 180MB to 1200MB when I upgrade the > compiler. > > I can see the .o files having to do with my MPL generated en/decoder are > huge. > > Does debug information affect performance in any way? Assuming you're using GNU/Linux, no. The pages that contain the info don't even get allocated any memory until they're needed. Andrew.
