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

To: Dan Nicolaescu <dann at godzilla dot ICS dot UCI dot EDU>
Subject: Re: bbreorder odity
From: Richard Henderson <rth at redhat dot com>
Date: Thu, 15 Mar 2001 14:05:34 -0800
Cc: gcc at gcc dot gnu dot org
References: <200103140226.aa10671@gremlin-relay.ics.uci.edu> <20010315011016.B21944@redhat.com> <200103151402.aa05472@gremlin-relay.ics.uci.edu>

On Thu, Mar 15, 2001 at 02:02:38PM -0800, Dan Nicolaescu wrote:
> Is there anything that is supposed to duplicate the epilogue instead
> of doing a jump to the epilogue (of course if not using -Os)? 

Not at present.

> Is this desirable at all? It seems so, but there might be other
> implications that I am not aware of...

Depending on the size of the epilogue, yes.  It should probably
be done with generic block duplication code -- possibly under
control of the instruction scheduler.

r~

References:
- bbreorder odity
  - From: Dan Nicolaescu
- Re: bbreorder odity
  - From: Richard Henderson
- Re: bbreorder odity
  - From: Dan Nicolaescu

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