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

Issue 39126: Fixed issue 253. No longer assuming that the target of a property lookup is a... (Closed)

Created:
11 years, 9 months ago by olehougaard
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

Fixed issue 253. No longer assuming that the target of a property lookup is a JSObject. Committed: http://code.google.com/p/v8/source/detail?r=1416

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+41 lines, -4 lines) Patch
M src/runtime.cc View 1 chunk +10 lines, -4 lines 0 comments Download
A test/mjsunit/regress/regress-253.js View 1 chunk +31 lines, -0 lines 2 comments Download

Messages

Total messages: 3 (0 generated)
olehougaard
11 years, 9 months ago (2009-03-04 11:03:11 UTC) #1
Mads Ager (chromium)
LGTM http://codereview.chromium.org/39126/diff/1/2 File test/mjsunit/regress/regress-253.js (right): http://codereview.chromium.org/39126/diff/1/2#newcode31 Line 31: assertEquals(2, x[0] = 2); This test case ...
11 years, 9 months ago (2009-03-04 11:45:29 UTC) #2
olehougaard
11 years, 9 months ago (2009-03-04 11:56:57 UTC) #3
http://codereview.chromium.org/39126/diff/1/2
File test/mjsunit/regress/regress-253.js (right):

http://codereview.chromium.org/39126/diff/1/2#newcode31
Line 31: assertEquals(2, x[0] = 2);
On 2009/03/04 11:45:30, Mads Ager wrote:
> This test case does not hit your optimization pattern, so it is not really a
> regression test.  Just remove the return value assertions?

Done

Powered by Google App Engine
This is Rietveld 408576698