- 24 Nov, 2014 9 commits
-
-
Benedikt Meurer authored
TEST=unittests R=jarin@chromium.org Review URL: https://codereview.chromium.org/749233002 Cr-Commit-Position: refs/heads/master@{#25479}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/756553002 Cr-Commit-Position: refs/heads/master@{#25478}
-
Ben L. Titzer authored
R=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/754803002 Cr-Commit-Position: refs/heads/master@{#25477}
-
yangguo authored
R=jkummerow@chromium.org BUG=435825 LOG=N Review URL: https://codereview.chromium.org/753983002 Cr-Commit-Position: refs/heads/master@{#25476}
-
baptiste.afsa authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/730183005 Cr-Commit-Position: refs/heads/master@{#25475}
-
svenpanne authored
Review URL: https://codereview.chromium.org/741643003 Cr-Commit-Position: refs/heads/master@{#25474}
-
dcarney authored
R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/725293003 Cr-Commit-Position: refs/heads/master@{#25473}
-
andrew_low authored
This is needed for 64bit alignment sensitive platforms (PowerPC) Exposed bugs with new GC compare and swap changes updating the field. Example failing test: out/ppc64.debug/cctest test-decls/ExistsInPrototype BUG= Review URL: https://codereview.chromium.org/740443002 Cr-Commit-Position: refs/heads/master@{#25472}
-
dcarney authored
R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/691513005 Cr-Commit-Position: refs/heads/master@{#25471}
-
- 22 Nov, 2014 2 commits
-
-
ishell authored
Revert of Enable inobject double fields unboxing for 64-bit archs. (patchset #3 id:40001 of https://codereview.chromium.org/753503002/) Reason for revert: GCMole and gc-stress issues. Original issue's description: > Enable inobject double fields unboxing for 64-bit archs. TBR=verwaest@chromium.org NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/751863002 Cr-Commit-Position: refs/heads/master@{#25470}
-
ishell authored
Review URL: https://codereview.chromium.org/753503002 Cr-Commit-Position: refs/heads/master@{#25469}
-
- 21 Nov, 2014 18 commits
-
-
dslomov authored
R=rossberg@chromium.org BUG=v8:2198 LOG=N Review URL: https://codereview.chromium.org/745963002 Cr-Commit-Position: refs/heads/master@{#25468}
-
mstarzinger authored
This reverts commit 9da92c1a because of performance regressions. R=danno@chromium.org Review URL: https://codereview.chromium.org/752613002 Cr-Commit-Position: refs/heads/master@{#25467}
-
danno authored
They generally cause regressions on most modern Intel chips. Replace them with addl/subl. Review URL: https://codereview.chromium.org/737153003 Cr-Commit-Position: refs/heads/master@{#25466}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/751543002 Cr-Commit-Position: refs/heads/master@{#25465}
-
yangguo authored
R=vogelheim@chromium.org Review URL: https://codereview.chromium.org/750543002 Cr-Commit-Position: refs/heads/master@{#25464}
-
yangguo authored
R=rossberg@chromium.org BUG=v8:3712 LOG=N Review URL: https://codereview.chromium.org/743843003 Cr-Commit-Position: refs/heads/master@{#25463}
-
jochen authored
A useful value would be 4, so we get 1, 4, 16MB (instead of the default value 2 which leads to 1, 2, 4, 8, 16) BUG=none R=hpayer@chromium.org LOG=n Review URL: https://codereview.chromium.org/753513002 Cr-Commit-Position: refs/heads/master@{#25462}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/748773002 Cr-Commit-Position: refs/heads/master@{#25461}
-
ulan authored
BUG=v8:3716 LOG=N Review URL: https://codereview.chromium.org/746983002 Cr-Commit-Position: refs/heads/master@{#25460}
-
mstarzinger authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/582683002 Cr-Commit-Position: refs/heads/master@{#25459}
-
Yang Guo authored
TBR=ulan@chromium.org Review URL: https://codereview.chromium.org/749963002 Cr-Commit-Position: refs/heads/master@{#25458}
-
yangguo authored
R=ulan@chromium.org BUG=v8:3229 LOG=N Review URL: https://codereview.chromium.org/736003002 Cr-Commit-Position: refs/heads/master@{#25457}
-
Michael Stanton authored
BUG=435477 LOG=N R=jarin@chromium.org Review URL: https://codereview.chromium.org/751513002 Cr-Commit-Position: refs/heads/master@{#25456}
-
Michael Stanton authored
The bug was an error when copying arrays in crankshaft. If it's a holey smi array, the copy must be done as FAST_HOLEY_ELEMENTS to prevent representation changes from being inserted that deopt on encountering the hole. Also, prevent inlining array pop() and shift() if the length is read-only. BUG=435073 LOG=N R=verwaest@chromium.org Review URL: https://codereview.chromium.org/737383002 Cr-Commit-Position: refs/heads/master@{#25455}
-
Baptiste Afsa authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/737733002 Cr-Commit-Position: refs/heads/master@{#25454}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/753483002 Cr-Commit-Position: refs/heads/master@{#25453}
-
chunyang.dai authored
is introduced by https://chromium.googlesource.com/v8/v8/+/aed26c05a50b2a1257ef8accc67143825f2e1f60. ( [turbofan] Clean up and factor out branch generation logic.) BUG= Review URL: https://codereview.chromium.org/748673002 Cr-Commit-Position: refs/heads/master@{#25452}
-
Akos Palfi authored
Port aed26c05a50b2a1257ef8accc67143825f2e1f60 BUG= R=paul.lind@imgtec.com Review URL: https://codereview.chromium.org/742243003 Cr-Commit-Position: refs/heads/master@{#25451}
-
- 20 Nov, 2014 11 commits
-
-
caitpotter88 authored
BUG=v8:3230 LOG=y Review URL: https://codereview.chromium.org/742643003 Cr-Commit-Position: refs/heads/master@{#25450}
-
baixo authored
D8 natives, in particular, will cause Windows static builds to not link due to another definition in the generated file d8-js.cc. BUG=421063 Review URL: https://codereview.chromium.org/738153003 Cr-Commit-Position: refs/heads/master@{#25449}
-
dslomov authored
Per TC39 Nov 2014 decison. R=arv@chromium.org,yangguo@chromium.org LOG=Y Committed: https://chromium.googlesource.com/v8/v8/+/b5379216e23ff0ec734e70361dd07057c2421c96 Review URL: https://codereview.chromium.org/742963002 Cr-Commit-Position: refs/heads/master@{#25448}
-
ulan authored
if there is not enough type-feedback to detect that f is Function.prototype.apply. BUG=v8:3709 LOG=N TEST=mjsunit/regress/regress-3709 Review URL: https://codereview.chromium.org/736043002 Cr-Commit-Position: refs/heads/master@{#25447}
-
titzer authored
R=dcarney@chromium.org BUG= Review URL: https://codereview.chromium.org/745633002 Cr-Commit-Position: refs/heads/master@{#25446}
-
mstarzinger authored
R=danno@chromium.org Review URL: https://codereview.chromium.org/736383002 Cr-Commit-Position: refs/heads/master@{#25445}
-
yangguo authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/737373003 Cr-Commit-Position: refs/heads/master@{#25444}
-
Dan Carney authored
TBR=vogelheim@chromium.org BUG= Review URL: https://codereview.chromium.org/744743002 Cr-Commit-Position: refs/heads/master@{#25443}
-
Ulan Degenbaev authored
BUG= TBR=hpayer@chromium.org Review URL: https://codereview.chromium.org/746443002 Cr-Commit-Position: refs/heads/master@{#25442}
-
ulan authored
If we run out of code range, then GC wouldn't be able to compact code space, because it wouldn't be able to allocate a new page. This can cause code space fragmentation and OOM crashes. BUG=chromium:430118 LOG=Y Review URL: https://codereview.chromium.org/742733002 Cr-Commit-Position: refs/heads/master@{#25441}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/725083004 Cr-Commit-Position: refs/heads/master@{#25440}
-