object file size is reduced after build

Hi all,


We have large code on which we are solving the bugs. For every bug we
change the code part either add or delete some of the code part. More
is adding the code part and very less is deleting the code.

But the question is , after build the object file( changed code) size
is less than the object file ( unchanged code)???. As we increased
the lines of code the object file size should be increased but here it
is decresing .. why?

Is these issue with the optimization? as we are doing with
optimization 2.


Thanks in advance,
jayapal
.

Relevant Pages

  • Re: object file size is reduced after build
    ... We have large code on which we are solving the bugs. ... after build the object file(changed code) size ... Is these issue with the optimization? ...
    (comp.lang.c)
  • object file size is reduced after build
    ... We have large code on which we are solving the bugs. ... after build the object file(changed code) size ... Is these issue with the optimization? ...
    (comp.lang.c)
  • Re: need help on CFLAGS in /etc/make.conf please
    ... Let's first deal with the notion that GCC has optimization bugs ... | Optimization is usually only turned on when compiling a release ... allowing a port's -O to override mine. ...
    (freebsd-hackers)
  • Re: need help on CFLAGS in /etc/make.conf please
    ... Let's first deal with the notion that GCC has optimization bugs ... | Optimization is usually only turned on when compiling a release ... allowing a port's -O to override mine. ...
    (freebsd-questions)
  • Re: Compiling with -O option gives different running time!
    ... with those optimization levels due to compiler bugs, ... The real issue is that higher optimization makes debugging _your_ code much more difficult, and -fomit-frame-pointer can make it tough to figure out where to look. ... If -O3 exposes more of my bugs, that's great, but excessive optimization may make it impossible for me to isolate them. ... One of the tribulations of optimization is that even including test code to find bugs may change the resulting code so that the bug no longer happens, and stepping through the code in a debugger is mind-boggling because it no longer remotely resembles what you wrote. ...
    (comp.lang.c)