- 13 Oct, 2016 40 commits
-
-
titzer authored
BUG= Review-Url: https://codereview.chromium.org/2417773004 Cr-Commit-Position: refs/heads/master@{#40282}
-
ishell authored
This CL also adds separate runtime call stats buckets for data handlers. BUG= Review-Url: https://codereview.chromium.org/2419513002 Cr-Commit-Position: refs/heads/master@{#40281}
-
rossberg authored
R=ahaas@chromium.org, titzer@chromium.org BUG=v8:5507 Review-Url: https://codereview.chromium.org/2421453002 Cr-Commit-Position: refs/heads/master@{#40280}
-
ulan authored
Revert of [heap] Cancel tasks before tearing down the heap. (patchset #2 id:20001 of https://codereview.chromium.org/2413203004/ ) Reason for revert: Timeout on gc stress bot. Original issue's description: > [heap] Cancel tasks before tearing down the heap. > > BUG=chromium:654343 > > Committed: https://crrev.com/9365463d6f1fc11b2369fff63ca0ac825c61eae4 > Cr-Commit-Position: refs/heads/master@{#40272} TBR=mlippautz@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:654343 Review-Url: https://codereview.chromium.org/2414073002 Cr-Commit-Position: refs/heads/master@{#40279}
-
Miran.Karic authored
When the test is executed in user mode qemu for mips64, it fails because the buffer is too small. Increasing the buffer fixes the problem. BUG= TEST=cctest/test-mark-compact/RegressJoinThreadsOnIsolateDeinit Review-Url: https://codereview.chromium.org/2416573002 Cr-Commit-Position: refs/heads/master@{#40278}
-
jgruber authored
This ports RegExpInitialize, IsRegExp, InternalMatch and InternalReplace to C++ / TurboFan. InternalMatch is in TurboFan because it calls RegExpExecStub and needs to construct a RegExpResult (which are, respectively, a PlatformStub and a CodeStubAssembler function). Except for LastMatchInfo (and GetSubstitution, which could be moved to string.js anytime), regexp.js is now completely empty. BUG=v8:5339 Review-Url: https://codereview.chromium.org/2409513003 Cr-Commit-Position: refs/heads/master@{#40277}
-
ziyang authored
GCC on S390 31-bit treats size_t as 'long unsigned int', which is incompatible with %d format specifier that expects an 'int'. Using the appropriate macro (PRIuS) instead. R=mlippautz@chromium.org, ulan@chromium.org BUG= Review-Url: https://codereview.chromium.org/2412563003 Cr-Commit-Position: refs/heads/master@{#40276}
-
verwaest authored
This is automatically taken into account in the Parser constructor already BUG=v8:5501 Review-Url: https://codereview.chromium.org/2409103005 Cr-Commit-Position: refs/heads/master@{#40275}
-
mythria authored
With --trace-ic flag, the function names and the source positions are not shown for interpreted functions. Interpreted functions have an extra frame built by bytecode handlers which has to be skipped to get the interpreted function's frame. Also the code offsets are computed differently for interpreted functions. BUG=v8:4280 Review-Url: https://codereview.chromium.org/2405173007 Cr-Commit-Position: refs/heads/master@{#40274}
-
rossberg authored
R=ahaas@chromium.org BUG= Review-Url: https://codereview.chromium.org/2411963003 Cr-Commit-Position: refs/heads/master@{#40273}
-
ulan authored
BUG=chromium:654343 Review-Url: https://codereview.chromium.org/2413203004 Cr-Commit-Position: refs/heads/master@{#40272}
-
ahaas authored
A decoder error sets builder_ to null, which causes builder_->StackCheck to segfault. R=titzer@chromium.org TEST=mjsunit/regress/wasm/loop-stack-check Review-Url: https://codereview.chromium.org/2416873002 Cr-Commit-Position: refs/heads/master@{#40271}
-
mvstanton authored
R=ishell@chromium.org BUG= Review-Url: https://codereview.chromium.org/2410353004 Cr-Commit-Position: refs/heads/master@{#40270}
-
verwaest authored
BUG=v8:5501 Review-Url: https://codereview.chromium.org/2417643004 Cr-Commit-Position: refs/heads/master@{#40269}
-
clemensh authored
This CL fixes the debugger interface to provide correct (high-level) information for asm.js frames. It moves the computation of the source position from the FrameInspector to the individual StackFrame implementations, such that we can easily specualize it for certain frame types, and can potentially reuse this in other locations. Also, we are finalizing the setup of the wasm module earlier, before executing the start function. This is required for correct stack traces during the execution of the start function. R=titzer@chromium.org, yangguo@chromium.org BUG=v8:4203 Review-Url: https://codereview.chromium.org/2413693003 Cr-Commit-Position: refs/heads/master@{#40268}
-
hpayer authored
BUG=chromium:648568 Review-Url: https://codereview.chromium.org/2418773002 Cr-Commit-Position: refs/heads/master@{#40267}
-
mvstanton authored
R=jarin@chromium.org BUG= Review-Url: https://codereview.chromium.org/2407153007 Cr-Commit-Position: refs/heads/master@{#40266}
-
neis authored
As part of this, introduce a new JSObject for iterating over the elements of a FixedArray. R=adamk@chromium.org,bmeurer@chromium.org TBR=ulan@chromium.org BUG=v8:1569 Review-Url: https://codereview.chromium.org/2407423002 Cr-Commit-Position: refs/heads/master@{#40265}
-
verwaest authored
BUG=v8:5501 Review-Url: https://codereview.chromium.org/2413763004 Cr-Commit-Position: refs/heads/master@{#40264}
-
neis authored
R=bmeurer@chromium.org BUG=v8:5439 Review-Url: https://codereview.chromium.org/2407823002 Cr-Commit-Position: refs/heads/master@{#40263}
-
Ilija.Pavlovic authored
AllocateAlignedMemory calls ReserveAlignedMemory which increments size_ value. In some cases AllocateAlignedMemory can return NULL value. Before returning NULL, AllocateAlignedMemory should decrease size_ value. TEST=cctest/test-spaces/LargeObjectSpace BUG= Review-Url: https://codereview.chromium.org/2418733002 Cr-Commit-Position: refs/heads/master@{#40262}
-
bmeurer authored
When we inlined a [[Construct]] call to a subclass constructor, we can also inline the super constructor call (either explicit or implicit), since we have a concrete JSFunction constant for the subclass and we can thus constant-fold the %_GetSuperConstructor intrinsic. We don't need any guards here since the prototype of subclass constructors is non-writable, non-configurable in ES6. BUG=v8:5517 R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2409423006 Cr-Commit-Position: refs/heads/master@{#40261}
-
jochen authored
Instead of suppressing the linker warnings and disallowing incremental linking, just fix the annotations.. R=machenbach@chromium.org,jgruber@chromium.org BUG= Review-Url: https://codereview.chromium.org/2420603002 Cr-Commit-Position: refs/heads/master@{#40260}
-
verwaest authored
BUG= Review-Url: https://codereview.chromium.org/2417833002 Cr-Commit-Position: refs/heads/master@{#40259}
-
marja authored
It belongs there more logically. In addition, this is a pre-step needed for preparsing the parameters of a preparsed function. In addition, move the "subtract rest parameter from arity" logic from Parser to (Pre)?ParserFormalParameters. BUG=v8:5515 Review-Url: https://codereview.chromium.org/2414003002 Cr-Commit-Position: refs/heads/master@{#40258}
-
machenbach authored
NOTRY=true TBR=adamk, caitp Review-Url: https://codereview.chromium.org/2419433006 Cr-Commit-Position: refs/heads/master@{#40257}
-
verwaest authored
Turn AllowsLazyParsingWithoutUnresolvedVariables into a whitelist stopping at the outer parsed context. Any context outer to what we're parsing already has proper context allocation, so we don't need to check those scopes. BUG=v8:5501 Review-Url: https://codereview.chromium.org/2417643003 Cr-Commit-Position: refs/heads/master@{#40256}
-
ishell authored
BUG= Review-Url: https://codereview.chromium.org/2412043003 Cr-Commit-Position: refs/heads/master@{#40255}
-
ahaas authored
In a fuzzer testcase I found locally the ast-decoder spent a lot of time in the decoding of kExprBrTable after the decoder already found an error. I did not add a test because the fuzzer test case did not actually crash. It only run out of memory in the chromium fuzzer. R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2413863003 Cr-Commit-Position: refs/heads/master@{#40254}
-
jgruber authored
This moves the implementation of @@replace from regexp.js to builtins-regexp.cc (the TurboFan fast path) and runtime-regexp.cc (slow path). The fast path handles all cases in which the regexp itself is an unmodified JSRegExp instance, the given 'replace' argument is not callable and does not contain any '$' characters (i.e. we are doing a string replacement). BUG=v8:5339 Review-Url: https://codereview.chromium.org/2398423002 Cr-Commit-Position: refs/heads/master@{#40253}
-
marja authored
BUG= Review-Url: https://codereview.chromium.org/2412493008 Cr-Commit-Position: refs/heads/master@{#40252}
-
ahaas authored
Stack checks in loops allows to interrupt loops. BUG=cctest/test-run-wasm-module/TestInterruptLoop R=titzer@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2405293002 Cr-Commit-Position: refs/heads/master@{#40251}
-
ulan authored
BUG=chromium:652721 Review-Url: https://codereview.chromium.org/2406363002 Cr-Commit-Position: refs/heads/master@{#40250}
-
jgruber authored
This fixes the code-path in RegExpExec in which both the passed exec argument and regexp.exec are not callable and regexp is a JSRegExp. In this case, we fall back to the default RegExp.prototype.exec implementation. The arguments for Execution::call were incorrect. BUG=v8:5339 Review-Url: https://codereview.chromium.org/2415073002 Cr-Commit-Position: refs/heads/master@{#40249}
-
verwaest authored
I don't see a reason why we can't benefit from preparsing such functions. We don't necessarily compile them, so fully parsing them when unnecessary is just additional overhead. BUG=v8:5501 Review-Url: https://codereview.chromium.org/2413213002 Cr-Commit-Position: refs/heads/master@{#40248}
-
verwaest authored
BUG=v8:5501,chromium:655122 Review-Url: https://codereview.chromium.org/2419663005 Cr-Commit-Position: refs/heads/master@{#40247}
-
ahaas authored
BUG=chromium:654377 TEST=mjsunit/regress/wasm/regression-654377 R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2403013002 Cr-Commit-Position: refs/heads/master@{#40246}
-
mvstanton authored
BUG= Review-Url: https://codereview.chromium.org/2402313003 Cr-Commit-Position: refs/heads/master@{#40245}
-
zhengxing.li authored
port c15c5827 (r40206) original commit message: This is the next step to unify the Call/Construct feedback collection and prepare it to be able to collect SharedFunctionInfo feedback. This also reduces the CallICStub overhead quite a bit since we only need one stub per mode (and tail call mode), not also one per call arity. BUG= Review-Url: https://codereview.chromium.org/2409953005 Cr-Commit-Position: refs/heads/master@{#40244}
-
neis authored
R=jgruber@chromium.org BUG= Review-Url: https://codereview.chromium.org/2407153003 Cr-Commit-Position: refs/heads/master@{#40243}
-