This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Warning about unreachable code.
- To: Geoff Keating <geoffk@ozemail.com.au>
- Subject: Re: Warning about unreachable code.
- From: Jeffrey A Law <law@cygnus.com>
- Date: Tue, 24 Aug 1999 00:32:27 -0600
- cc: rth@cygnus.com, egcs-patches@gcc.gnu.org
- Reply-To: law@cygnus.com
In message <199908181056.UAA01194@gluttony.geoffk.wattle.id.au>you write:
> Is that code supposed to be unreachable? The comment says:
>
> /* If no suitable BARRIER was found, create a suitab
> le
> one before TARGET. Since TARGET is a fall throug
> h
> path, we'll need to insert an jump around our blo
> ck
> and a add a BARRIER before TARGET.
>
> This creates an extra unconditional jump outside
> the loop. However, the benefits of removing rare
> ly
> executed instructions from inside the loop usuall
> y
> outweighs the cost of the extra unconditional jum
> p
> outside the loop. */
>
> but actually we never do this because if we didn't find a BARRIER we
> didn't get to this code.
The code above is meant to find hunks of code in loops that represent
exit paths from the loop and move them physically out of the loop. It
used to work :-0 Apparently something has changed or the patch got
mis-applied a couple years ago.
Anyone want to work on this?
jeff