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

Issue 2432143003: [turbofan] Don't introduce PlainPrimitiveToNumber for String inputs. (Closed)

Created:
4 years, 2 months ago by Benedikt Meurer
Modified:
4 years, 1 month ago
Reviewers:
Jarin
CC:
v8-reviews_googlegroups.com
Target Ref:
refs/pending/heads/master
Project:
v8
Visibility:
Public.

Description

[turbofan] Don't introduce PlainPrimitiveToNumber for String inputs. During JSTypedLowering we can decide to insert PlainPrimitiveToNumber operators on the inputs to still utilize pure Number operators, when the type feedback on the numeric binary operation is NumberOrOddball. However that is not beneficial if the inputs can be Strings, that is we cannot statically rule out String based on input type, as that inserts a ToNumber stub call into the hot code path. This repairs the NavierStokes regression with Ignition on Octane. R=jarin@chromium.org Committed: https://crrev.com/09410621f98bcf9fd022c4f183457ada6342c7fa Cr-Commit-Position: refs/heads/master@{#40427}

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M src/compiler/js-typed-lowering.cc View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 10 (6 generated)
Benedikt Meurer
4 years, 2 months ago (2016-10-19 09:00:15 UTC) #1
Jarin
lgtm
4 years, 2 months ago (2016-10-19 09:01:54 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2432143003/1
4 years, 2 months ago (2016-10-19 09:02:32 UTC) #7
Benedikt Meurer
4 years, 2 months ago (2016-10-19 10:33:20 UTC) #9
Message was sent while issue was closed.
Committed patchset #1 (id:1) manually as
09410621f98bcf9fd022c4f183457ada6342c7fa (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698