- 03 Mar, 2015 13 commits
-
-
dslomov authored
R=mvstanton@chromium.org,arv@chromium.org,rossberg@chromium.org BUG=v8:3930 LOG=Y Review URL: https://codereview.chromium.org/975463002 Cr-Commit-Position: refs/heads/master@{#26960}
-
bmeurer authored
Also allow inlining of native functions. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/962963006 Cr-Commit-Position: refs/heads/master@{#26959}
-
jarin authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/968913002 Cr-Commit-Position: refs/heads/master@{#26958}
-
mstarzinger authored
R=jarin@chromium.org Review URL: https://codereview.chromium.org/960273002 Cr-Commit-Position: refs/heads/master@{#26957}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/974783003 Cr-Commit-Position: refs/heads/master@{#26956}
-
sejunho authored
Problem: Excuting with flags as "--prof --logfile-per-isolate --logfile=/path/to/filename" expected file name: /path/to/isolate-<isolate id>-filename current result: isolate-<isolate id>-/path/to/filename This patch makes the file name we expected. Review URL: https://codereview.chromium.org/960813004 Cr-Commit-Position: refs/heads/master@{#26955}
-
rmcilroy authored
Android doesn't have swap space so if the heap goes over the physical memory size the system will just kill us. Applying the Heap::kPointerMultipler to heap size could cause the max heap size to be larger than physical memory. Instead use the defaults which are based on actual physical memory configured by Api::ConfigureDefaults(). BUG=432909 LOG=N Review URL: https://codereview.chromium.org/960213007 Cr-Commit-Position: refs/heads/master@{#26954}
-
loislo authored
TryInline needed position only for the case when we track positions. We can drop the position argument and use the current position from GraphBuilder. The only problem that it doesn't match with the inline point. The reason of that was the fact that builder had moved the position forward by visiting arguments expressions. I fixed this by restoring the current positon in HOptimizedGraphBuilderWithPositions::Visit* BUG=452067 LOG=n Review URL: https://codereview.chromium.org/962593005 Cr-Commit-Position: refs/heads/master@{#26953}
-
dcarney authored
R=svenpanne@chromium.org BUG=v8:3929 LOG=y Review URL: https://codereview.chromium.org/972623003 Cr-Commit-Position: refs/heads/master@{#26952}
-
michael_dawson authored
Contribution of PowerPC port (continuation of 422063005, 817143002, 866843003, and 901083004. This patch updates the ppc directories to make them current with changes in common code, removes the optimization to use the ool constant pool, and excludes tests that don't pass under the ppc simulator given a 240s timeout. Subsequent patches will cover: - remaining optimizations for PPC - remaining AIX changes not resolved by 4.8 compiler (4.8 is only recently available for AIX) - incremental updates required to ppc directories due to platform specific changes made in google repos while we complete the above steps. modified: src/compiler/ppc/code-generator-ppc.cc modified: src/ic/ppc/handler-compiler-ppc.cc modified: src/ppc/assembler-ppc-inl.h modified: src/ppc/assembler-ppc.cc modified: src/ppc/assembler-ppc.h modified: src/ppc/builtins-ppc.cc modified: src/ppc/code-stubs-ppc.cc modified: src/ppc/debug-ppc.cc modified: src/ppc/deoptimizer-ppc.cc modified: src/ppc/frames-ppc.cc modified: src/ppc/frames-ppc.h modified: src/ppc/full-codegen-ppc.cc modified: src/ppc/lithium-codegen-ppc.cc modified: src/ppc/lithium-ppc.cc modified: src/ppc/lithium-ppc.h modified: src/ppc/macro-assembler-ppc.cc modified: src/ppc/macro-assembler-ppc.h modified: test/cctest/cctest.status modified: test/mjsunit/mjsunit.status R=danno@chromium.org, svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/965823002 Cr-Commit-Position: refs/heads/master@{#26951}
-
weiliang.lin authored
Review URL: https://codereview.chromium.org/972053002 Cr-Commit-Position: refs/heads/master@{#26950}
-
bmeurer authored
Review URL: https://codereview.chromium.org/971223002 Cr-Commit-Position: refs/heads/master@{#26949}
-
chunyang.dai authored
port 7ee31a23 (r26941). original commit message: Compute correct contextual load ICs in fullcodegen. BUG= Review URL: https://codereview.chromium.org/974483005 Cr-Commit-Position: refs/heads/master@{#26948}
-
- 02 Mar, 2015 15 commits
-
-
yangguo authored
R=vogelheim@chromium.org Review URL: https://codereview.chromium.org/957703003 Cr-Commit-Position: refs/heads/master@{#26947}
-
Balazs Kilvady authored
Port 7ee31a23 BUG= R=dusan.milosavljevic@imgtec.com Review URL: https://codereview.chromium.org/969803002 Cr-Commit-Position: refs/heads/master@{#26946}
-
Dan Carney authored
r26943 just moved the problem around TBR=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/963023003 Cr-Commit-Position: refs/heads/master@{#26945}
-
Jaroslav Sevcik authored
BUG= R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/972543003 Cr-Commit-Position: refs/heads/master@{#26944}
-
Dan Carney authored
blink is incorrectly calling api functions without a context. we need this to find those places R=svenpanne@chromium.org BUG=v8:3929 LOG=y Review URL: https://codereview.chromium.org/968943002 Cr-Commit-Position: refs/heads/master@{#26943}
-
Benedikt Meurer authored
- (x * (K << L)) & (-1 << L) => x * (K << L) - ((K << L) * x) & (-1 << L) => x * (K << L) R=dcarney@chromium.org Review URL: https://codereview.chromium.org/972653002 Cr-Commit-Position: refs/heads/master@{#26942}
-
Toon Verwaest authored
BUG= R=dcarney@chromium.org Review URL: https://codereview.chromium.org/969733003 Cr-Commit-Position: refs/heads/master@{#26941}
-
Dan Carney authored
BUG=v8:3929 LOG=y R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/971693002 Cr-Commit-Position: refs/heads/master@{#26940}
-
Benedikt Meurer authored
R=rossberg@chromium.org Review URL: https://codereview.chromium.org/968773004 Cr-Commit-Position: refs/heads/master@{#26939}
-
Jaroslav Sevcik authored
Deferred replacement must also replace in the pending node vector. BUG=chromium:463056 LOG=n R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/966423002 Cr-Commit-Position: refs/heads/master@{#26938}
-
Sven Panne authored
BUG=v8:3929 LOG=y R=dcarney@chromium.org Review URL: https://codereview.chromium.org/958053003 Cr-Commit-Position: refs/heads/master@{#26937}
-
Sven Panne authored
BUG=v8:3929 LOG=y R=dcarney@chromium.org Review URL: https://codereview.chromium.org/967243002 Cr-Commit-Position: refs/heads/master@{#26936}
-
Benedikt Meurer authored
On Intel targets, it is cheaper to load the context from the frame instead of loading the context as a constant (which usually involves a PropertyCell because the context is in new space when we compile the function). R=jarin@chromium.org Review URL: https://codereview.chromium.org/970803002 Cr-Commit-Position: refs/heads/master@{#26935}
-
Benedikt Meurer authored
On 64-bit targets, we can skip the write barrier for Store nodes if the input is ChangeInt32ToTagged, because the value being stored is definitely represented as a smi then. R=jarin@chromium.org Review URL: https://codereview.chromium.org/968113002 Cr-Commit-Position: refs/heads/master@{#26934}
-
arv authored
Revert of ES6: Make function name configurable (patchset #10 id:220001 of https://codereview.chromium.org/960343002/) Reason for revert: Breaks Chrome browser test that checks Object.name [16509:16509:0228/030150:INFO:CONSOLE(43)] "Uncaught Error: Clobbered Object.name getter", source: http://www.chromium.org:33611/assertions.js (43) http://build.chromium.org/p/client.v8/builders/Linux%20Tests%20%28dbg%29%281%29/builds/2328/steps/browser_tests/logs/stdio Original issue's description: > ES6: Make function name configurable > > This is partially based on r21609 but that CL was incomplete. > > Function name is still non writable so one has to use defineProperty > to change the actual value. > > BUG=v8:3333 > LOG=N > R=adamk, mstarzinger@chromium.org > > Committed: https://crrev.com/f7790f7670c8d859455a98fcb90ff1b66af1eca7 > Cr-Commit-Position: refs/heads/master@{#26924} TBR=adamk@chromium.org,mstarzinger@chromium.org,verwaest@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3333 Review URL: https://codereview.chromium.org/969683002 Cr-Commit-Position: refs/heads/master@{#26933}
-
- 28 Feb, 2015 2 commits
-
-
cdai2 authored
port 290ee378 (r26931). original commit message: UG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/963393002 Cr-Commit-Position: refs/heads/master@{#26932}
-
dslomov authored
R=rossberg@chromium.org,arv@chromium.org BUG=v8:3930 LOG=Y Committed: https://crrev.com/87f3e08e72510ee5544e82bb7ad39b2b5f001ad3 Cr-Commit-Position: refs/heads/master@{#26925} Review URL: https://codereview.chromium.org/962263002 Cr-Commit-Position: refs/heads/master@{#26931}
-
- 27 Feb, 2015 10 commits
-
-
dslomov authored
Revert of Disallow subclassing Arrays. (patchset #3 id:40001 of https://codereview.chromium.org/962263002/) Reason for revert: Fails on nosnap build Original issue's description: > Disallow subclassing Arrays. > > R=rossberg@chromium.org,arv@chromium.org > BUG=v8:3930 > LOG=Y > > Committed: https://crrev.com/87f3e08e72510ee5544e82bb7ad39b2b5f001ad3 > Cr-Commit-Position: refs/heads/master@{#26925} TBR=arv@chromium.org,rossberg@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3930 Review URL: https://codereview.chromium.org/965053002 Cr-Commit-Position: refs/heads/master@{#26930}
-
dslomov authored
Revert of Regression test for v8:3930. (patchset #1 id:1 of https://codereview.chromium.org/961353002/) Reason for revert: Fails on nosnap builds Original issue's description: > Regression test for v8:3930. > > R=arv@chromium.org,rossberg@chromium.org > BUG=v8:3930 > LOG=N > > Committed: https://crrev.com/48fb3e83c5882e9818bc1e0a035864b465602aca > Cr-Commit-Position: refs/heads/master@{#26926} TBR=arv@chromium.org,rossberg@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3930 Review URL: https://codereview.chromium.org/965043002 Cr-Commit-Position: refs/heads/master@{#26929}
-
machenbach authored
The auto-push script is only used in an automated fashion on bots. It doesn't need to check for a clean git environment as it has a special workdir checkout. If the release creation fails for whatever reason (e.g. a master restart happens in the middle), the workdir checkout might be left dirty. Any new attempt of the auto pusher then bails out. After this change it will call the create_release script in any case which tidies up the workspace on startup. TBR=tandrii@chromium.org NOTRY=true TEST=./script_test.py Review URL: https://codereview.chromium.org/960773007 Cr-Commit-Position: refs/heads/master@{#26928}
-
arv authored
The test didn't call the test function. BUG=v8:3932 LOG=N TBR=ulan@chromium.org Review URL: https://codereview.chromium.org/964993002 Cr-Commit-Position: refs/heads/master@{#26927}
-
dslomov authored
R=arv@chromium.org,rossberg@chromium.org BUG=v8:3930 LOG=N Review URL: https://codereview.chromium.org/961353002 Cr-Commit-Position: refs/heads/master@{#26926}
-
dslomov authored
R=rossberg@chromium.org,arv@chromium.org BUG=v8:3930 LOG=Y Review URL: https://codereview.chromium.org/962263002 Cr-Commit-Position: refs/heads/master@{#26925}
-
arv authored
This is partially based on r21609 but that CL was incomplete. Function name is still non writable so one has to use defineProperty to change the actual value. BUG=v8:3333 LOG=N R=adamk, mstarzinger@chromium.org Review URL: https://codereview.chromium.org/960343002 Cr-Commit-Position: refs/heads/master@{#26924}
-
ricow authored
R=yangguo@chromium.org BUG= Review URL: https://codereview.chromium.org/961263002 Cr-Commit-Position: refs/heads/master@{#26923}
-
arv authored
BUG=v8:3754 LOG=N R=dslomov@chromium.org, rossberg@chromium.org Review URL: https://codereview.chromium.org/959313002 Cr-Commit-Position: refs/heads/master@{#26922}
-
adamk authored
BUG=v8:1569 LOG=n Review URL: https://codereview.chromium.org/958213006 Cr-Commit-Position: refs/heads/master@{#26921}
-