[cleanup] Bring back comment lost in refactoring.

R=cbruni@chromium.org
BUG=v8:6474

Change-Id: I84be45bab041082cc66b5fdd70a9e799a44facee
Reviewed-on: https://chromium-review.googlesource.com/529207
Reviewed-by: Camillo Bruni <cbruni@chromium.org>
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#45819}
This commit is contained in:
Michael Starzinger 2017-06-09 15:53:42 +02:00 committed by Commit Bot
parent 5287d48bca
commit 2b9e36e968

View File

@ -3090,9 +3090,10 @@ template <SearchMode search_mode, typename T>
inline int Search(T* array, Name* name, int valid_entries = 0, inline int Search(T* array, Name* name, int valid_entries = 0,
int* out_insertion_index = NULL); int* out_insertion_index = NULL);
// The cache for maps used by normalized (dictionary mode) objects. // HandlerTable is a fixed array containing entries for exception handlers in
// Such maps do not have property descriptors, so a typical program // the code object it is associated with. The tables comes in two flavors:
// needs very limited number of distinct normalized maps. // 1) Based on ranges: Used for unoptimized code. Contains one entry per
// exception handler and a range representing the try-block covered by that
// handler. Layout looks as follows: // handler. Layout looks as follows:
// [ range-start , range-end , handler-offset , handler-data ] // [ range-start , range-end , handler-offset , handler-data ]
// 2) Based on return addresses: Used for turbofanned code. Contains one entry // 2) Based on return addresses: Used for turbofanned code. Contains one entry