This is the mail archive of the gcc-patches@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: proposed documentation change to bitmap.h

From: Daniel Berlin <dberlin at dberlin dot org>
To: Richard Henderson <rth at redhat dot com>
Cc: Diego Novillo <dnovillo at redhat dot com>, Ken Zadeck <zadeck at naturalbridge dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Date: Wed, 27 Oct 2004 15:14:37 -0400 (EDT)
Subject: Re: proposed documentation change to bitmap.h
References: <417E7C64.1040703@naturalbridge.com> <1098809484.10239.26.camel@localhost.localdomain><Pine.LNX.4.60.0410261301530.23544@dberlin.org> <20041027191117.GE18849@redhat.com>

On Wed, 27 Oct 2004, Richard Henderson wrote:

On Tue, Oct 26, 2004 at 01:02:25PM -0400, Daniel Berlin wrote:

Easily yes.
Cheaply, i'm not so sure.


Certainly.  Add a "modified" bit to the bitmap structure.
Clear it before beginning iteration.  Set it in anything
that changes the bitmap.  ICE in the iteration loop if it
becomes set.


This is the part i'm not sure is cheap.
I'm actually adding it now, we'll see what happens.

Should be --enable-checking, for certain.

r~

References:
- proposed documentation change to bitmap.h
  - From: Kenneth Zadeck
- Re: proposed documentation change to bitmap.h
  - From: Diego Novillo
- Re: proposed documentation change to bitmap.h
  - From: Daniel Berlin
- Re: proposed documentation change to bitmap.h
  - From: Richard Henderson

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