This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: empty function optimizations


"Ken Clark" <ken@gesn.com> writes:

|> > > Would collecting all the identical code at link time be as easy as it
|> > > sounds, or are there complications?
|> >
|> > Some conforming programs would break, but these are fairly obscure (e.g.
|> > programs that compare function pointers).  Debugging might get harder.
|> 
|> Thanks for the follow up guys.  The debugging argument is pretty simple to
|> answer -- turn it off.  When debugging you already have a hard drive full of
|> dwarf info, so you'd hardly be worried about duplicate object code.  The
|> only point of this is to reduce object bloat.

This would break the gurantee of generating identical code with or without
debugging information.  Debugging information should be completely
removable with a simple run of `strip'.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]