Searched refs:objects (Results 1 – 11 of 11) sorted by relevance
619 objects = zmalloc(sizeof(robj*) * numkeys); in bitopCommand()624 objects[j] = NULL; in bitopCommand()634 if (objects[i]) in bitopCommand()635 decrRefCount(objects[i]); in bitopCommand()639 zfree(objects); in bitopCommand()642 objects[j] = getDecodedObject(o); in bitopCommand()643 src[j] = objects[j]->ptr; in bitopCommand()644 len[j] = sdslen(objects[j]->ptr); in bitopCommand()736 if (objects[j]) in bitopCommand()737 decrRefCount(objects[j]); in bitopCommand()[all …]
8 is enough for all the objects to have a different enough time stamp during
200 set objects {1 a}202 r sadd set {*}$objects
195 test {BITOP with integer encoded source objects} {
57 test {INCR uses shared objects in the 0-9999 range} {68 test {INCR can modify objects in-place} {
133 * JEMALLOC_TCACHE enables a thread-specific caching layer for small objects.134 * This makes it possible to allocate/deallocate objects without any locking
142 work on objects having the same tag (e.g., groups of tables).165 + new functions for handling references to Lua objects
367 objects.447 making unallocated objects appear reachable to Valgrind.709 to be underreported (though the reported number of objects and bytes were718 size for sampled objects.732 - Fix junk filling of large objects, which could cause memory corruption.760 statistics for large objects.
144 Disable thread-specific caches for small objects. Objects are cached and249 or an array of such objects in the space allocated [...]
117 Note that this function will take care of freeing sub-replies objects356 uses customized reply object functions to create Ruby objects.
77 It's not a critical bug: the effect is to, sometimes, don't report objects1618 * [FIX] Lua debugger crash when printing too deeply nested objects.1668 * [NEW] Modify Jemalloc size classes to make certain Redis objects fit