test/mjsunit/binary-op-newspace.js - Issue 263103006: Set max new space size in tests to proper MB value.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: test/mjsunit/binary-op-newspace.js

Issue 263103006: Set max new space size in tests to proper MB value. (Closed) Base URL: https://v8.googlecode.com/svn/branches/bleeding_edge

Patch Set: Created 6 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: test/mjsunit/binary-op-newspace.js

diff --git a/test/mjsunit/binary-op-newspace.js b/test/mjsunit/binary-op-newspace.js

index b47fcf6f59b1f8f7fc640cf309377a040e265f88..dac7d24dba2f551028dc934bd650d455667903dc 100644

--- a/test/mjsunit/binary-op-newspace.js

+++ b/test/mjsunit/binary-op-newspace.js

@@ -25,7 +25,7 @@

// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE

// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

-// Flags: --noopt

+// Flags: --max-new-space-size=2 --noopt

// Check that a mod where the stub code hits a failure in heap number

// allocation still works.

« no previous file with comments | « test/cctest/test-strings.cc ('k') | test/mjsunit/compiler/math-floor-global.js » ('j') | no next file with comments »