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

Issue 10698125: Fixed array bounds check elimination (Chromium issue 132114). (Closed)

Created:
8 years, 5 months ago by Massi
Modified:
8 years, 5 months ago
CC:
v8-dev
Visibility:
Public.

Description

Fixed array bounds check elimination (Chromium issue 132114). BUG= TEST= Committed: https://code.google.com/p/v8/source/detail?r=12025

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+80 lines, -52 lines) Patch
M src/flag-definitions.h View 1 chunk +1 line, -1 line 0 comments Download
M src/hydrogen.cc View 6 chunks +64 lines, -50 lines 0 comments Download
M test/mjsunit/array-bounds-check-removal.js View 2 chunks +15 lines, -1 line 0 comments Download

Messages

Total messages: 2 (0 generated)
Massi
8 years, 5 months ago (2012-07-10 10:30:10 UTC) #1
Vyacheslav Egorov (Google)
8 years, 5 months ago (2012-07-10 10:57:31 UTC) #2
LGTM

But I think implementation could become _much_ cleaner if we had a 

BoundsCheckRange index, low, high, length

(where low and high are int32_t [not even HConstant] and index and length are
HValues.

Bounds check elimination if performed after GVN so there is absolutely no gain
in exposing additions on HIR level.

Powered by Google App Engine
This is Rietveld 408576698