search for: bitword

...Message: 'You have used a std:: construct that is not safe. See documentation on how to use the Safe Standard C++ Library' c:\Eigenes\compiler\llvm-2.0\include\llvm/ADT/BitVector.h(90) : see reference to function template instantiation '_OutIt std::copy<llvm::BitVector::BitWord*,llvm::BitVector::BitWord*>(_InIt,_InIt,_OutIt)' being compiled with [ _OutIt=llvm::BitVector::BitWord *, _InIt=llvm::BitVector::BitWord * ] C:\eigenes\compiler\vcc2005\VC\include\xutility(2282) : warning C4996: 'std::_Copy_opt' was dec...

...// Current bit number inside 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, C...

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

...inside 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? They were intended to be, sorry. > > > + SparseBitmapIterator(SparseBitmap<ElementSize> &RHS, > > + bool end = false):Bitmap(RHS) { &gt...