Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(247)

Issue 3125011: ARM: Ensure that we are not in a spilled scope when calling... (Closed)

Created:
10 years, 4 months ago by Erik Corry
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

ARM: Ensure that we are not in a spilled scope when calling Load() or constructing a reference. Committed: http://code.google.com/p/v8/source/detail?r=5270

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+35 lines, -28 lines) Patch
M src/arm/codegen-arm.cc View 20 chunks +35 lines, -28 lines 1 comment Download

Messages

Total messages: 2 (0 generated)
Erik Corry
10 years, 4 months ago (2010-08-16 06:49:17 UTC) #1
Søren Thygesen Gjesse
10 years, 4 months ago (2010-08-16 07:15:35 UTC) #2
LGTM

Should this mention issue 815?
Is it easy to make a regression test for
http://code.google.com/p/v8/issues/detail?id=815?

http://codereview.chromium.org/3125011/diff/1/2
File src/arm/codegen-arm.cc (right):

http://codereview.chromium.org/3125011/diff/1/2#newcode2609
src/arm/codegen-arm.cc:2609: STATIC_ASSERT(StackHandlerConstants::kNextOffset ==
0);
Maybe add the r0 comment here as well.

Powered by Google App Engine
This is Rietveld 408576698