limit InitialMaxFastElement by MaxRegularSpaceAllocationSize

limit InitialMaxFastElement by MaxRegularSpaceAllocationSize

BUG=

[weiliang.lin2, 2013-09-01 10:20:10]

To deopt when the allocation size (including elements size and array base size)
exceeds MaxRegularSpaceAllocationSize. 

That leads to deoptimization for ia32 with more than 100000 fast elements and
x64 with more than 98297 elements. 

It seems we can not make HAllocate smarter statically without adding extra code
in backend to check whether the size will exceed the limit.

[Jakob Kummerow, 2013-09-02 13:06:05]

If I understand correctly, this CL is functionally equivalent to:

#if V8_TARGET_ARCH_X64
  static const int kInitialMaxFastElementArray = 98297;
#else
  static const int kInitialMaxFastElementArray = 100000;
#endif

Right?
While a computed value is arguably cleaner (and more robust towards potential
future target architectures) than an #if, I'm still not sure it's the best
solution here. Since fast vs. dictionary elements can have a significant impact
on performance, it would be quite surprising to have different behavior on
different platforms.

Since the limit we're hitting is kind of arbitrary anyway, how about simply
bumping that a bit? See https://codereview.chromium.org/23604023 for what I
mean.