search for: sparsebitvectorelement

Displaying 5 results from an estimated 5 matches for "sparsebitvectorelement".

2009 May 12
1
[LLVMdev] SparseBitVector compile warning
The warning is: R:\SDKs\llvm\trunk\include\llvm/ADT/SparseBitVector.h(58) : warning C4099: 'llvm::ilist_sentinel_traits<llvm::SparseBitVectorElement<ElementSize>>' : type name first seen using 'struct' now seen using 'class' R:\SDKs\llvm\trunk\include\llvm/ADT/SparseBitVector.h(275) : see reference to class template instantiation 'llvm::SparseBitVectorElement<ElementSize>' being compiled R:\SDK...
2007 Sep 07
0
[LLVMdev] [PATCH]: Add SparseBitmap implementation
...tion of a bitvector that is sparse by only +/// storing the elements that have non-zero bits set. In order to make this +/// fast for the most common cases, SparseBitVector is implemented as a linked list Please wrap lines to fit in 80 columns. + template <int ElementSize = 128> + struct SparseBitVectorElement { + public: I'd suggest outdenting this. Indenting due to the namespace doesn't add any value. Also, I'd suggest making ElementSize 'unsigned' instead of int. + unsigned ElementIndex; // Index of Element in terms of where first bit + // starts Please use: /// El...
2007 Sep 04
6
[LLVMdev] [PATCH]: Add SparseBitmap implementation
On 9/4/07, Dan Gohman <djg at cray.com> wrote: > On Tue, Sep 04, 2007 at 10:35:10AM -0400, Daniel Berlin wrote: > > On 9/4/07, Dan Gohman <djg at cray.com> wrote: > > > On Fri, Aug 31, 2007 at 08:10:33PM -0400, Daniel Berlin wrote: > > > > + template <int ElementSize> > > > > + class SparseBitmap { > > > > > > Do you
2007 Sep 07
1
[LLVMdev] [PATCH]: Add SparseBitmap implementation
...nly > +/// storing the elements that have non-zero bits set. In order to make this > +/// fast for the most common cases, SparseBitVector is implemented as a linked list > > Please wrap lines to fit in 80 columns. Done > > + template <int ElementSize = 128> > + struct SparseBitVectorElement { > + public: > > I'd suggest outdenting this. Indenting due to the namespace doesn't add > any value. Also, I'd suggest making ElementSize 'unsigned' instead of > int. Done > > + unsigned ElementIndex; // Index of Element in terms of where first bit...
2014 Mar 02
3
[LLVMdev] [RFC] The coding standard for "struct" should be relaxed or removed
On Mar 1, 2014, at 7:15 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Sat, Mar 1, 2014 at 5:59 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > The current guidelines [1] on the use of the struct keyword are too > restrictive and apparently ignored. They limit the use of struct to > PODs, citing broken compilers. > > The guidelines are