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]
Other format:	[Raw text]

Re: Java segfault in predict.c

From: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
To: Richard Henderson <rth at redhat dot com>,Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, gcc at gcc dot gnu dot org,gcc-patches at gcc dot gnu dot org
Date: Fri, 31 May 2002 13:06:36 +0200
Subject: Re: Java segfault in predict.c
References: <3CF4842F.8020802@waitaki.otago.ac.nz> <20020529085438.GA32472@atrey.karlin.mff.cuni.cz> <20020529104400.D4168@redhat.com>

Hello.

> Seems like
> 
> 	FOR_ALL_BB (bb)
> 	  if (TEST_BIT (loop->nodes, bb->index))
> 	    break;
> 	loop->first = bb;
> 
> 	FOR_ALL_BB_REVERSE (bb)
> 	  if (TEST_BIT (loop->nodes, bb->index))
> 	    break;
> 	loop->last = bb;
> 
> actually searches fewer blocks, and is clearer.

I'm committing this for now.

> Again, this seems like a real opportunity to want to rely on
> monotonicly increasing indicies...

Zdenek

References:
- Java segfault in predict.c
  - From: Bryce McKinlay
- Re: Java segfault in predict.c
  - From: Zdenek Dvorak
- Re: Java segfault in predict.c
  - From: Richard Henderson

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