Initialize zone lists in the register allocator with more reasonable initial ...

Initialize zone lists in the register allocator with more reasonable initial capacities.

Also replace fixed length zone lists with embedded vectors for the fixed live ranges.


Committed: http://code.google.com/p/v8/source/detail?r=7122

[Kevin Millikin (Chromium), 2011-03-10 11:23:08]

LGTM.

http://codereview.chromium.org/6660023/diff/1/src/lithium-allocator.h
File src/lithium-allocator.h (right):

http://codereview.chromium.org/6660023/diff/1/src/lithium-allocator.h#newcode604
src/lithium-allocator.h:604: EmbeddedVector<LiveRange*,
No matter what you do here, it will be a nasty line break.  I like to break at
the lowest precedence operator that makes it fit on the fewest lines.  Here, the
lowest precedence ought to be the space between the type and identifier:

EmbeddedVector<LiveRange*, Register::kNumAllocatableRegisters>
    fixed_live_ranges_;

I like that a little better, but what do you think?

[fschneider, 2011-03-10 12:04:16]

http://codereview.chromium.org/6660023/diff/1/src/lithium-allocator.h
File src/lithium-allocator.h (right):

http://codereview.chromium.org/6660023/diff/1/src/lithium-allocator.h#newcode604
src/lithium-allocator.h:604: EmbeddedVector<LiveRange*,
On 2011/03/10 11:23:08, Kevin Millikin wrote:
> No matter what you do here, it will be a nasty line break.  I like to break at
> the lowest precedence operator that makes it fit on the fewest lines.  Here,
the
> lowest precedence ought to be the space between the type and identifier:
> 
> EmbeddedVector<LiveRange*, Register::kNumAllocatableRegisters>
>     fixed_live_ranges_;
> 
> I like that a little better, but what do you think?

I'm fine with both.