Jim et al, > Our applications run on 64-bit machines, and we rely heavily on both > JudyL and JudySL. For some of our JudyL use, the keys are always > 32-bits, and the values are counts. These counts are always well less > than 2^32, so ideally we'd have a version of JudyL that mapped 32-bit > words to 32-bit words.
My best recollection is that the 32-bit version is "hardwired" to use 32-bit index and value area sizes, no matter the native pointer sizes on the machine. Try it? That is, link with the 32-bit version of the library, even on a 64-bit system, load up your data, and check the malloc()'d memory usage. If I recall right, it's true that you can't store a 64-bit pointer in a 32-bit JudyL value area. I just glanced at the Shop Manual and that's what it seems to indicate too. Cheers, Alan Silverstein ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
