- 15 Sep, 2015 2 commits
-
-
v8-autoroll authored
Rolling v8/buildtools to f7310ee61725e68b1c8921e381830362cf4f0999 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1342063002 Cr-Commit-Position: refs/heads/master@{#30724}
-
alph authored
Filtering out functions does not allow sample processor to figure out if a sample hit a non-frame region of a function. The filtering should be done in the frontend. BUG=chromium:529931 LOG=N Review URL: https://codereview.chromium.org/1337743002 Cr-Commit-Position: refs/heads/master@{#30723}
-
- 14 Sep, 2015 18 commits
-
-
mbrandy authored
Port eadfd666 Original commit message: The String constructor was somewhat complex with a lot of micro optimizations that are not relevant or even misguided. It would be really hard to port that code to ES6, which requires String to be subclassable. So as a first step we reduced the necessary complexity to the bare minimum (also removing the last user of the fairly complex MacroAssembler::LookupNumberStringCache method). This also removes the counters for the String constructor, which were not properly exposed anymore (and not kept in sync with inlined versions of the String constructor anyway). R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1339143002 Cr-Commit-Position: refs/heads/master@{#30722}
-
mbrandy authored
Port e7fb2339 Original commit message: Adds support for JS calls to the interpreter. In order to support calls from the interpreter, the PushArgsAndCall builtin is added which pushes a sequence of arguments onto the stack and calls builtin::Call. Adds the Call bytecode. R=rmcilroy@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1345543002 Cr-Commit-Position: refs/heads/master@{#30721}
-
gdeepti authored
Enhance the perf runner to run with the profiler and print the summary for each d8 run. This automates running the profiler with multiple benchmarks. BUG=None LOG=N TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1327033003 Cr-Commit-Position: refs/heads/master@{#30720}
-
machenbach authored
Revert of VectorICs: ia32 store ics need a virtual register. (patchset #3 id:40001 of https://codereview.chromium.org/1336313002/ ) Reason for revert: [Sheriff] Breaks GC stress on mac: http://build.chromium.org/p/client.v8/builders/V8%20Mac%20GC%20Stress/builds/2536 Original issue's description: > VectorICs: ia32 store ics need a virtual register. > > Some pretty hacky code was used to carry out the tail-call > handler dispatch on ia32 vector stores due to a lack > of free registers. It really tanks performance. A better > approach is to use a virtual register on the isolate. > > BUG= > > Committed: https://crrev.com/b26e98f19b5e77df50cb4a259f099ee6afa335e3 > Cr-Commit-Position: refs/heads/master@{#30718} TBR=jkummerow@chromium.org,vogelheim@chromium.org,mvstanton@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1340123002 Cr-Commit-Position: refs/heads/master@{#30719}
-
mvstanton authored
Some pretty hacky code was used to carry out the tail-call handler dispatch on ia32 vector stores due to a lack of free registers. It really tanks performance. A better approach is to use a virtual register on the isolate. BUG= Review URL: https://codereview.chromium.org/1336313002 Cr-Commit-Position: refs/heads/master@{#30718}
-
cbruni authored
BUG= Review URL: https://codereview.chromium.org/1341763002 Cr-Commit-Position: refs/heads/master@{#30717}
-
mstarzinger authored
This prevents the internal objects-visiting.h to be usable outisde of the "heap" directory. The static object visitation is only usefull within the GC and is now properly encapsulated. R=hpayer@chromium.org,mlippautz@chromium.org Review URL: https://codereview.chromium.org/1328003002 Cr-Commit-Position: refs/heads/master@{#30716}
-
cbruni authored
BUG= Review URL: https://codereview.chromium.org/1338983003 Cr-Commit-Position: refs/heads/master@{#30715}
-
mlippautz authored
Parallel compaction, i.e., concurrently moving of objects (and code) requires proper synchronization in the logger. R=hpayer@chromium.org BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1338253002 Cr-Commit-Position: refs/heads/master@{#30714}
-
mlippautz authored
BUG=chromium:531322 LOG=N R=jochen@chromium.org Review URL: https://codereview.chromium.org/1337943005 Cr-Commit-Position: refs/heads/master@{#30713}
-
mstarzinger authored
This moves scavenging functionality into a separate component so that neither the scavenger nor objects-visiting need to be exposed outside the heap. R=hpayer@chromium.org,mlippautz@chromium.org Review URL: https://codereview.chromium.org/1323993004 Cr-Commit-Position: refs/heads/master@{#30712}
-
cbruni authored
LOG=N BUG=chromium:531348 Review URL: https://codereview.chromium.org/1344493004 Cr-Commit-Position: refs/heads/master@{#30711}
-
rmcilroy authored
Adds support for JS calls to the interpreter. In order to support calls from the interpreter, the PushArgsAndCall builtin is added which pushes a sequence of arguments onto the stack and calls builtin::Call. Adds the Call bytecode. MIPS port contributed by akos.palfi@imgtec.com in https://codereview.chromium.org/1334873002/ BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1323463005 Cr-Commit-Position: refs/heads/master@{#30710}
-
neis authored
BUG= Review URL: https://codereview.chromium.org/1331553002 Cr-Commit-Position: refs/heads/master@{#30709}
-
neis authored
Also clarify some comments. R=jarin@chromium.org BUG= Review URL: https://codereview.chromium.org/1328193003 Cr-Commit-Position: refs/heads/master@{#30708}
-
bmeurer authored
These builtins present an optimization for the general addition case, where one side is already known to be a string. Unfortunately this optimization is wrong in the presence of @@toPrimitive (there are some ideas how to implement a similar optimization using the prototype backpointer mechanism that jkummerow@ introduced earlier). So this also removes the broken %_IsStringWrapperSafeForDefaultValueOf, which is the key part of the optimization mentioned above. R=mstarzinger@chromium.org BUG=v8:4307 LOG=n Review URL: https://codereview.chromium.org/1336273002 Cr-Commit-Position: refs/heads/master@{#30707}
-
bmeurer authored
The String constructor was somewhat complex with a lot of micro optimizations that are not relevant or even misguided. It would be really hard to port that code to ES6, which requires String to be subclassable. So as a first step we reduced the necessary complexity to the bare minimum (also removing the last user of the fairly complex MacroAssembler::LookupNumberStringCache method). This also removes the counters for the String constructor, which were not properly exposed anymore (and not kept in sync with inlined versions of the String constructor anyway). R=jarin@chromium.org Review URL: https://codereview.chromium.org/1335193002 Cr-Commit-Position: refs/heads/master@{#30706}
-
cbruni authored
In certiain cases the ArgumentsIteratorSetter would trigger an invalid state in the LookupIterator when being overridden. This is now solved by bypassing the SetDataProperty and directly using DefinePropertyOrElementIgnoringAttributes since we know exactly which property we're going to install LOG=N BUG=chromium:521484 Review URL: https://codereview.chromium.org/1332873002 Cr-Commit-Position: refs/heads/master@{#30705}
-
- 13 Sep, 2015 1 commit
-
-
tandrii authored
R=machenbach@chromium.org BUG=530941 NOTRY=true NOPRESUBMIT=true Review URL: https://codereview.chromium.org/1340773002 Cr-Commit-Position: refs/heads/master@{#30704}
-
- 11 Sep, 2015 14 commits
-
-
brettw authored
The GN default optimization flag is changing from being specific to the debug/release status of the build to always being "default_optimization" so it's easier to override without being conditional on the exact setup in BUILDCONFIG.gn. See https://codereview.chromium.org/1324623005/ Since V8 is DEPS-ed in, it will need to support both modes to allow a landing. This patch uses a temporary transitional flag I added to BUILDCONFIG to indicate which variant should be used. After the patch is landed, we can remove the new conditions and just remove default_optimization. Review URL: https://codereview.chromium.org/1333963002 Cr-Commit-Position: refs/heads/master@{#30703}
-
yurys authored
BUG=None LOG=N Review URL: https://codereview.chromium.org/1332683002 Cr-Commit-Position: refs/heads/master@{#30702}
-
mstarzinger authored
R=mlippautz@chromium.org Review URL: https://codereview.chromium.org/1334273002 Cr-Commit-Position: refs/heads/master@{#30701}
-
akos.palfi authored
Correctly save and restore FP registers in cctest/ConvertDToI to avoid accidental register overwriting by the generated code. Note: This failure is manifested only in R6 mode. TEST=test/cctest/interpreter/test-interpreter BUG= Review URL: https://codereview.chromium.org/1337023002 Cr-Commit-Position: refs/heads/master@{#30700}
-
balazs.kilvady authored
Port 622fa0ea Original commit message: Currently we do this dance between the CallConstructStub, the CALL_* builtins and the %GetConstructorDelegate, %GetProxyTrap, and %Apply runtime functions for every [[Construct]] operation on non-function callables. This is complexity is unnecessary, and can be simplified to work without any JS builtin. This will also make it a lot easier to implement ES6 compliant [[Construct]] for proxies. Also sanitize the invariant for CallConstructStub, which up until now always restored the context itself, but that force us to always create another copy of all arguments in case of proxies and other callables, so we can relax that constraint by making the caller restore the context (this only affects fullcodegen, since the optimizing compilers already properly restore the context anyway). BUG= Review URL: https://codereview.chromium.org/1340553002 Cr-Commit-Position: refs/heads/master@{#30699}
-
mbrandy authored
Port 9fc4fc14 R=mlippautz@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1339673002 Cr-Commit-Position: refs/heads/master@{#30698}
-
mbrandy authored
Port 39604dda Original commit message: Just use a %ThrowStackOverflow runtime function instead, which does the trick, especially since the Isolate already has a preallocated StackOverflow error for that. R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1334303002 Cr-Commit-Position: refs/heads/master@{#30697}
-
mbrandy authored
Port 622fa0ea Original commit message: Currently we do this dance between the CallConstructStub, the CALL_* builtins and the %GetConstructorDelegate, %GetProxyTrap, and %Apply runtime functions for every [[Construct]] operation on non-function callables. This is complexity is unnecessary, and can be simplified to work without any JS builtin. This will also make it a lot easier to implement ES6 compliant [[Construct]] for proxies. Also sanitize the invariant for CallConstructStub, which up until now always restored the context itself, but that force us to always create another copy of all arguments in case of proxies and other callables, so we can relax that constraint by making the caller restore the context (this only affects fullcodegen, since the optimizing compilers already properly restore the context anyway). R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1338663003 Cr-Commit-Position: refs/heads/master@{#30696}
-
mlippautz authored
BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1332283002 Cr-Commit-Position: refs/heads/master@{#30695}
-
Michael Achenbach authored
Cr-Commit-Position: refs/heads/master@{#30694}
-
bmeurer authored
Just use a %ThrowStackOverflow runtime function instead, which does the trick, especially since the Isolate already has a preallocated StackOverflow error for that. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1337883002 Cr-Commit-Position: refs/heads/master@{#30693}
-
mvstanton authored
This is so we can build with the flag on in the snapshot. D8 then needs to be run with --vector-stores. BUG= R=machenbach@chromium.org Review URL: https://codereview.chromium.org/1339593002 Cr-Commit-Position: refs/heads/master@{#30692}
-
bmeurer authored
Currently we do this dance between the CallConstructStub, the CALL_* builtins and the %GetConstructorDelegate, %GetProxyTrap, and %Apply runtime functions for every [[Construct]] operation on non-function callables. This is complexity is unnecessary, and can be simplified to work without any JS builtin. This will also make it a lot easier to implement ES6 compliant [[Construct]] for proxies. Also sanitize the invariant for CallConstructStub, which up until now always restored the context itself, but that force us to always create another copy of all arguments in case of proxies and other callables, so we can relax that constraint by making the caller restore the context (this only affects fullcodegen, since the optimizing compilers already properly restore the context anyway). R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1335723002 Cr-Commit-Position: refs/heads/master@{#30691}
-
mtrofin authored
Grouping of live ranges that would be beneficial if allocated on the same register. Currently, that means phi outputs and inputs. Review URL: https://codereview.chromium.org/1312473018 Cr-Commit-Position: refs/heads/master@{#30690}
-
- 10 Sep, 2015 5 commits
-
-
mbrandy authored
PPC: Vector ICs: The Oracle needs to report feedback for the object literals and the count operation. Port 752b0308 Original commit message: The refactoring is because it's awkward and error-prone to deterimine which IC slot an ObjectLiteralProperty uses for feedback. The fix is for each one to know it's own slot. In the numbering pass, we allocate slots for the ObjectLiteral, then hand out those slots into the properties. It adds one word to the ObjectLiteralProperty expression - I'm investigating if thats a problem. This changes makes compiling the object literal cleaner across the three compilers. Also, the slot allocation logic in ObjectLiteral::ComputeFeedbackRequirements() was refactoring to mimic the style in full-codegen. This is useful since it must remain in sync with FullCodegen::VisitObjectLiteral(). R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1331893003 Cr-Commit-Position: refs/heads/master@{#30689}
-
yurys authored
When we cannot map top frame's pc to a code object and top frame is JS frame we now assume that it was a frameless invocation of a native function (e.g. __fmod) and try to resolve address on top of the stack into a JS function. BUG=chromium:529931 LOG=Y Review URL: https://codereview.chromium.org/1315683007 Cr-Commit-Position: refs/heads/master@{#30688}
-
oth authored
Add skeleton version bytecode-graph-builder.{h,cc} for existing bytecodes. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1291693004 Cr-Commit-Position: refs/heads/master@{#30687}
-
mvstanton authored
The refactoring is because it's awkward and error-prone to deterimine which IC slot an ObjectLiteralProperty uses for feedback. The fix is for each one to know it's own slot. In the numbering pass, we allocate slots for the ObjectLiteral, then hand out those slots into the properties. It adds one word to the ObjectLiteralProperty expression - I'm investigating if thats a problem. This changes makes compiling the object literal cleaner across the three compilers. Also, the slot allocation logic in ObjectLiteral::ComputeFeedbackRequirements() was refactoring to mimic the style in full-codegen. This is useful since it must remain in sync with FullCodegen::VisitObjectLiteral(). Review URL: https://codereview.chromium.org/1321993004 Cr-Commit-Position: refs/heads/master@{#30686}
-
conradw authored
Inner functions must be eagerly parsed for scope analysis, but the full AST is also kept around even though it's not needed. This CL mitigates this problem by allocating some AstNodes of the inner function to a temporary Zone which is deallocated once the scope information has been built. The remaining nodes (such as VariableProxy) must persist until scope analysis actually happens, and have to be allocated to a parser-persistent Zone. BUG=417697 LOG=N Review URL: https://codereview.chromium.org/1304923004 Cr-Commit-Position: refs/heads/master@{#30685}
-