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

Issue 23441018: Make VisitStatements() consistent among all AstVisitor implementations (Closed)

Created:
7 years, 3 months ago by Jakob Kummerow
Modified:
7 years, 3 months ago
Reviewers:
rossberg, Yang
CC:
v8-dev
Visibility:
Public.

Description

Make VisitStatements() consistent among all AstVisitor implementations R=yangguo@chromium.org Committed: http://code.google.com/p/v8/source/detail?r=16443

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+13 lines, -11 lines) Patch
M src/ast.cc View 1 chunk +3 lines, -1 line 0 comments Download
M src/hydrogen.cc View 1 chunk +3 lines, -1 line 0 comments Download
A + test/mjsunit/compiler/type-feedback-after-throw.js View 1 chunk +7 lines, -9 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
Jakob Kummerow
AstTyper::VisitStatements() contains the optimization "if (stmt->IsJump()) break;". Other AstVisitors, in particular the HOptimizedGraphBuilder, must do ...
7 years, 3 months ago (2013-08-30 10:34:48 UTC) #1
Yang
On 2013/08/30 10:34:48, Jakob wrote: > AstTyper::VisitStatements() contains the optimization "if (stmt->IsJump()) > break;". Other ...
7 years, 3 months ago (2013-08-30 10:37:48 UTC) #2
Jakob Kummerow
Committed patchset #1 manually as r16443.
7 years, 3 months ago (2013-08-30 10:51:47 UTC) #3
rossberg
7 years, 3 months ago (2013-08-30 11:24:21 UTC) #4
Message was sent while issue was closed.
On 2013/08/30 10:34:48, Jakob wrote:
> AstTyper::VisitStatements() contains the optimization "if (stmt->IsJump())
> break;". Other AstVisitors, in particular the HOptimizedGraphBuilder, must do
> the same, or they will stumble over uninitialized type feedback (empty
handles)
> in nodes that the typer has skipped.
> 
> An alternative implementation would be to remove the early return from the
> AstTyper, but I think it's a valid optimization, so we should just do it
> everywhere.

LGTM too. Thanks for fixing.

Ideally, we should really only have one implementation of
VisitStatements/Declarations and the CHECK macros that works for all visitors.
Maybe I'll try to refactor that.

Powered by Google App Engine
This is Rietveld 408576698