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

Issue 2905623003: [turbofan] Speculatively optimize string character access. (Closed)

Created:
3 years, 7 months ago by Benedikt Meurer
Modified:
3 years, 7 months ago
CC:
Hannes Payer (out of office), v8-reviews_googlegroups.com
Target Ref:
refs/heads/master
Project:
v8
Visibility:
Public.

Description

[turbofan] Speculatively optimize string character access. Add a protector cell for string bounds checks that is being used to protect speculative bounds for String.prototype.charCodeAt and String.prototype.charAt in TurboFan (and Crankshaft). This way we don't have the diamond in optimized code, which stands in the way of other optimizations for charCodeAt that are currently being worked on by petermarshall@. BUG=v8:6391 TBR=mlippautz@chromium.org R=petermarshall@chromium.org Review-Url: https://codereview.chromium.org/2905623003 Cr-Commit-Position: refs/heads/master@{#45514} Committed: https://chromium.googlesource.com/v8/v8/+/9d8bd0551657d60c66b2f96544eecedfba1cba8a

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+93 lines, -7 lines) Patch
M src/builtins/builtins-string-gen.cc View 2 chunks +14 lines, -2 lines 0 comments Download
M src/compiler/js-builtin-reducer.cc View 2 chunks +40 lines, -4 lines 0 comments Download
M src/crankshaft/hydrogen.cc View 1 chunk +1 line, -1 line 0 comments Download
M src/heap/heap.h View 1 chunk +1 line, -0 lines 0 comments Download
M src/heap/heap.cc View 1 chunk +4 lines, -0 lines 0 comments Download
M src/isolate.h View 1 chunk +1 line, -0 lines 0 comments Download
M src/isolate-inl.h View 1 chunk +5 lines, -0 lines 0 comments Download
A test/mjsunit/regress/regress-6391.js View 1 chunk +27 lines, -0 lines 0 comments Download

Messages

Total messages: 18 (8 generated)
Benedikt Meurer
3 years, 7 months ago (2017-05-24 12:51:21 UTC) #1
petermarshall
LGTM! Thanks
3 years, 7 months ago (2017-05-24 13:19:14 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/2905623003/1
3 years, 7 months ago (2017-05-24 13:19:58 UTC) #7
Michael Lippautz
heap/ LGTM
3 years, 7 months ago (2017-05-24 13:42:10 UTC) #8
commit-bot: I haz the power
Committed patchset #1 (id:1) as https://chromium.googlesource.com/v8/v8/+/9d8bd0551657d60c66b2f96544eecedfba1cba8a
3 years, 7 months ago (2017-05-24 13:53:49 UTC) #12
Michael Achenbach
A revert of this CL (patchset #1 id:1) has been created in https://codereview.chromium.org/2900333002/ by machenbach@chromium.org. ...
3 years, 7 months ago (2017-05-24 17:04:25 UTC) #13
Michael Achenbach
Alexey, could you have a look why so many inspector and debugger tests are flakily ...
3 years, 7 months ago (2017-05-24 20:14:19 UTC) #15
kozy
On 2017/05/24 20:14:19, machenbach (OOO) wrote: > Alexey, could you have a look why so ...
3 years, 7 months ago (2017-05-24 20:27:04 UTC) #16
kozy
crash on another bot looks completely unrelated, maybe it's a reason why revert doesn't help/ ...
3 years, 7 months ago (2017-05-24 20:29:55 UTC) #17
Michael Achenbach
3 years, 7 months ago (2017-05-25 15:02:38 UTC) #18
Message was sent while issue was closed.
On 2017/05/24 20:29:55, kozy wrote:
> crash on another bot looks completely unrelated, maybe it's a reason why
revert
> doesn't help/

Not sure if unrelated. Maybe another V8 change that causes this. The bots only
show V8 side failures as they retry with the pinned version. E.g. chromium
upstream doesn't have these errors and our roll is probably going to be blocked
as soon as we roll again after the branch. Which means we have to revert
something V8-side or skip the tests temporarily.

Powered by Google App Engine
This is Rietveld 408576698