Messages in this thread | | | Date | Sat, 16 Aug 2008 12:26:54 -0700 (PDT) | From | Alex Dubov <> | Subject | Problem with find_first_bit function and kin |
| |
It's well may be that I'm just missing something obvious.
It seems to me that find_first_bit/find_next_bit functions return their offsets "base 1" - first set bit is "1" and last is "bitmap size". This means that if only the last bit in the bitmap is set, the returned value will be indistinguishable from no bits set situation. Moreover, bit manipulation functions appear to use "base 0" bit addresses, adding to the inconvenience.
Is this a desired behavior? And, if yes, how is one supposed to deal with last bit of the bitmap?
| |