From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4864 invoked by alias); 1 Jul 2009 06:48:07 -0000 Received: (qmail 4847 invoked by uid 22791); 1 Jul 2009 06:48:06 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f225.google.com (HELO mail-ew0-f225.google.com) (209.85.219.225) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 01 Jul 2009 06:47:59 +0000 Received: by ewy25 with SMTP id 25so940772ewy.8 for ; Tue, 30 Jun 2009 23:47:56 -0700 (PDT) Received: by 10.210.30.10 with SMTP id d10mr1284665ebd.3.1246430875932; Tue, 30 Jun 2009 23:47:55 -0700 (PDT) Received: from ?192.168.2.99? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62]) by mx.google.com with ESMTPS id 7sm758020eyb.35.2009.06.30.23.47.54 (version=SSLv3 cipher=RC4-MD5); Tue, 30 Jun 2009 23:47:55 -0700 (PDT) Message-ID: <4A4B098C.7020507@gmail.com> Date: Wed, 01 Jul 2009 06:48:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeff Law CC: Alexander Monakov , Joe Buck , Richard Guenther , GCC 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> <20090626163559.GM14794@synopsys.com> <4A4AC845.7080709@redhat.com> In-Reply-To: <4A4AC845.7080709@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00016.txt.bz2 Jeff Law wrote: > (*) Imagine something like this (and related variants) > > EXECUTE_IF_SET_IN_BITMAP (bitmap, 0, i, bi) > { > blah blah blah > > if (bitmap_empty_p (bitmap)) > { > modify bitmap > break; > } > more blah blah > } > > We exit without iterating BI and thus miss your check. That's OK; there's no problem if you don't use the iterator again after you modify the bitmap. cheers, DaveK