v8/test
kmillikin@chromium.org cc0c8d178f Materializing a frame element on the stack by pushing it can cause the
stack pointer to change by more than one in a corner case.  If we push
a constant smi larger than 16 bits, we push it via a temporary
register.  Allocating the temporary can cause a register to be spilled
from the frame somewhere above the stack pointer.

As a fix, do not use pushes to materialize ranges of elements of size
larger than one.

Review URL: http://codereview.chromium.org/92121

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1785 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2009-04-24 11:26:49 +00:00
..
cctest Materializing a frame element on the stack by pushing it can cause the 2009-04-24 11:26:49 +00:00
message Fixed a bunch of memory leaks in tests, including: 2009-03-27 00:24:49 +00:00
mjsunit - Extended lazy loading to general objects, not just functions. 2009-04-24 08:13:09 +00:00
mozilla Add support for \b and ^ and $ in multiline mode, completing Irregexp 2009-01-19 18:56:47 +00:00