- 18 Feb, 2016 2 commits
-
-
fmeawad authored
This CL adds a TRACE_EVENT where there is an isolated LOG, a HistogramTimer or a TimerEvent. Once we have a d8 tracing controller, all TimerEvents will be removed since they do not provide an added value over TRACE_EVENTs. HistogramTimers will remain, but their functionality will be limited to Histograms only. BUG=v8:4562 LOG=N Review URL: https://codereview.chromium.org/1707563002 Cr-Commit-Position: refs/heads/master@{#34099}
-
v8-autoroll authored
Rolling v8/tools/clang to 893d75d10357b96b4441ca9ffa363654bd2a07df TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1705413002 Cr-Commit-Position: refs/heads/master@{#34098}
-
- 17 Feb, 2016 38 commits
-
-
hablich authored
R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1703103002 Cr-Commit-Position: refs/heads/master@{#34097}
-
mbrandy authored
Port 32b4bc13 Original commit message: This CL introduces two new bytecodes TailCall and TailCallWide. R=ishell@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG=v8:4698,v8:4687 LOG=N Review URL: https://codereview.chromium.org/1705913002 Cr-Commit-Position: refs/heads/master@{#34096}
-
machenbach authored
Revert of Add Scoped Context Info (Isolate) to V8 Traces (patchset #5 id:80001 of https://codereview.chromium.org/1686233002/ ) Reason for revert: [Sheriff] Breaks arm cross-compile: https://build.chromium.org/p/client.v8/builders/V8%20Arm%20-%20debug%20builder/builds/7825/ Original issue's description: > Add Scoped Context Info (Isolate) to V8 Traces > > This patch adds the newly added support for contexts in V8 Tracing, as well > as use it to mark all the entry points for a V8 Isolate. > > BUG=v8:4565 > LOG=N > > Committed: https://crrev.com/44823c3c6965966c63b7e2e2361d0f2a58d196ea > Cr-Commit-Position: refs/heads/master@{#34092} TBR=jochen@chromium.org,fmeawad@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4565 Review URL: https://codereview.chromium.org/1710573002 Cr-Commit-Position: refs/heads/master@{#34095}
-
bmeurer authored
We already have a proper abstraction for dealing with subclassable builtins, namely JSObject::New, so we should use that instead of inlining this rather complex code sequence multiple times. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1709563003 Cr-Commit-Position: refs/heads/master@{#34094}
-
binji authored
This is not currently implemented in the simulator, just the assembler and disassembler. BUG=v8:4614 LOG=y Review URL: https://codereview.chromium.org/1699173003 Cr-Commit-Position: refs/heads/master@{#34093}
-
fmeawad authored
This patch adds the newly added support for contexts in V8 Tracing, as well as use it to mark all the entry points for a V8 Isolate. BUG=v8:4565 LOG=N Review URL: https://codereview.chromium.org/1686233002 Cr-Commit-Position: refs/heads/master@{#34092}
-
machenbach authored
Revert of [fullcodegen] Remove the hacky %_FastOneByteArrayJoin intrinsic. (patchset #1 id:1 of https://codereview.chromium.org/1708523002/ ) Reason for revert: [Sheriff] Speculative revert for adding arm flakes: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm%20-%20sim/builds/5756 https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm%20-%20sim%20-%20novfp3/builds/3375/ And some more... Original issue's description: > [fullcodegen] Remove the hacky %_FastOneByteArrayJoin intrinsic. > > This intrinsic was only supported in fullcodegen, and is actually no > longer relevant for SunSpider peak performance it seems, so let's get > rid of it and maybe just implement Array.prototype.join with a fast > path at some point instead. > > R=mstarzinger@chromium.org > > Committed: https://crrev.com/ccf12b4bede3f1ce3ce14fb33bcc4041525a40af > Cr-Commit-Position: refs/heads/master@{#34084} TBR=mstarzinger@chromium.org,bmeurer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1709693002 Cr-Commit-Position: refs/heads/master@{#34091}
-
mbrandy authored
R=joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1710453002 Cr-Commit-Position: refs/heads/master@{#34090}
-
bbudge authored
Adds kSimd128 to MachineRepresentation. Adds a Simd128Register concept that's platform independent. Adds UntaggedSimd128 to types.h. LOG=N BUG=v8:4124 Review URL: https://codereview.chromium.org/1693963004 Cr-Commit-Position: refs/heads/master@{#34089}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1703083002 Cr-Commit-Position: refs/heads/master@{#34088}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1706833002 Cr-Commit-Position: refs/heads/master@{#34087}
-
verwaest authored
I replaced the hidden string with hidden_properties_symbol, so we don't need the extra hash-check anymore. This is slightly faster anyway. BUG= Review URL: https://codereview.chromium.org/1707653003 Cr-Commit-Position: refs/heads/master@{#34086}
-
mbrandy authored
Port 0d595bb0 Original commit message: It's fine to only have the runtime call here, as it's only used in the debug mirror. R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1707683002 Cr-Commit-Position: refs/heads/master@{#34085}
-
bmeurer authored
This intrinsic was only supported in fullcodegen, and is actually no longer relevant for SunSpider peak performance it seems, so let's get rid of it and maybe just implement Array.prototype.join with a fast path at some point instead. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1708523002 Cr-Commit-Position: refs/heads/master@{#34084}
-
ishell authored
This CL introduces two new bytecodes TailCall and TailCallWide. BUG=v8:4698,v8:4687 LOG=N Review URL: https://codereview.chromium.org/1698273003 Cr-Commit-Position: refs/heads/master@{#34083}
-
machenbach authored
Revert of More simplification and unification of frame handling (patchset #5 id:80001 of https://codereview.chromium.org/1702593002/ ) Reason for revert: [Sheriff] Breaks nosnap debug: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/5329 Original issue's description: > More simplification and unification of frame handling > > Frame slots indexes numbers are used more consistently for > computation in both TurboFan and Crankshaft. Specifically, > Crankshaft now uses frame slot indexes in LChunk, removing > the need for some special-case maths when building the > deoptimization translation table. > > LOG=N > R=mstarzinger@chromium.org > > Committed: https://crrev.com/81423b84dbb2eaf7e1a57b0f6029fc8e643b4755 > Cr-Commit-Position: refs/heads/master@{#34078} TBR=mstarzinger@chromium.org,jarin@chromium.org,danno@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1708583002 Cr-Commit-Position: refs/heads/master@{#34082}
-
mstarzinger authored
This removes the CompilationInfo field from the BytecodeGraphBuilder class. The intention is to reduce the risk of using uninitialized or unavailable values from the CompilationInfo (e.g. values that are only available after parsing). R=rmcilroy@chromium.org Review URL: https://codereview.chromium.org/1704913002 Cr-Commit-Position: refs/heads/master@{#34081}
-
bmeurer authored
There's no need to have inline platform code for this intrinsic, which is only used when generating a descriptive string for an error, the runtime call is just fine here. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1706743002 Cr-Commit-Position: refs/heads/master@{#34080}
-
machenbach authored
BUG=chromium:535160 LOG=n TBR=tandrii@chromium.org, kjellander@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1706783002 Cr-Commit-Position: refs/heads/master@{#34079}
-
danno authored
Frame slots indexes numbers are used more consistently for computation in both TurboFan and Crankshaft. Specifically, Crankshaft now uses frame slot indexes in LChunk, removing the need for some special-case maths when building the deoptimization translation table. LOG=N R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1702593002 Cr-Commit-Position: refs/heads/master@{#34078}
-
bmeurer authored
It's dead^Wa runtime call Jim! R=jarin@chromium.org Review URL: https://codereview.chromium.org/1702313002 Cr-Commit-Position: refs/heads/master@{#34077}
-
hablich authored
R=machenbach@chromium.org TBR=danno@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1706753002 Cr-Commit-Position: refs/heads/master@{#34076}
-
machenbach authored
BUG=chromium:535160 LOG=n TBR=tandrii@chromium.org, kjellander@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1703853002 Cr-Commit-Position: refs/heads/master@{#34075}
-
nikolaos authored
R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1704963002 Cr-Commit-Position: refs/heads/master@{#34074}
-
mstarzinger authored
This removes the language mode parameter from all JSCall operators. The information is no longer used anywhere and is not threaded through the interpreter bytecode. We should only thread it through the bytecode if it has a semantic impact on the compilation. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1709493002 Cr-Commit-Position: refs/heads/master@{#34073}
-
bmeurer authored
Everything that HCallStub does can easily be done using the more general HCallWithDescriptor, so there's no need to have this dedicated instruction around. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1705633004 Cr-Commit-Position: refs/heads/master@{#34072}
-
ulan authored
If sweeping is in progress then we need to filter out slots in free space after array trimming, because the sweeper will add the free space into free list. This CL also fixes a bug in SlotSet::RemoveRange. BUG=chromium:587004 LOG=NO TBR=hpayer@chromium.org Review URL: https://codereview.chromium.org/1701963003 Cr-Commit-Position: refs/heads/master@{#34071}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1705713002 Cr-Commit-Position: refs/heads/master@{#34070}
-
bmeurer authored
Also move Object.is implementation to C++ builtin, which is faster than the current implementation. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1695743003 Cr-Commit-Position: refs/heads/master@{#34069}
-
bmeurer authored
There's no point in having the setup or the toString/valueOf methods in JavaScript. The full setup can be done during bootstrapping when the Boolean constructor is created, and the prototype methods don't benefit from JS + %_ at all. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1701273003 Cr-Commit-Position: refs/heads/master@{#34068}
-
mstarzinger authored
R=rossberg@chromium.org,bmeurer@chromium.org,verwaest@chromium.org BUG=v8:3956 LOG=n Review URL: https://codereview.chromium.org/1700993002 Cr-Commit-Position: refs/heads/master@{#34067}
-
balazs.kilvady authored
Port fd8fd05c Original commit message: This functionality is useful for stubs that need to walk the stack. The new machine operator, LoadParentFramePointer doesn't force the currently compiling method to have a frame in contrast to LoadFramePointer. Instead, it adapts accordingly when frame elision is possible, making efficient stack walks possible without incurring a performance penalty for small stubs that can benefit from frame elision. BUG= Review URL: https://codereview.chromium.org/1701933003 Cr-Commit-Position: refs/heads/master@{#34066}
-
machenbach authored
BUG=chromium:535160 LOG=n TBR=tandrii@chromium.org, kjellander@chromium.org Review URL: https://codereview.chromium.org/1709503002 Cr-Commit-Position: refs/heads/master@{#34065}
-
zhengxing.li authored
port fd8fd05c (r34014) original commit message: This functionality is useful for stubs that need to walk the stack. The new machine operator, LoadParentFramePointer dosn't force the currently compiling method to have a frame in contrast to LoadFramePointer. Instead, it adapts accordingly when frame elision is possible, making efficient stack walks possible without incurring a performance penalty for small stubs that can benefit from frame elision. BUG= Review URL: https://codereview.chromium.org/1705673002 Cr-Commit-Position: refs/heads/master@{#34064}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1702623002 Cr-Commit-Position: refs/heads/master@{#34063}
-
zhengxing.li authored
port e0129d0f (r33986) original commit message: Turn the fast case of ArgumentsAccessStub into a new stub FastNewSloppyArgumentsStub, which is similar to the existing FastNewStrictArgumentsStub, although not polished yet, and the slow case always went to the runtime anyway, so we can just directly emit a runtime call there. BUG= Review URL: https://codereview.chromium.org/1701983004 Cr-Commit-Position: refs/heads/master@{#34062}
-
alph authored
CPU profiler probes stack frame to find if it's in a valid state. Under simulator it might happen the frame is not initialized and MSAN repors that. That's totally ok. Suppress the warning. BUG=v8:4751 LOG=N Review URL: https://codereview.chromium.org/1700533003 Cr-Commit-Position: refs/heads/master@{#34061}
-
verwaest authored
Minor improvements measured through by https://github.com/kpdecker/six-speed/blob/master/tests/object-assign/object-assign.es6. Mostly due to inlining of NowContains on the FieldType Review URL: https://codereview.chromium.org/1703513002 Cr-Commit-Position: refs/heads/master@{#34060}
-