- 30 Oct, 2014 11 commits
-
-
sigurds@chromium.org authored
R=rodolph.perfetta@gmail.com, ulan@chromium.org, bmeurer@chromium.org, rodolph.perfetta@arm.com Review URL: https://codereview.chromium.org/682643002 Cr-Commit-Position: refs/heads/master@{#25013} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25013 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/686053003 Cr-Commit-Position: refs/heads/master@{#25011} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25011 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/683933004 Cr-Commit-Position: refs/heads/master@{#25010} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25010 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=bmeurer@chromium.org,mstarzinger@chromium.org Review URL: https://codereview.chromium.org/692823002 Cr-Commit-Position: refs/heads/master@{#25009} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25009 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
T=jarin@chromium.org BUG= R=jarin@chromium.org Review URL: https://codereview.chromium.org/688633002 Cr-Commit-Position: refs/heads/master@{#25008} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25008 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=bmeurer@chromium.org BUG=chromium:428315 LOG=n Review URL: https://codereview.chromium.org/693473002 Cr-Commit-Position: refs/heads/master@{#25007} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25007 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
This bug (mismatch between new[] and free) was found by running VC++'s /analyze on all of Chrome. BUG=chromium:427616 LOG=N R=yangguo@chromium.org Review URL: https://codereview.chromium.org/686193004 Patch from Bruce Dawson <brucedawson@chromium.org>. Cr-Commit-Position: refs/heads/master@{#25003} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25003 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=jarin@chromium.org BUG=v8:3660 LOG=N Review URL: https://codereview.chromium.org/665833003 Cr-Commit-Position: refs/heads/master@{#25002} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25002 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
The HeapIterator implies DisallowHeapAllocation, but Script::GetWrapper may allocate. LOG=N R=jkummerow@chromium.org BUG=chromium:410033 Review URL: https://codereview.chromium.org/680283002 Cr-Commit-Position: refs/heads/master@{#25001} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25001 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r24987 original commit message: EmitCreateIteratorResult loads map from function's context Caching or serialization can cause full-codegen output to be shared between contexts. CreateIteratorResult, however, was doing the wrong thing by creating results with the map that was current when the code was generated. Instead, we should chase pointers to load the right map from the function's context. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/674073004 Patch from Chunyang Dai <chunyang.dai@intel.com>. Cr-Commit-Position: refs/heads/master@{#25000} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@25000 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r24976. original commit message: Classes: Add super support in methods and accessors This is done by installing the [[HomeObject]] on the method and the accessor functions. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/687273005 Patch from Chunyang Dai <chunyang.dai@intel.com>. Cr-Commit-Position: refs/heads/master@{#24999} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24999 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 29 Oct, 2014 29 commits
-
-
rmcilroy@chromium.org authored
R=rmcilroy@chromium.org Review URL: https://codereview.chromium.org/684263002 Patch from André Baixo <baixo@google.com>. Cr-Commit-Position: refs/heads/master@{#24998} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24998 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/684193002 Cr-Commit-Position: refs/heads/master@{#24997} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24997 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/687103004 Cr-Commit-Position: refs/heads/master@{#24996} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24996 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
titzer@chromium.org authored
R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/686213002 Cr-Commit-Position: refs/heads/master@{#24995} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24995 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Namely, -Winconsistent-missing-override. No behavior change. BUG=v8:3658 LOG=N R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/688533002 Cr-Commit-Position: refs/heads/master@{#24994} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24994 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
balazs.kilvady@imgtec.com authored
Port r24987 (cfc4713) Original commit message: Caching or serialization can cause full-codegen output to be shared between contexts. CreateIteratorResult, however, was doing the wrong thing by creating results with the map that was current when the code was generated. Instead, we should chase pointers to load the right map from the function's context. BUG=v8:3656 LOG=N R=paul.lind@imgtec.com Review URL: https://codereview.chromium.org/691563002 Cr-Commit-Position: refs/heads/master@{#24993} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24993 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/639763004 Cr-Commit-Position: refs/heads/master@{#24992} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24992 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=titzer@chromium.org, jarin@chromium.org Review URL: https://codereview.chromium.org/687133003 Cr-Commit-Position: refs/heads/master@{#24991} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24991 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
The biggest change is the removal of the map wrapper objects: we now operate directly on the observation weak map, since there are already Get/GetOrCreate/Set functions for each info map. Various other small cleanups as well, including the deletion of unnecessary forwarding functions and making use of standard macros. This is a reland of r24972, retaining GetObservationStateJS() to keep snapshotting working properly. R=rossberg@chromium.org Review URL: https://codereview.chromium.org/663253006 Cr-Commit-Position: refs/heads/master@{#24990} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24990 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
baptiste.afsa@arm.com authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/687193002 Cr-Commit-Position: refs/heads/master@{#24989} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24989 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dusan.milosavljevic@imgtec.com authored
TEST=/benchmarks/octane/crypto BUG= R=paul.lind@imgtec.com Review URL: https://codereview.chromium.org/688693002 Cr-Commit-Position: refs/heads/master@{#24988} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24988 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
wingo@igalia.com authored
Caching or serialization can cause full-codegen output to be shared between contexts. CreateIteratorResult, however, was doing the wrong thing by creating results with the map that was current when the code was generated. Instead, we should chase pointers to load the right map from the function's context. R=verwaest@chromium.org BUG=v8:3656 LOG=N Review URL: https://codereview.chromium.org/686063002 Cr-Commit-Position: refs/heads/master@{#24987} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24987 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
titzer@chromium.org authored
The justification for doing this is to reduce the size of the graph and therefore speedup later phases of compilation. The control reducer also obviates the need to run the PhiReducer, since it subsumes it. R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/681263004 Cr-Commit-Position: refs/heads/master@{#24986} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24986 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/652193007 Cr-Commit-Position: refs/heads/master@{#24985} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24985 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=tandrii@chromium.org Review URL: https://codereview.chromium.org/688013002 Cr-Commit-Position: refs/heads/master@{#24984} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24984 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
titzer@chromium.org authored
This is a first step to refactoring OperatorProperties out of existence. The next step is to inline OperatorProperties::GetXXXCount into the callers. R=rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/680313003 Cr-Commit-Position: refs/heads/master@{#24983} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24983 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
BUG=410721 LOG=n TEST=script_test.py R=tandrii@chromium.org TBR=tandrii@chromium.org Review URL: https://codereview.chromium.org/670263004 Cr-Commit-Position: refs/heads/master@{#24981} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24981 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TEST=mjsunit,unittests R=dcarney@chromium.org Review URL: https://codereview.chromium.org/691513002 Cr-Commit-Position: refs/heads/master@{#24980} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24980 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
balazs.kilvady@imgtec.com authored
Port r24976 (5cb743f) Original commit message: This is done by installing the [[HomeObject]] on the method and the accessor functions. BUG=v8:3330 LOG=Y R=dusan.milosavljevic@imgtec.com Review URL: https://codereview.chromium.org/691503002 Cr-Commit-Position: refs/heads/master@{#24979} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24979 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
BUG= R=jarin@chromium.org Review URL: https://codereview.chromium.org/671043004 Cr-Commit-Position: refs/heads/master@{#24978} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24978 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
It broke the context snapshot by trying to get ahold of the per-isolate observation_state object too early. This reverts commit a137cb74. TBR=yangguo@chromium.org Review URL: https://codereview.chromium.org/692473002 Cr-Commit-Position: refs/heads/master@{#24977} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24977 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
arv@chromium.org authored
This is done by installing the [[HomeObject]] on the method and the accessor functions. BUG=v8:3330 LOG=Y R=dslomov@chromium.org Review URL: https://codereview.chromium.org/683893002 Cr-Commit-Position: refs/heads/master@{#24976} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24976 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dslomov@chromium.org authored
R=rossberg@chromium.org Review URL: https://codereview.chromium.org/650663003 Cr-Commit-Position: refs/heads/master@{#24975} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24975 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
baptiste.afsa@arm.com authored
Also add corresponding unit tests. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/684813004 Cr-Commit-Position: refs/heads/master@{#24974} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24974 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
BUG= R=dslomov@chromium.org Review URL: https://codereview.chromium.org/684103002 Cr-Commit-Position: refs/heads/master@{#24973} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24973 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
The biggest change is the removal of the map wrapper objects: we now operate directly on the observation weak map, since there are already Get/GetOrCreate/Set functions for each info map. Various other small cleanups as well, including the deletion of unnecessary forwarding functions and making use of standard macros. R=arv@chromium.org, rossberg@chromium.org Review URL: https://codereview.chromium.org/686773002 Cr-Commit-Position: refs/heads/master@{#24972} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24972 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
Scenario: On reload, Devtools restores previously set break points. At this point, since Devtools is already opened, all code is compiled with debug break slots. No break points exist yet, so we would lazily compile inner functions, even ones that cannot be compiled lazily without a context. So when we use Debug::FindSharedFunctionInfoInScript to find the break positions, those lazily compiled functions are skipped. By eagerly compiling when debug is active, we make sure that whenever Devtools is open, functions that cannot be compiled lazily without a context are always compiled with its outer function. R=ulan@chromium.org BUG=chromium:424142 LOG=N Review URL: https://codereview.chromium.org/683413003 Cr-Commit-Position: refs/heads/master@{#24971} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24971 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=chromium:424142 LOG=N R=jarin@chromium.org Review URL: https://codereview.chromium.org/692453002 Cr-Commit-Position: refs/heads/master@{#24970} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24970 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
The big change here is to split out each key type into its own benchmark suite, since optimizations for different key types are likely to be disjoint. ForEach tests have also been split into separate "Iteration" suites, again with the thought that iteration performance is likely separable from key type. As part of adding the new tests, rejiggered the existing tests: - Map.set and Set.add (along with their Weak variants) no longer include construction costs in their scores - Moved key logic into the shared common.js R=arv@chromium.org, machenbach@chromium.org Review URL: https://codereview.chromium.org/685753004 Cr-Commit-Position: refs/heads/master@{#24969} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24969 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-