Introduce kGCCallbackForced flag.

Introduce kGCCallbackForced flag.

This flag will be passed to GC prologue/epilogue callbacks if GC was forced through GC extension.

BUG=
R=dcarney@chromium.org, mstarzinger@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=18558

[Vyacheslav Egorov (Chromium), 2013-12-05 12:59:22]

Please take a look.

[dcarney, 2013-12-05 13:07:14]

lgtm

I think mstarzinger wanted kGCCallbackForced renamed to something else though

[Vyacheslav Egorov (Chromium), 2013-12-05 13:37:34]

I think we agreed not to rename it. Michael wanted to use the same flag in the
other forced types of GCs, in this case it would make sense to rename it. 

I am not likely to land until branch point anyways so we will double check with
him when he is back.

[Michael Starzinger, 2014-01-07 13:44:39]

LGTM, just a not about the name.

https://codereview.chromium.org/104023011/diff/1/include/v8.h
File include/v8.h (right):

https://codereview.chromium.org/104023011/diff/1/include/v8.h#newcode4115
include/v8.h:4115: kGCCallbackForced = 1 << 2
nit: Sticking with the naming convention of the other flags, I think this should
be called kGCCallbackFlagForced.

[Vyacheslav Egorov (Google), 2014-01-13 10:44:17]

Thanks for the review Michael & Dan! Landing

https://codereview.chromium.org/104023011/diff/1/include/v8.h
File include/v8.h (right):

https://codereview.chromium.org/104023011/diff/1/include/v8.h#newcode4115
include/v8.h:4115: kGCCallbackForced = 1 << 2
On 2014/01/07 13:44:40, Michael Starzinger wrote:
> nit: Sticking with the naming convention of the other flags, I think this
should
> be called kGCCallbackFlagForced.

Done.

[Vyacheslav Egorov (Chromium), 2014-01-13 10:57:58]

Committed patchset #1 manually as r18558 (presubmit successful).