search for: sparsebitmapiterator

...nside of our bitmap > + unsigned BitNumber; > + > + // Current word number inside of our element > + unsigned WordNumber; > + > + // Current bits from the element. > + typename SparseBitmapElement<ElementSize>::BitWord Bits; Can these SparseBitmapIterator members, and a few more that follow, be made private? > + SparseBitmapIterator(SparseBitmap<ElementSize> &RHS, > + bool end = false):Bitmap(RHS) { This appears to miss an explicit keyword. Dan -- Dan Gohman, Cray Inc.

The attached patch adds a SparseBitmap implementation, which more or less works the same way as GCC's sparse bitmap. That is, we only store non-zero bits (broken up into elements of some bit size), and store the elements in a linked list. We keep track of the last accessed part of the linked list, so in-order tests/sets/resets are all constant time, rather than linear time. Set operations

...unsigned BitNumber; > > + > > + // Current word number inside of our element > > + unsigned WordNumber; > > + > > + // Current bits from the element. > > + typename SparseBitmapElement<ElementSize>::BitWord Bits; > > Can these SparseBitmapIterator members, and a few more that follow, > be made private? They were intended to be, sorry. > > > + SparseBitmapIterator(SparseBitmap<ElementSize> &RHS, > > + bool end = false):Bitmap(RHS) { > > This appears to miss an explicit keyword...