On 10/07/2016 01:07 PM, Richard Biener wrote:
On Fri, 7 Oct 2016, Bernd Schmidt wrote:
Here, if necessary I'd prefer we create a to_clear bitmap and perform an
and_compl operation after the loop.
But that's way more expensive -- you allocate memory and perform an
additional loop over the bitmap.
Yeah. Can we have an additional safer variant of the bitmap iterators
maybe? We could have an object that gets constructed in the for
statement and serves as a lock/unlock, where we postpone deletion of
elements while locked, and flush them on unlock (keeping a flag to say
if that's necessary).
Bernd
