- 26 Oct, 2014 2 commits
-
-
jarin@chromium.org authored
TBR=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/670023003 Cr-Commit-Position: refs/heads/master@{#24887} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24887 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/639883002 Cr-Commit-Position: refs/heads/master@{#24886} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24886 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 Oct, 2014 28 commits
-
-
dslomov@chromium.org authored
R=dslomov@chromium.org Review URL: https://codereview.chromium.org/664333003 Patch from Caitlin Potter <caitpotter88@gmail.com>. Cr-Commit-Position: refs/heads/master@{#24885} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24885 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
SparseSlice does not need this (non-optimal) reordering since its callers guarantee that [[Get]] has no side effects on the passed-in array. BUG=v8:3643 LOG=n R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/674003002 Cr-Commit-Position: refs/heads/master@{#24884} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24884 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
This avoids using the Sparse methods on objects with non-enumerable elements, which can cause the 'enumerable: false' bit to get lost in the operation. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/672323003 Cr-Commit-Position: refs/heads/master@{#24883} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24883 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
baptiste.afsa@arm.com authored
R=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/668633003 Cr-Commit-Position: refs/heads/master@{#24882} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24882 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/669383002 Cr-Commit-Position: refs/heads/master@{#24881} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24881 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dslomov@chromium.org authored
LOG=Y BUG=v8:3606 R=arv@chromium.org, marja@chromium.org Review URL: https://codereview.chromium.org/615813004 Patch from Caitlin Potter <caitpotter88@gmail.com>. Cr-Commit-Position: refs/heads/master@{#24880} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24880 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
Cr-Commit-Position: refs/heads/master@{#24878} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24878 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
titzer@chromium.org authored
R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/677683002 Cr-Commit-Position: refs/heads/master@{#24877} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24877 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=jarin@chromium.org TEST=cctest/test-schedule/TestScheduleInsertBranch Review URL: https://codereview.chromium.org/675983002 Cr-Commit-Position: refs/heads/master@{#24876} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24876 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
Now that C++11 is allowed, we can use arraysize instead of ARRAYSIZE_UNSAFE, except in NaCl builds. So let's move this macro inside an NaCl ifdef. BUG=chromium:405225 LOG=y R=jochen@chromium.org Review URL: https://codereview.chromium.org/668303002 Patch from Mostyn Bramley-Moore <mostynb@opera.com>. Cr-Commit-Position: refs/heads/master@{#24875} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24875 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sigurds@chromium.org authored
These operators are not supported by any backends yet, and a backend is free to not support them. R=bmeurer@chromium.org TEST=unittest/machine-operator Review URL: https://codereview.chromium.org/668173002 Cr-Commit-Position: refs/heads/master@{#24874} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24874 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
marja@chromium.org authored
They were not, so we were creating several instances of them, one for each time they occurred in the source code. It's not known to have caused efficiency problems though, so this is a sanity fix more than an efficiency fix. Note that numbers are still not unique. BUG= R=rossberg@chromium.org Review URL: https://codereview.chromium.org/657893003 Cr-Commit-Position: refs/heads/master@{#24873} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24873 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=vogelheim@chromium.org Review URL: https://codereview.chromium.org/661343003 Cr-Commit-Position: refs/heads/master@{#24872} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24872 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
- consider the source string as a special sort of back reference. - use repeat op code for more root members. R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/674883002 Cr-Commit-Position: refs/heads/master@{#24871} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24871 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
This is to cope with the recent division of the TypeFeedbackVector into Slots and ICSlots. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/673203002 Cr-Commit-Position: refs/heads/master@{#24870} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24870 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
Private symbols we create in the heap don't have names, but we can resolve them to a constant string. This gives handy debugger output like: (gdb) job 0x2020c67d 0x2020c67d: [Symbol] - hash: 547385396 - name: 0x20208091 <undefined> (uninitialized_symbol) - private: 1 - own: 1 $7 = void (gdb) or with ShortPrint() in an array: ... [5]: 0x2020c67d <Symbol: 547385396 (uninitialized_symbol)> ... Printing help for internal symbols R=yangguo@chromium.org Review URL: https://codereview.chromium.org/677633003 Cr-Commit-Position: refs/heads/master@{#24869} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24869 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/663893004 Cr-Commit-Position: refs/heads/master@{#24868} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24868 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/650633003 Cr-Commit-Position: refs/heads/master@{#24867} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24867 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
Simple refactoring that is useful for upcoming --vector-ic changes. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/673933005 Cr-Commit-Position: refs/heads/master@{#24866} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24866 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
Cr-Commit-Position: refs/heads/master@{#24865} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24865 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
Cr-Commit-Position: refs/heads/master@{#24864} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24864 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=agable@chromium.org Review URL: https://codereview.chromium.org/672293006 Cr-Commit-Position: refs/heads/master@{#24863} git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24863 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TEST=mjsunit/compiler,unittests R=titzer@chromium.org Review URL: https://codereview.chromium.org/671393002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24862 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/663453005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24861 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TBR=jarin@chromium.org Review URL: https://codereview.chromium.org/673873004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24860 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r24825. original commit message: Classes: implement 'new super'. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/663233003 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24859 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
And also fix a OOB read in SerializeExternalString. R=vogelheim@chromium.org Review URL: https://codereview.chromium.org/671633004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24858 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
Each time a transition is added to a hidden class, the whole transitions array must be copied, which causes poor performance in some circumstances. This change limits the maximum size of the transition array, avoiding this behavior in the pathological case. For example, this improves the performance of the EtchMark benchmark by nearly 60%. BUG=v8:3616 LOG= R=verwaest@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/635883003 Patch from Kevin M. McCormick <mckev@amazon.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24857 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Oct, 2014 10 commits
-
-
adamk@chromium.org authored
BUG=chromium:423633 LOG=n R=verwaest@chromium.org Review URL: https://codereview.chromium.org/673893002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24856 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
Added a new %HasComplexElements runtime function (meaning elements that are non-writable, non-configurable, or have getters and setters) and use it in UseSparseVariant to filter out cases where the sparse optimizations can cause V8 to fall out of spec compliance. Renamed SmartMove/SmartSlice to SparseMove/SparseSlice and guarded them with the new and improved UseSparseVariant. These two changes combine let us pass nearly every test in bug-2615.js, as well as fixing reverse and join on sparse arrays. Note that there are various test changes in this patch that correct existing tests to match the correct-by-spec behavior. This patch depends on https://codereview.chromium.org/666883009, which better-aligns the behavior of SmartMove with SimpleMove. BUG=v8:2615,v8:3612,v8:3621 LOG=y R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/656423004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24855 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
adamk@chromium.org authored
The previous behavior, which caused Array.prototype.unshift() (with no args) to have side-effects, no longer matches the spec (ES6 changed the no-arg behavior in April 2014). The new SmartMove behavior is also compatible with current versions of Firefox. This is a baby step towards getting rid of SmartMove; it isolates the test change in this patch, instead of lumping it in confusingly with all the other test updates necessary for moving away from SmartMove. R=dslomov@chromium.org Review URL: https://codereview.chromium.org/666883009 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24854 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=jarin@chromium.org Review URL: https://codereview.chromium.org/673753003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24853 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=jarin@chromium.org Review URL: https://codereview.chromium.org/667553003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24852 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ulan@chromium.org authored
BUG=chromium:424423 LOG=Y R=jochen@chromium.org Review URL: https://codereview.chromium.org/662543008 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24851 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
TBR=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/673793002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24850 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ishell@chromium.org authored
BUG=chromium:423687 LOG=N R=verwaest@chromium.org Review URL: https://codereview.chromium.org/669403002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24849 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
This is based on Georg's work on typing arithmetic operations (https://codereview.chromium.org/658743002/). Instead of weakening to bitset types, we weaken to the closest 2^n limit if we see that we are re-typing a node with a range type (which means that the node can be part of a cycle, so we might need to speed up the fixpoint there). BUG= R=rossberg@chromium.org Review URL: https://codereview.chromium.org/636283009 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24848 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=bmeurer@chromium.org Review URL: https://codereview.chromium.org/667213006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24847 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-