- 22 Sep, 2016 10 commits
-
-
bmeurer authored
If a JSCallFunction node doesn't have any callee information, either from feedback taken on input nodes, i.e. on property loads, or from the CallIC, we insert a soft deoptimization exit instead. R=jarin@chromium.org BUG=v8:5267 Review-Url: https://codereview.chromium.org/2361773002 Cr-Commit-Position: refs/heads/master@{#39619}
-
epertoso authored
An AtomicStore was used as an input to SmiTag. R=jgruber@chromium.org BUG= Review-Url: https://codereview.chromium.org/2360993002 Cr-Commit-Position: refs/heads/master@{#39618}
-
ishell authored
The handlers cleanup will be done in a follow-up CL. BUG=v8:5407 Review-Url: https://codereview.chromium.org/2357163003 Cr-Commit-Position: refs/heads/master@{#39617}
-
Ilija.Pavlovic authored
Port for VisitFloat32Add, VisitFloat64Add, VisitFloat32Sub and VisitFloat64Sub in InstructionSelector. TEST=unittests/InstructionSelectorTest.Float32AddWithFloat32Mul, unittests/InstructionSelectorTest.Float64AddWithFloat64Mul, unittests/InstructionSelectorTest.Float32SubWithFloat32Mul, unittests/InstructionSelectorTest.Float64SubWithFloat64Mul BUG= Review-Url: https://codereview.chromium.org/2341303002 Cr-Commit-Position: refs/heads/master@{#39616}
-
mtrofin authored
try_perf.py knows now of the "unity" benchmark suite NOTRY=true Review-Url: https://codereview.chromium.org/2358873002 Cr-Commit-Position: refs/heads/master@{#39615}
-
mstarzinger authored
This makes sure cycles in the object states graph are detected early by escape analysis instead of late in the scheduler. This is mainly done for improved debuggability. R=bmeurer@chromium.org BUG=chromium:613923 Review-Url: https://codereview.chromium.org/2354263002 Cr-Commit-Position: refs/heads/master@{#39614}
-
ishell authored
BUG=v8:5407 Review-Url: https://codereview.chromium.org/2353303002 Cr-Commit-Position: refs/heads/master@{#39613}
-
hablich authored
Revert of [Interpreter] Optimize BytecodeArrayBuilder and BytecodeArrayWriter. (patchset #6 id:200001 of https://codereview.chromium.org/2351763002/ ) Reason for revert: Prime suspect for roll blocker: https://codereview.chromium.org/2362503002/ Original issue's description: > [Interpreter] Optimize BytecodeArrayBuilder and BytecodeArrayWriter. > > This CL optimizes the code in BytecodeArrayBuilder and > BytecodeArrayWriter by making the following main changes: > > - Move operand scale calculation out of BytecodeArrayWriter to the > BytecodeNode constructor, where the decision on which operands are > scalable can generally be statically decided by the compiler. > - Move the maximum register calculation out of BytecodeArrayWriter > and into BytecodeRegisterOptimizer (which is the only place outside > BytecodeGenerator which updates which registers are used). This > avoids the BytecodeArrayWriter needing to know the operand types > of a node as it writes it. > - Modify EmitBytecodes to use individual push_backs rather than > building a buffer and calling insert, since this turns out to be faster. > - Initialize BytecodeArrayWriter's bytecode vector by reserving 512 > bytes, > - Make common functions in Bytecodes constexpr so that they > can be statically calculated by the compiler. > - Move common functions and constructors in Bytecodes and > BytecodeNode to the header so that they can be inlined. > - Change large static switch statements in Bytecodes to const array > lookups, and move to the header to allow inlining. > > I also took the opportunity to remove a number of unused helper > functions, and rework some others for consistency. > > This reduces the percentage of time spent in making BytecodeArrays > in CodeLoad from ~15% to ~11% according to perf. The > CoadLoad score increase by around 2%. > > BUG=v8:4280 > > Committed: https://crrev.com/b11a8b4d41bf09d6b3d6cf214fe3fb61faf01a64 > Cr-Commit-Position: refs/heads/master@{#39599} TBR=mythria@chromium.org,leszeks@chromium.org,rmcilroy@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4280 Review-Url: https://codereview.chromium.org/2360193003 Cr-Commit-Position: refs/heads/master@{#39612}
-
v8-autoroll authored
Rolling v8/base/trace_event/common to 6232c13e4edb36c84c61653fdae5a4afb5af9745 Rolling v8/build to 8438b8f51c0b125b298ad497c1bc1aa016c908ae Rolling v8/buildtools to 57649e5e2001ba1f5e5d45f5a838c616ea0e9cb9 Rolling v8/tools/clang to c1f39cb405e8af68a20e08e9485275a42260a88f TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2353363007 Cr-Commit-Position: refs/heads/master@{#39611}
-
kozyatinskiy authored
BUG=chromium:635948 R=dgozman@chromium.org,alph@chromium.org Committed: https://crrev.com/3d10918d2e1c57d72531c55a956262f5a72fceaa Review-Url: https://codereview.chromium.org/2332163002 Cr-Original-Commit-Position: refs/heads/master@{#39426} Cr-Commit-Position: refs/heads/master@{#39610}
-
- 21 Sep, 2016 30 commits
-
-
gsathya authored
BUG=v8:649078 Review-Url: https://codereview.chromium.org/2362503003 Cr-Commit-Position: refs/heads/master@{#39609}
-
kozyatinskiy authored
BUG=chromium:635948 R=dgozman@chromium.org,alph@chromium.org TBR=machenbach@chromium.org Review-Url: https://codereview.chromium.org/2338413003 Cr-Commit-Position: refs/heads/master@{#39608}
-
adamk authored
Revert of [heap] Concurrently free empty typed slot set chunks. (patchset #3 id:40001 of https://codereview.chromium.org/2352423002/ ) Reason for revert: TSAN failures on Linux64: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20TSAN/builds/11850 Also saw various threading-related flakiness on multiple bots. Original issue's description: > [heap] Concurrently free empty typed slot set chunks. > > BUG=chromium:648568 > > Committed: https://crrev.com/ff8101d8e8d5e14dfa89de1252c510e6a0775539 > Cr-Commit-Position: refs/heads/master@{#39605} TBR=ulan@chromium.org,hpayer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:648568 Review-Url: https://codereview.chromium.org/2358333002 Cr-Commit-Position: refs/heads/master@{#39607}
-
kozyatinskiy authored
Runtime.evaluate can return result by value. We need to provide more details why method call was failed. BUG=chromium:645640 R=dgozman@chromium.org,alph@chromium.org Committed: https://crrev.com/0965b9b5df532d3aa0583966ca60794b54f56943 Review-Url: https://codereview.chromium.org/2345263003 Cr-Original-Commit-Position: refs/heads/master@{#39574} Cr-Commit-Position: refs/heads/master@{#39606}
-
hpayer authored
BUG=chromium:648568 Review-Url: https://codereview.chromium.org/2352423002 Cr-Commit-Position: refs/heads/master@{#39605}
-
neis authored
R=adamk@chromium.org BUG=v8:1569 Review-Url: https://codereview.chromium.org/2353403003 Cr-Commit-Position: refs/heads/master@{#39604}
-
littledan authored
BUG=v8:5411 Review-Url: https://codereview.chromium.org/2354333003 Cr-Commit-Position: refs/heads/master@{#39603}
-
ahaas authored
TEST=unittests/WasmModuleVerifyTest.Regression_648070 BUG=chromium:648070 R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2356253002 Cr-Commit-Position: refs/heads/master@{#39602}
-
littledan authored
Review-Url: https://codereview.chromium.org/2353503006 Cr-Commit-Position: refs/heads/master@{#39601}
-
ahaas authored
This behavior is required by the WebAssembly spec. TEST=mjsunit/wasm/ffi-error.js:I64ParamsInSignatureThrows R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2360653002 Cr-Commit-Position: refs/heads/master@{#39600}
-
rmcilroy authored
This CL optimizes the code in BytecodeArrayBuilder and BytecodeArrayWriter by making the following main changes: - Move operand scale calculation out of BytecodeArrayWriter to the BytecodeNode constructor, where the decision on which operands are scalable can generally be statically decided by the compiler. - Move the maximum register calculation out of BytecodeArrayWriter and into BytecodeRegisterOptimizer (which is the only place outside BytecodeGenerator which updates which registers are used). This avoids the BytecodeArrayWriter needing to know the operand types of a node as it writes it. - Modify EmitBytecodes to use individual push_backs rather than building a buffer and calling insert, since this turns out to be faster. - Initialize BytecodeArrayWriter's bytecode vector by reserving 512 bytes, - Make common functions in Bytecodes constexpr so that they can be statically calculated by the compiler. - Move common functions and constructors in Bytecodes and BytecodeNode to the header so that they can be inlined. - Change large static switch statements in Bytecodes to const array lookups, and move to the header to allow inlining. I also took the opportunity to remove a number of unused helper functions, and rework some others for consistency. This reduces the percentage of time spent in making BytecodeArrays in CodeLoad from ~15% to ~11% according to perf. The CoadLoad score increase by around 2%. BUG=v8:4280 Review-Url: https://codereview.chromium.org/2351763002 Cr-Commit-Position: refs/heads/master@{#39599}
-
caitp authored
BUG=v8:5388 R=bmeurer@chromium.org, adamk@chromium.org TBR=hpayer@chromium.org Review-Url: https://codereview.chromium.org/2348493003 Cr-Commit-Position: refs/heads/master@{#39598}
-
rmcilroy authored
Review-Url: https://codereview.chromium.org/2353343002 Cr-Commit-Position: refs/heads/master@{#39597}
-
hpayer authored
BUG=chromium:648568 Review-Url: https://codereview.chromium.org/2360513002 Cr-Commit-Position: refs/heads/master@{#39596}
-
ahaas authored
Changing the global state can effect the outcome of later tests. R=jpp@chromium.org Review-Url: https://codereview.chromium.org/2359573003 Cr-Commit-Position: refs/heads/master@{#39595}
-
mstarzinger authored
This add support for ConsString objects allocated inline to the escape analysis pass. The raw hash field in such strings needs special handling similar to existing raw fields. This also contains materialization code within the deoptimizer as usual. R=bmeurer@chromium.org TEST=mjsunit/regress/regress-crbug-648737 BUG=chromium:648737 Review-Url: https://codereview.chromium.org/2357153002 Cr-Commit-Position: refs/heads/master@{#39594}
-
ishell authored
Each stub should have more meaningful descriptor instead. BUG=v8:5407 Review-Url: https://codereview.chromium.org/2356163002 Cr-Commit-Position: refs/heads/master@{#39593}
-
machenbach authored
This also adds sources missing for PPC and x87, fixes a few missing files in gyp due to wrong quotation and a few that were simply not included. The gn files are now authoritative, but the gcmole gyp and gn source lists are enforced to match exactly. This additional enforcement helped finding the bugs above and will be removed when we deprecate the gyp files. BUG=614645 NOTRY=true Review-Url: https://codereview.chromium.org/2352103002 Cr-Commit-Position: refs/heads/master@{#39592}
-
jarin authored
Review-Url: https://codereview.chromium.org/2360523002 Cr-Commit-Position: refs/heads/master@{#39591}
-
ishell authored
This cleanup is necessary to make HCallWithDescriptor support passing arguments on the stack. BUG=v8:5407 Review-Url: https://codereview.chromium.org/2352163004 Cr-Commit-Position: refs/heads/master@{#39590}
-
cbruni authored
Minidumps have gotten bigger stack ranges leading to long load times when using grokdump's web interface. A major factor seems to be the output size of the generated table. Using shorter class names and avoiding quotes for most attributes we can get a significant size reduction. BUG= Review-Url: https://codereview.chromium.org/2352303002 Cr-Commit-Position: refs/heads/master@{#39589}
-
ahaas authored
Set up Wasm Table and Memory constructors This only provides skeletons so far: the constructors work, but the types are not wired up with the import/export mechanism yet; methods are still nops. Also, fix errors generated from Wasm to be proper Error/TypeError instances instead of just strings. I took over this CL from rossberg@chromium.org. The original CL is https://codereview.chromium.org/2342623002 R=titzer@chromium.org, rossberg@chromium.org Review-Url: https://codereview.chromium.org/2350643003 Cr-Commit-Position: refs/heads/master@{#39588}
-
nikolaos authored
This patch moves the following parsing method to ParserBase: - ParseForStatement R=adamk@chromium.org, marja@chromium.org BUG= LOG=N Review-Url: https://codereview.chromium.org/2351233002 Cr-Commit-Position: refs/heads/master@{#39587}
-
cbruni authored
Handlify pointers in IncludesValueImpl and DirectCollectElementIndicesImpl. BUG=chromium:648373 Review-Url: https://codereview.chromium.org/2354773006 Cr-Commit-Position: refs/heads/master@{#39586}
-
hpayer authored
Do not overwrite a collector decision. BUG= Review-Url: https://codereview.chromium.org/2336943003 Cr-Commit-Position: refs/heads/master@{#39585}
-
balazs.kilvady authored
Review-Url: https://codereview.chromium.org/2184843002 Cr-Commit-Position: refs/heads/master@{#39584}
-
mstarzinger authored
This removes an optimization from the code generator that tries to materialize certain constants (i.e. context and closure) from the stackframe when possible. This does not work with Harmony tail calls which are split into several instructions. There have already been numerous bugs in this optimization, it is too fragile in its current form. R=bmeurer@chromium.org TEST=mjsunit/regress/regress-crbug-648539 BUG=chromium:648539 Review-Url: https://codereview.chromium.org/2357583003 Cr-Commit-Position: refs/heads/master@{#39583}
-
marija.antic authored
Port of https://crrev.com/14a5c18cc35b2c55b37de3bd0ad27941cf21cb68 BUG= Review-Url: https://codereview.chromium.org/2355743003 Cr-Commit-Position: refs/heads/master@{#39582}
-
verwaest authored
After parsing a function, if there's no masking declaration in the function scope, DeclareFunctionVar will also bind the function name to a variable. It will either bind it to the const/const-legacy function_ variable, or to a dynamic non-local if the function calls sloppy eval. Even if the variable is masked or sloppy eval is called, we still declare the function-var. The client immediately sets up the variable by assigning the resulting function to it. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2274133002 Cr-Commit-Position: refs/heads/master@{#39581}
-
machenbach authored
Revert of [inspector] provide more usefull error message for non serializable value (patchset #3 id:40001 of https://codereview.chromium.org/2345263003/ ) Reason for revert: Breaks https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/9932 See also https://github.com/v8/v8/wiki/Blink-layout-tests Original issue's description: > [inspector] provide more usefull error message for non serializable value > > Runtime.evaluate can return result by value. We need to provide more details why method call was failed. > > BUG=chromium:645640 > R=dgozman@chromium.org,alph@chromium.org > > Committed: https://crrev.com/0965b9b5df532d3aa0583966ca60794b54f56943 > Cr-Commit-Position: refs/heads/master@{#39574} TBR=dgozman@chromium.org,alph@chromium.org,kozyatinskiy@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:645640 Review-Url: https://codereview.chromium.org/2352263003 Cr-Commit-Position: refs/heads/master@{#39580}
-