diff options
author | Mansour Moufid <mansourmoufid@gmail.com> | 2014-10-19 12:59:28 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2014-11-02 11:54:42 -0500 |
commit | 06b1ef7b76feb93243affd0ac7b62b03caf9a27d (patch) | |
tree | 65b5df306be2acdec3983fb46481f343c52ded9f /src/common | |
parent | 3ab2c865bfb78e50f7c67c71144fbed37a7b4478 (diff) | |
download | tor-06b1ef7b76feb93243affd0ac7b62b03caf9a27d.tar.gz tor-06b1ef7b76feb93243affd0ac7b62b03caf9a27d.zip |
Remove a duplicate comment.
Diffstat (limited to 'src/common')
-rw-r--r-- | src/common/util.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/common/util.c b/src/common/util.c index 6e30c47bf9..013a501dbc 100644 --- a/src/common/util.c +++ b/src/common/util.c @@ -212,12 +212,6 @@ size_mul_check(const size_t x, const size_t y) void * tor_calloc_(size_t nmemb, size_t size DMALLOC_PARAMS) { - /* You may ask yourself, "wouldn't it be smart to use calloc instead of - * malloc+memset? Perhaps libc's calloc knows some nifty optimization trick - * we don't!" Indeed it does, but its optimizations are only a big win when - * we're allocating something very big (it knows if it just got the memory - * from the OS in a pre-zeroed state). We don't want to use tor_malloc_zero - * for big stuff, so we don't bother with calloc. */ tor_assert(size_mul_check(nmemb, size)); return tor_malloc_zero_((nmemb * size) DMALLOC_FN_ARGS); } |