Make the max_semispace_size parameter customizable on a PLATFORM basis....

Make the max_semispace_size parameter customizable on a PLATFORM basis. This provides platforms with larger available memory pools the ability to exploit these. The current existing implementation limits the expansion of the max_semispace_size parameter to the default max value in the presence of snapshots.

[Mads Ager (chromium), 2010-11-15 08:43:04]

LGTM, I'll land for you with minor modifications.

http://codereview.chromium.org/4937001/diff/1/src/heap.cc
File src/heap.cc (right):

http://codereview.chromium.org/4937001/diff/1/src/heap.cc#newcode101
src/heap.cc:101: #if defined(PLATFORM_SPECIFIC_MAX_SEMISPACE_SIZE)
Let's just call this V8_MAX_SEMISPACE_SIZE. I would keep the section above
unchanged and just have a reassignment to Heap::max_semispace_size_ here.

[Mads Ager (chromium), 2010-11-15 10:00:56]

http://codereview.chromium.org/4937001/diff/1/src/heap.cc
File src/heap.cc (right):

http://codereview.chromium.org/4937001/diff/1/src/heap.cc#newcode101
src/heap.cc:101: #if defined(PLATFORM_SPECIFIC_MAX_SEMISPACE_SIZE)
On 2010/11/15 08:43:04, Mads Ager wrote:
> Let's just call this V8_MAX_SEMISPACE_SIZE.

> I would keep the section above
> unchanged and just have a reassignment to Heap::max_semispace_size_ here.

I take this part back. You can't since this is an initialization. :)

[Mads Ager (chromium), 2010-11-15 10:13:08]

Landed in revision 5823.