- 08 Sep, 2016 33 commits
-
-
cbruni authored
This CL fixes %DebugPrint for FAST_HOLEY_DOUBLE_ELEMENTS and now properly distinguishes TheHole and NaN values. BUG= Review-Url: https://codereview.chromium.org/2294913004 Cr-Commit-Position: refs/heads/master@{#39293}
-
cbruni authored
Revert of [runtime] temporarily transform IsContext check from DHECK to CHECK (patchset #2 id:20001 of https://codereview.chromium.org/2164633002/ ) Reason for revert: There have been no more occurrences of this on dev / beta so we can convert the CHECK back to DCHECK. Original issue's description: > [runtime] temporarily transform IsContext check from DCHECK to CHECK > > We are enabling this trial on canary to see if we can flush out some missing > context restores. > > BUG= > > Committed: https://crrev.com/ec94ad400dc257af396efa3b1899bc3168347d82 > Cr-Commit-Position: refs/heads/master@{#37875} TBR=jkummerow@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG= Review-Url: https://codereview.chromium.org/2303543003 Cr-Commit-Position: refs/heads/master@{#39292}
-
caitp authored
BUG=v8:5363 R=adamk@chromium.org, littledan@chromium.org, cbruni@chromium.org Review-Url: https://codereview.chromium.org/2328523002 Cr-Commit-Position: refs/heads/master@{#39291}
-
epertoso authored
The previous DCHECK (removed in issue 2316033002) was checking that the new interval strictly overlapped with the first interval. BUG= Review-Url: https://codereview.chromium.org/2321113002 Cr-Commit-Position: refs/heads/master@{#39290}
-
ishell authored
Drive-by-fix: the old code never triggered write barrier. Review-Url: https://codereview.chromium.org/2321993002 Cr-Commit-Position: refs/heads/master@{#39289}
-
aseemgarg authored
BUG=v8:4124 TEST:test-run-wasm-simd R=titzer@chromium.org,bradnelson@chromium.org,gdeepti@chromium.org Review-Url: https://codereview.chromium.org/2300753005 Cr-Commit-Position: refs/heads/master@{#39288}
-
ofrobots authored
Revert of Use -fno-delete-null-pointer-checks with gcc builds (patchset #2 id:20001 of https://codereview.chromium.org/2310513002/ ) Reason for revert: Fails on MIPS: https://build.chromium.org/p/client.v8.ports/builders/V8%20Mips%20-%20builder/builds/3653 Original issue's description: > Use -fno-delete-null-pointer-checks with gcc builds > > R=bmeurer@chromium.org, jochen@chromium.org, machenbach@chromium.org > BUG=v8:3782 > > Committed: https://crrev.com/dbefc8ee2e9ee6e41b83f3d09c788c34bc923b43 > Cr-Commit-Position: refs/heads/master@{#39286} TBR=jochen@chromium.org,bmeurer@chromium.org,machenbach@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3782 Review-Url: https://codereview.chromium.org/2328563002 Cr-Commit-Position: refs/heads/master@{#39287}
-
ofrobots authored
R=bmeurer@chromium.org, jochen@chromium.org, machenbach@chromium.org BUG=v8:3782 Review-Url: https://codereview.chromium.org/2310513002 Cr-Commit-Position: refs/heads/master@{#39286}
-
machenbach authored
Fell through the cracks in a recent CL. Should have switched with the CI bot, which is on GN already. BUG=chromium:474921 NOTRY=true Review-Url: https://codereview.chromium.org/2328533002 Cr-Commit-Position: refs/heads/master@{#39285}
-
mlippautz authored
BUG= R=ulan@chromium.org Review-Url: https://codereview.chromium.org/2328503002 Cr-Commit-Position: refs/heads/master@{#39284}
-
mythria authored
Adds support to collect allocation site feedback for Array function calls to the call bytecode handler. BUG=v8:4280, v8:4780 LOG=N Review-Url: https://codereview.chromium.org/2307903002 Cr-Commit-Position: refs/heads/master@{#39283}
-
ahaas authored
I could not reproduce the bug in either a unittest nor a cctest. That's why I created an mjsunit test now. BUG=chromium:644682 R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2319213003 Cr-Commit-Position: refs/heads/master@{#39282}
-
machenbach authored
BUG=chromium:644643 NOTRY=true Review-Url: https://codereview.chromium.org/2319583002 Cr-Commit-Position: refs/heads/master@{#39281}
-
ishell authored
Review-Url: https://codereview.chromium.org/2321543003 Cr-Commit-Position: refs/heads/master@{#39280}
-
franzih authored
The existing PropertyQueryCallback intercepts getOwnPropertyDescriptor, but it returns only value and attributes, not the accessors. This PropertyDescriptorCallback returns a descriptor similar to Ecma-262 6.2.4. You can either set a PropertyQueryCallback or a PropertyDescriptorCallback, but not both. When you set a callback for DefineProperty(), you can set a PropertyDescriptorCallback but not a PropertyQueryCallback. BUG=v8:5359 Review-Url: https://codereview.chromium.org/2311873002 Cr-Commit-Position: refs/heads/master@{#39279}
-
ulan authored
BUG= Review-Url: https://codereview.chromium.org/2324623004 Cr-Commit-Position: refs/heads/master@{#39278}
-
mstarzinger authored
This fixes the materialization of JSFunction objects to not rely on a context being available. The context has been cleared because it might be de-materiallized itself. R=bmeurer@chromium.org TEST=mjsunit/compiler/escape-analysis-materialize BUG=chromium:644245 Review-Url: https://codereview.chromium.org/2320983002 Cr-Commit-Position: refs/heads/master@{#39277}
-
ishell authored
Review-Url: https://codereview.chromium.org/2319243002 Cr-Commit-Position: refs/heads/master@{#39276}
-
rodolph.perfetta authored
The test was using some callee saved registers but tests don't save those. BUG=v8:5354 Review-Url: https://codereview.chromium.org/2322923002 Cr-Commit-Position: refs/heads/master@{#39275}
-
mstarzinger authored
This fixes the materialization of JSArray objects to not rely on a context being available. The context has been cleared because it might be de-materiallized itself. R=bmeurer@chromium.org BUG=chromium:644245 Review-Url: https://codereview.chromium.org/2323713002 Cr-Commit-Position: refs/heads/master@{#39274}
-
mlippautz authored
BUG=chromium:636331 R=ulan@chromium.org Review-Url: https://codereview.chromium.org/2319683002 Cr-Commit-Position: refs/heads/master@{#39273}
-
nikolaos authored
This patch moves the following parsing methods to ParserBase: - ParseScopedStatement - ParseVariableStatement - ParseDebuggerStatement - ParseV8Intrinsic It also cleans up the implementation-specific use counter mechanism. R=adamk@chromium.org, marja@chromium.org BUG= LOG=N Review-Url: https://codereview.chromium.org/2318263002 Cr-Commit-Position: refs/heads/master@{#39272}
-
ishell authored
Review-Url: https://codereview.chromium.org/2319173002 Cr-Commit-Position: refs/heads/master@{#39271}
-
mstarzinger authored
This adds support to the deoptimizer to materialize ContextExtension objects that have been de-materialized by escape analysis. This is follow-up to the inline allocation of such objects during the create lowering phase (i.e. JSCreateWithContext and JSCreateCatchContext). R=bmeurer@chromium.org TEST=mjsunit/regress/regress-crbug-644245 BUG=chromium:644245 Review-Url: https://codereview.chromium.org/2317353003 Cr-Commit-Position: refs/heads/master@{#39270}
-
machenbach authored
Also roll build and android_tools, which contains a bump of the ndk to r12b. BUG=chromium:629806 Review-Url: https://codereview.chromium.org/2320843003 Cr-Commit-Position: refs/heads/master@{#39269}
-
ishell authored
Delete unused CSA::AllocateUninitializedFixedArray() which also does not respect ParameterMode concept. Review-Url: https://codereview.chromium.org/2321643002 Cr-Commit-Position: refs/heads/master@{#39268}
-
mstarzinger authored
This clears the context register by setting it to Smi(0) before calling the Runtime::kNotifyDeoptimized helper. The deoptimizer must be able to materialize all heap objects without any context available. The context itself might be dematerialized. With this change we make sure that invariant is maintained even without escape analysis kicking in. We also satisfy the check that the context register is either Smi(0) or a valid context. It might have been the special {arguments_marker} in this particular case. R=bmeurer@chromium.org BUG=chromium:644245 Review-Url: https://codereview.chromium.org/2320673002 Cr-Commit-Position: refs/heads/master@{#39267}
-
bmeurer authored
When lowering Array.prototype.push/.pop to the fast inlined version, we first need to ensure that all prototypes (including the Object.prototype) are stable. R=mvstanton@chromium.org BUG=chromium:644689 Review-Url: https://codereview.chromium.org/2319533005 Cr-Commit-Position: refs/heads/master@{#39266}
-
marija.antic authored
BUG= Review-Url: https://codereview.chromium.org/2304133002 Cr-Commit-Position: refs/heads/master@{#39265}
-
martyn.capewell authored
Reason for revert: Breaks g++ build. Original issue's description: > [turbofan] ARM: Implement vswp and use in gap resolver > > Use vswp to switch double-precision registers in the gap resolver, with fall > back temp register-based code if NEON is not available. > > BUG= > > Committed: https://crrev.com/2837c2e65a2ee5b9fc610f30ce1215f52323ecbd > Cr-Commit-Position: refs/heads/master@{#39209} BUG= Review-Url: https://codereview.chromium.org/2314043002 Cr-Commit-Position: refs/heads/master@{#39264}
-
landell authored
BUG= Review-Url: https://codereview.chromium.org/2292973002 Cr-Commit-Position: refs/heads/master@{#39263}
-
bmeurer authored
The optimization is not correct for unsigned output types, and we the overall complexity seems too high. We need to find a better way to take into account the input/output type restrictions. Also added a regression test for the unsigned output bug. BUG=v8:5267,v8:5270,v8:5357 TBR=jarin@chromium.org Review-Url: https://codereview.chromium.org/2320013002 Cr-Commit-Position: refs/heads/master@{#39262}
-
jarin authored
The trouble here is that the type of the induction variable might be a bit ahead of the increment (JSAdd) operation's type. When we update the type of the increment, we might only update the induction variable type while the JSAdd type might be stale. If the induction variable typing needs to fall back to normal phi typing (e.g., when the increment is not an integer anymore), it might use the stale type. To get around this, we fake monotonicity if we fallback to normal phi typing. Another option would be to force re-typing of the increment operation, but that seems to be harder to maintain. BUG=chromium:644633 Review-Url: https://codereview.chromium.org/2320803002 Cr-Commit-Position: refs/heads/master@{#39261}
-
- 07 Sep, 2016 7 commits
-
-
littledan authored
This patch fixes a bunch of out-of-date TODOs, un-skips some tests and refers to appropriate bug numbers and current specification status where appropriate. R=adamk Review-Url: https://codereview.chromium.org/2319203002 Cr-Commit-Position: refs/heads/master@{#39260}
-
franzih authored
BUG= Review-Url: https://codereview.chromium.org/2315413002 Cr-Commit-Position: refs/heads/master@{#39259}
-
jshin authored
Move it to HARMONY_STAGED bucket Spec discussion: https://github.com/tc39/ecma402/issues/30 It's in stage 4 and Firefox has already implemented it. BUG=v8:5244 TEST=intl/date-format/date-format-to-parts.js TEST=test262/intl402/DateTimeFormat/prototype/formatToParts/* Review-Url: https://codereview.chromium.org/2317783003 Cr-Commit-Position: refs/heads/master@{#39258}
-
adamk authored
While fixing the bug, removed code duplication from super load/store runtime calls, and inlined calls of Object::ReadAbsentProperty (left over from strong mode). BUG=v8:5335 Review-Url: https://codereview.chromium.org/2311413002 Cr-Commit-Position: refs/heads/master@{#39257}
-
mstarzinger authored
This adds support for dematerialized context values as part of an interpreted frame (similar to an FCG frame). Both frame translations should be kept in sync as much as possible. R=rmcilroy@chromium.org BUG=chromium:644728 Review-Url: https://codereview.chromium.org/2313343002 Cr-Commit-Position: refs/heads/master@{#39256}
-
machenbach authored
Chromium doesn't support lsan with mac's current toolchain. BUG=chromium:644643 NOTRY=true Review-Url: https://codereview.chromium.org/2322493002 Cr-Commit-Position: refs/heads/master@{#39255}
-
jbroman authored
This yields a ~5% serialization time improvement on typical JSON-esque data. The approach taken matches json-stringifier fairly closely. BUG=chromium:148757 Review-Url: https://codereview.chromium.org/2311063004 Cr-Commit-Position: refs/heads/master@{#39254}
-