the question here: what is the motivation for making number string cache flushing more complicated?
do we have any benchmark? http://codereview.chromium.org/8341014/diff/1/src/heap.cc File src/heap.cc (right): http://codereview.chromium.org/8341014/diff/1/src/heap.cc#newcode833 src/heap.cc:833: // TODO(1605) select heuristic for flushing NumberString cache with remove todo? http://codereview.chromium.org/8341014/diff/1/src/heap.h File src/heap.h (right): http://codereview.chromium.org/8341014/diff/1/src/heap.h#newcode1423 src/heap.h:1423: static const int kNSCUnusedAge = -1; I don't think abbreviation NSC is good. http://codereview.chromium.org/8341014/ -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
