- 06 Apr, 2016 29 commits
-
-
cbruni authored
All the counters, trace events and runtime call stats roughly create a 30% overhead when calling into the runtime. This CL factors out the counters into separate non-inlined functions. This way we can reduce the overhead to a minimum and still have some useful stats without a compile-time flag. BUG=chromium:596055 LOG=n Review URL: https://codereview.chromium.org/1868513002 Cr-Commit-Position: refs/heads/master@{#35308}
-
marija.antic authored
Implementation of turbofan operators Word32PairShl, Word32PairShr, Word32PairSar, Int32AddPair and Int32SubPair for MIPS. Port of: https://codereview.chromium.org/1765973002/ https://codereview.chromium.org/1778893004/ https://codereview.chromium.org/1778493004/ https://codereview.chromium.org/1778893005/ https://codereview.chromium.org/1842013002/ Added tests for Word32PairShr and Word32PairSar in test-run-machops.cc. BUG= Review URL: https://codereview.chromium.org/1819383002 Cr-Commit-Position: refs/heads/master@{#35307}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1861963003 Cr-Commit-Position: refs/heads/master@{#35306}
-
mattloring authored
If no objects allocated at a location are live when a profile is collected we report a zero count sample. This is confusing to those looking at the profiles and will leak memory. We now delete allocations once the number of sampled live objects for that location reaches zero. R=ofrobots@google.com BUG= Review URL: https://codereview.chromium.org/1828333002 Cr-Commit-Position: refs/heads/master@{#35305}
-
machenbach authored
BUG=535160 TBR=sergiyb@chromium.org, kjellander@chromium.org NOTRY=true NOPRESUBMIT=true Review URL: https://codereview.chromium.org/1864963003 Cr-Commit-Position: refs/heads/master@{#35304}
-
cbruni authored
BUG= NOTRY=true NOPRESUBMIT=true NOTREECHECKS=true Review URL: https://codereview.chromium.org/1865903002 Cr-Commit-Position: refs/heads/master@{#35303}
-
cbruni authored
drive-by-fix: unify template parameters BUG=chromium:586068 LOG=n Review URL: https://codereview.chromium.org/1857163002 Cr-Commit-Position: refs/heads/master@{#35302}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1865873002 Cr-Commit-Position: refs/heads/master@{#35301}
-
cbruni authored
BUG= Review URL: https://codereview.chromium.org/1834613003 Cr-Commit-Position: refs/heads/master@{#35300}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1853373004 Cr-Commit-Position: refs/heads/master@{#35299}
-
ssanfilippo authored
An overzealous removal in https://crrev.com/9e39a9fff1c2966a3f650a4c31dbbe533886d614 caused the disassembly not to be annotated with ticks, even when requested. LOG=N Review URL: https://codereview.chromium.org/1861323002 Cr-Commit-Position: refs/heads/master@{#35298}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1865863003 Cr-Commit-Position: refs/heads/master@{#35297}
-
hpayer authored
BUG=chromium:600258 LOG=n Review URL: https://codereview.chromium.org/1864433003 Cr-Commit-Position: refs/heads/master@{#35296}
-
bmeurer authored
Now that we pass all these tests, we need to update the test expectations. TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1864013002 Cr-Commit-Position: refs/heads/master@{#35295}
-
mlippautz authored
- MemoryAllocator is now part of Heap - CodeRange is now part of MemoryAllocator BUG=chromium:581076 LOG=N Review URL: https://codereview.chromium.org/1862653002 Cr-Commit-Position: refs/heads/master@{#35294}
-
clemensh authored
This particularly changes the StackTraceFrameIterator such that is not only returs JavaScriptFrames, but also WasmFrames. Because of that, some methods (Summarize, function, receiver) were pulled up to the StandardFrame, with specializations in JavaScriptFrame and WasmFrame. R=jfb@chromium.org, titzer@chromium.org BUG= Review URL: https://codereview.chromium.org/1861283002 Cr-Commit-Position: refs/heads/master@{#35293}
-
jacob.bramley authored
BUG= Review URL: https://codereview.chromium.org/1862993002 Cr-Commit-Position: refs/heads/master@{#35292}
-
verwaest authored
The previous code cache system required stubs to be marked with a StubType, causing them to be inserted either into a fixed array or into a dictionary-mode code cache. This could cause names to be in both cases, and lookup would just find the "fast" one first. Given that we clear out the caches on each GC, the memory overhead shouldn't be too bad. Additionally, the dictionary itself should just stay linear for small arrays; that's faster anyway. This CL additionally deletes some dead IC code. BUG= Review URL: https://codereview.chromium.org/1846963002 Cr-Commit-Position: refs/heads/master@{#35291}
-
clemensh authored
R=ahaas@chromium.org, titzer@chromium.org BUG= Review URL: https://codereview.chromium.org/1861293002 Cr-Commit-Position: refs/heads/master@{#35290}
-
ahaas authored
1) I moved the implementations of the wrapper functions into a new cc file so that I can use these wrapper functions in tests. 2) I made a generic test for all tests in test-run-calls-to-external-references.cc. In the new test we only compare the result of a function call through an external reference with the result of a direct function call. This is sufficient because we only want to test function calls through external references work here. The implementation of these functions are tested somewhere else. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1853123002 Cr-Commit-Position: refs/heads/master@{#35289}
-
hpayer authored
Review URL: https://codereview.chromium.org/1855943002 Cr-Commit-Position: refs/heads/master@{#35288}
-
epertoso authored
Adds a MultiplyStub for the multiplication operator and hooks it with TurboFan and Ignition. Currently, the SMI times SMI case is handled by converting both the operands to double precision floating points, we may consider adding a fast path later. Review URL: https://codereview.chromium.org/1860043002 Cr-Commit-Position: refs/heads/master@{#35287}
-
titzer authored
R=ahaas@chromium.org BUG= Review URL: https://codereview.chromium.org/1860103002 Cr-Commit-Position: refs/heads/master@{#35286}
-
clemensh authored
SingletonFor(type, state) returns NULL and does nothing whenever SingletonFor(type) also return NULL. So checking this beforehand is redundant. This is my first CL, so I also use it to get familiar with the system. R=titzer@chromium.org BUG= Review URL: https://codereview.chromium.org/1862753003 Cr-Commit-Position: refs/heads/master@{#35285}
-
mlippautz authored
BUG= Review URL: https://codereview.chromium.org/1864953003 Cr-Commit-Position: refs/heads/master@{#35284}
-
bmeurer authored
Introduce a ResumeGeneratorTrampoline, which does the actual stack state reconstruction (currently always restores a fullcodegen frame), and introduce appropriate TurboFan builtins for %GeneratorPrototype%.next, %GeneratorPrototype%.return and %GeneratorPrototype%.throw based on this native builtin. Also unify the flooding in case of step-in to always work based on JSFunction and remove the special casing for JSGeneratorObject. R=mstarzinger@chromium.org, neis@chromium.org TBR=rossberg@chromium.org BUG=chromium:513471 LOG=n Review URL: https://codereview.chromium.org/1865833002 Cr-Commit-Position: refs/heads/master@{#35283}
-
ishell authored
BUG=chromium:590071 LOG=N Review URL: https://codereview.chromium.org/1856123005 Cr-Commit-Position: refs/heads/master@{#35282}
-
oth authored
Anotates bytecodes with a description of how each uses the accumulator. Validates annotations and uses of accumulator when generating bytecode handlers. Only prints the accumulator during tracing where used. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1852213002 Cr-Commit-Position: refs/heads/master@{#35281}
-
v8-autoroll authored
Rolling v8/third_party/icu to c291cde264469b20ca969ce8832088acb21e0c48 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1863963002 Cr-Commit-Position: refs/heads/master@{#35280}
-
- 05 Apr, 2016 11 commits
-
-
adamk authored
The Chrome Extensions code that was broken by this change the first time it landed has been amended to deal appropriately with the ES2015 semantics in https://codereview.chromium.org/1864733002/. BUG=v8:4602 LOG=y Review URL: https://codereview.chromium.org/1857313003 Cr-Commit-Position: refs/heads/master@{#35279}
-
hablich authored
BUG=v8:4680 LOG=N TBR=mstarzinger@chromium.org,rmcilroy@chromium.org Review URL: https://codereview.chromium.org/1865683002 Cr-Commit-Position: refs/heads/master@{#35278}
-
caitpotter88 authored
The parser eagerly rewrites destructuring assignments occuring in formal parameter initializers, because not doing so would cause the BindingPattern rewriting to be confused and do the wrong thing. This change prevents this rewriting from descending into the bodies of lazily parsed functions. In general, it's a mistake to descend into the bodies of function literals anyways, since they are rewritten separately on their own time, so there is no distinction made between lazily "throw away" eagerly parsed functions in the temporary parser arena, or "real" eagerly parsed functions that will be compiled. BUG=chromium:594084, v8:811 LOG=N R=adamk@chromium.org, littledan@chromium.org Review URL: https://codereview.chromium.org/1864553002 Cr-Commit-Position: refs/heads/master@{#35277}
-
bjaideep authored
Since interface-descriptors-ppc.h is removed, so remove it from v8.gyp as well. R=machenbach@chromium.org,joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1864593002 Cr-Commit-Position: refs/heads/master@{#35276}
-
kozyatinskiy authored
We decided to remove related devtools experiment. BUG=chromium:526811 LOG=Y R=yangguo@chromium.org Review URL: https://codereview.chromium.org/1833563002 Cr-Commit-Position: refs/heads/master@{#35275}
-
titzer authored
R=ahaas@chromium.org,bradnelson@chromium.org BUG= Review URL: https://codereview.chromium.org/1862633002 Cr-Commit-Position: refs/heads/master@{#35274}
-
titzer authored
R=bradnelson@chromium.org BUG=chromium:599825 LOG=Y Review URL: https://codereview.chromium.org/1858263002 Cr-Commit-Position: refs/heads/master@{#35273}
-
titzer authored
R=ahaas@chromium.org BUG= Review URL: https://codereview.chromium.org/1856413002 Cr-Commit-Position: refs/heads/master@{#35272}
-
littledan authored
Previously, CreateDataProperty would fail a DCHECK when used to create an integer indexed property on a TypedArray. This patch makes it throw a TypeError instead. The issue came up when Array.prototype.concat was repaired to use CreateDataProperty rather than SetElement; concat can be tricked into making a new TypedArray if it is given an Array whose prototype is a TypedArray. This patch prevents the issue. R=adamk LOG=Y BUG=chromium:596394 Review URL: https://codereview.chromium.org/1821723004 Cr-Commit-Position: refs/heads/master@{#35271}
-
yangguo authored
R=neis@chromium.org BUG=v8:4887 LOG=N Review URL: https://codereview.chromium.org/1857263002 Cr-Commit-Position: refs/heads/master@{#35270}
-
cbruni authored
BUG=chromium:599414 LOG=n Review URL: https://codereview.chromium.org/1863553003 Cr-Commit-Position: refs/heads/master@{#35269}
-