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: Richard Henderson <rth at redhat dot com>
To: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
Cc: 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: Wed, 29 May 2002 12:49:22 -0700
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> <20020529192907.GA28830@atrey.karlin.mff.cuni.cz>

On Wed, May 29, 2002 at 09:29:07PM +0200, Zdenek Dvorak wrote:
> > Again, this seems like a real opportunity to want to rely on
> > monotonicly increasing indicies...
> 
> Why?

So that we don't have to search for the start, obviously. 
It'll be the lowest numbered block.


r~

Follow-Ups:
- Re: Java segfault in predict.c
  - From: Zdenek Dvorak
- Re: Java segfault in predict.c
  - From: Zdenek Dvorak

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
- Re: Java segfault in predict.c
  - From: Zdenek Dvorak

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