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

Issue 10736009: Fix inline constructors for Harmony Proxy prototypes. (Closed)

Created:
8 years, 5 months ago by Michael Starzinger
Modified:
8 years, 5 months ago
Reviewers:
rossberg
CC:
v8-dev, jochen (gone - plz use gerrit)
Visibility:
Public.

Description

Fix inline constructors for Harmony Proxy prototypes. R=rossberg@chromium.org BUG=v8:2225 TEST=mjsunit/regress/regress-2225 Committed: https://code.google.com/p/v8/source/detail?r=12028

Patch Set 1 #

Total comments: 4

Patch Set 2 : Addressed comments by Andreas Rossberg. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+61 lines, -47 lines) Patch
M src/objects.cc View 1 3 chunks +25 lines, -16 lines 0 comments Download
M src/runtime.cc View 1 chunk +3 lines, -2 lines 0 comments Download
A + test/mjsunit/regress/regress-2225.js View 1 chunk +33 lines, -29 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
Michael Starzinger
8 years, 5 months ago (2012-07-10 11:00:03 UTC) #1
rossberg
LGTM with comments. https://chromiumcodereview.appspot.com/10736009/diff/1/src/objects.cc File src/objects.cc (right): https://chromiumcodereview.appspot.com/10736009/diff/1/src/objects.cc#newcode4864 src/objects.cc:4864: obj != heap->null_value(); While you're at ...
8 years, 5 months ago (2012-07-10 11:08:14 UTC) #2
Michael Starzinger
8 years, 5 months ago (2012-07-10 11:24:50 UTC) #3
Comments addressed. Landing.

https://chromiumcodereview.appspot.com/10736009/diff/1/src/objects.cc
File src/objects.cc (right):

https://chromiumcodereview.appspot.com/10736009/diff/1/src/objects.cc#newcode...
src/objects.cc:4864: obj != heap->null_value();
On 2012/07/10 11:08:14, rossberg wrote:
> While you're at it, can you replace this with !obj->IsNull()? (And likewise in
a
> couple of places below.)

As discussed offline: I'll keep the pointer comparison here, because it's more
efficient than the IsNull() predicate for cases where we already have the heap.

https://chromiumcodereview.appspot.com/10736009/diff/1/src/objects.cc#newcode...
src/objects.cc:7799: if (!prototype->IsJSReceiver()) {
On 2012/07/10 11:08:14, rossberg wrote:
> Do we still need this conditional at all? AFAICS, it is subsumed by the loop
> condition below.

Done.

Powered by Google App Engine
This is Rietveld 408576698