Issue 1733016: Fix a bug where a GC at an unlucky moment caused a wrong

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

Issue 1733016: Fix a bug where a GC at an unlucky moment caused a wrong (Closed)

Created:
10 years, 8 months ago by Erik Corry

Modified:
9 years, 7 months ago

Reviewers:
Søren Thygesen Gjesse

CC:
v8-dev

Base URL:
http://v8.googlecode.com/svn/branches/bleeding_edge/

Visibility:
Public.

Description

Fix a bug where a GC at an unlucky moment caused a wrong calculation on ARM. Committed: http://code.google.com/p/v8/source/detail?r=4491

Patch Set 1 #

Total comments: 1

Created: 10 years, 8 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+60 lines, -4 lines)			Patch
	M	src/arm/codegen-arm.cc	View		5 chunks	+15 lines, -4 lines	0 comments	Download
	A	test/mjsunit/binary-op-newspace.js	View		1 chunk	+45 lines, -0 lines	1 comment	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

Søren Thygesen Gjesse

10 years, 8 months ago (2010-04-26 09:18:52 UTC) #2

LGTM

http://codereview.chromium.org/1733016/diff/1/2
File test/mjsunit/binary-op-newspace.js (right):

http://codereview.chromium.org/1733016/diff/1/2#newcode33
test/mjsunit/binary-op-newspace.js:33: // Flags: --max-new-space-size=65536
--trace-gc
Do you need to leave --trace-gc in here?

Expand Messages | Collapse Messages