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

Issue 6902202: Be more discriminating about uses of the arguments object in optimized code. (Closed)

Created:
9 years, 7 months ago by Kevin Millikin (Chromium)
Modified:
9 years, 7 months ago
Reviewers:
fschneider
CC:
v8-dev
Visibility:
Public.

Description

Be more discriminating about uses of the arguments object in optimized code. Because we track the value of the arguments object, we need to check values whenever plugged into a forbidden value context. It is not enough to check at only variable references as we did previously. R=fschneider@chromium.org BUG=1351 TEST=regress-1351.js Committed: http://code.google.com/p/v8/source/detail?r=7739

Patch Set 1 #

Total comments: 1

Patch Set 2 : Simplified. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+76 lines, -22 lines) Patch
M src/hydrogen.h View 5 chunks +19 lines, -5 lines 0 comments Download
M src/hydrogen.cc View 1 6 chunks +15 lines, -17 lines 0 comments Download
A test/mjsunit/regress/regress-1351.js View 1 chunk +42 lines, -0 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
Kevin Millikin (Chromium)
9 years, 7 months ago (2011-05-02 11:06:58 UTC) #1
Kevin Millikin (Chromium)
http://codereview.chromium.org/6902202/diff/1/src/hydrogen.cc File src/hydrogen.cc (right): http://codereview.chromium.org/6902202/diff/1/src/hydrogen.cc#newcode3469 src/hydrogen.cc:3469: CHECK_ALIVE(VisitForValue(expr->value(), arguments_allowed)); This is actually simpler, arguments is always ...
9 years, 7 months ago (2011-05-02 11:08:41 UTC) #2
fschneider
9 years, 7 months ago (2011-05-02 11:12:49 UTC) #3
LGTM.

Powered by Google App Engine
This is Rietveld 408576698