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: bbreorder odity


Richard Henderson <rth@redhat.com> writes:

  > On Wed, Mar 14, 2001 at 02:27:02AM -0800, Dan Nicolaescu wrote:
  > > Shouldn't the epilogue be duplicated here instead of using a jump? 
  > 
  > bb-reorder doesn't duplicate code.  So, "no" in that it isn't
  > designed to do that.

Is there anything that is supposed to duplicate the epilogue instead
of doing a jump to the epilogue (of course if not using -Os)? 
Is this desirable at all? It seems so, but there might be other
implications that I am not aware of...

  > > The odd thing is that the epilogue is duplicated when using 
  > > -O2 -fomit-frame-pointer
  > 
  > Technically, no.  With -fomit-frame-pointer, we have no
  > epilogue, just a return.  At which point HAVE_return is
  > true, and we put them everywhere we need them.


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