Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation `Resource use' incorrect for 64-bit pointer architecture #36

Closed
GoogleCodeExporter opened this issue Aug 3, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

In the documentation `Implementation notes' under the section `Resource
use', it states:

The space overhead for an sparsetable of size N is N + 48N/M bits. For the
default value of M, this is exactly 2 bits per array entry.

This statement is true for architectures with a 32-bit pointer. For an
architecture with a 64-bit pointer, the overhead is
N + 80N/M bits
and for the default value of M=48, the overhead is 8/3 or 2.67 bits per entry.

Cheers,
Shaun

Original issue reported on code.google.com by sjackman on 4 Mar 2009 at 12:41

@GoogleCodeExporter
Copy link
Author

Good point.  I'll fix the documentation for the next release.

Original comment by csilv...@gmail.com on 4 Mar 2009 at 8:56

  • Changed state: Started
  • Added labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

This should be fixed in sparsehash 1.5, just released.

Original comment by csilv...@gmail.com on 7 May 2009 at 3:10

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant