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: (known?) Issue with bitmap iterators

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: Jeff Law <law at redhat dot com>
Cc: Joe Buck <Joe dot Buck at synopsys dot COM>, Richard Guenther <richard dot guenther at gmail dot com>, GCC <gcc at gcc dot gnu dot org>
Date: Thu, 25 Jun 2009 23:49:40 +0100
Subject: Re: (known?) Issue with bitmap iterators
References: <4A3CF81C.7050406@redhat.com> <84fc9c000906200801v28f814cj3fa5327c5f3df35e@mail.gmail.com> <4A3FBA1E.6040502@redhat.com> <20090622174623.GA6603@synopsys.com> <4A43C0F3.30503@redhat.com>

Jeff Law wrote:

> My biggest concern would be catching all the exit paths from the
> gazillion iterators we use and making sure they all reset the readonly
> flag.  Ick...


  Heh.  GCC-in-CXX would solve that for us :) or we could implement
try...finally clauses ....

    cheers,
      DaveK

References:
- (known?) Issue with bitmap iterators
  - From: Jeff Law
- Re: (known?) Issue with bitmap iterators
  - From: Richard Guenther
- Re: (known?) Issue with bitmap iterators
  - From: Jeff Law
- Re: (known?) Issue with bitmap iterators
  - From: Joe Buck
- Re: (known?) Issue with bitmap iterators
  - From: Jeff Law

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