- 14 Apr, 2015 20 commits
-
-
jarin authored
BUG=chromium:470390 R=hpayer@chromium.org LOG=n Review URL: https://codereview.chromium.org/1066653003 Cr-Commit-Position: refs/heads/master@{#27819}
-
bmeurer authored
It's cheaper to materialize heap constants by loading from the roots array instead of embedding the constant into the instruction stream, at least on x64, arm and arm64. Drive-by-fix: Also cleanup the materialize constant from frame optimization. R=dcarney@chromium.org Review URL: https://codereview.chromium.org/1088913002 Cr-Commit-Position: refs/heads/master@{#27818}
-
mvstanton authored
BUG=476488 LOG=N R=jarin@chromium.org Review URL: https://codereview.chromium.org/1080253003 Cr-Commit-Position: refs/heads/master@{#27817}
-
jochen authored
Revert of Reland "Remove support for thread-based recompilation" (patchset #1 id:1 of https://codereview.chromium.org/1059853004/) Reason for revert: still times out Original issue's description: > Reland "Remove support for thread-based recompilation" > > Original issue's description: > > Remove support for thread-based recompilation > > > > BUG=v8:3608 > > R=yangguo@chromium.org > > LOG=y > > > > Committed: https://crrev.com/ed5db223a19dfe126af012e894582251aa3635d7 > > Cr-Commit-Position: refs/heads/master@{#27619} > > BUG=v8:3608 > R=yangguo@chromium.org > LOG=y > > Committed: https://crrev.com/f1ceccb8b8b352a91e6366e3e3103f1db0df6afb > Cr-Commit-Position: refs/heads/master@{#27813} TBR=yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3608 Review URL: https://codereview.chromium.org/1082183003 Cr-Commit-Position: refs/heads/master@{#27816}
-
yangguo authored
R=svenpanne@chromium.org BUG=v8:4025 LOG=N Review URL: https://codereview.chromium.org/1084853002 Cr-Commit-Position: refs/heads/master@{#27815}
-
jochen authored
> BUG=468601 > LOG=n > > Review URL: https://codereview.chromium.org/1016353002 > > Cr-Commit-Position: refs/heads/master@{#27317} R=hpayer@chromium.org BUG=v8:3996,chromium:468601 LOG=n Review URL: https://codereview.chromium.org/1080303002 Cr-Commit-Position: refs/heads/master@{#27814}
-
jochen authored
Original issue's description: > Remove support for thread-based recompilation > > BUG=v8:3608 > R=yangguo@chromium.org > LOG=y > > Committed: https://crrev.com/ed5db223a19dfe126af012e894582251aa3635d7 > Cr-Commit-Position: refs/heads/master@{#27619} BUG=v8:3608 R=yangguo@chromium.org LOG=y Review URL: https://codereview.chromium.org/1059853004 Cr-Commit-Position: refs/heads/master@{#27813}
-
dslomov authored
R=arv@chromium.org Review URL: https://codereview.chromium.org/1052963002 Cr-Commit-Position: refs/heads/master@{#27812}
-
jochen authored
If a major gc happens between allocation and initialization of the buffer, it might be already in old space. Since we need the list of buffers to be sorted from new to old, we keep track of the last buffer and put old buffers to the end BUG=chromium:476032 R=hpayer@chromium.org,dslomov@chromium.org LOG=n Review URL: https://codereview.chromium.org/1079923003 Cr-Commit-Position: refs/heads/master@{#27811}
-
yangguo authored
Revert of Revert of Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1083013002/) Reason for revert: Seems to still break those tests. Original issue's description: > Revert of Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1086683002/) > > Reason for revert: > I don't think this is the cause. > > Original issue's description: > > Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1082703003/) > > > > Reason for revert: > > [Sheriff] Flaky nosnap failures: > > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20nosnap%20-%20debug%20-%201/builds/1720 > > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3312 > > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3313 > > > > Original issue's description: > > > Wrap typed array implementations in functions. > > > > > > R=mvstanton@chromium.org > > > > > > Committed: https://crrev.com/6fc394a15614b74776f9bbeeb0486f430bdc8597 > > > Cr-Commit-Position: refs/heads/master@{#27784} > > > > TBR=mvstanton@chromium.org,yangguo@chromium.org > > NOPRESUBMIT=true > > NOTREECHECKS=true > > NOTRY=true > > > > Committed: https://crrev.com/8e3fa7adf20f4f9c9125076a878d601eee7c9f35 > > Cr-Commit-Position: refs/heads/master@{#27789} > > TBR=mvstanton@chromium.org,machenbach@chromium.org > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > > Committed: https://crrev.com/d7fe3b83f5dfa997f0c8a29436a22b999dc49a76 > Cr-Commit-Position: refs/heads/master@{#27803} TBR=mvstanton@chromium.org,machenbach@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1088863002 Cr-Commit-Position: refs/heads/master@{#27810}
-
dslomov authored
Instead of modifying a context chain and then modifying it back, causing potential mismatches, we clone the inner context chain and evaluate the expression in this cloned context. We then copy all local variable values back if needed. R=yangguo@chromium.org,yurys@chromium.org Review URL: https://codereview.chromium.org/1088503003 Cr-Commit-Position: refs/heads/master@{#27809}
-
dcarney authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1060373006 Cr-Commit-Position: refs/heads/master@{#27808}
-
chunyang.dai authored
The overwrite-builtins test cases will throw one expected exception and the exception message should include the source position in the JS file. But crankshaft compiler does not generate the source position for it when creating the flow graph by default. The source position information is always zero. So it failed when comparing with the reference file. If we use crankshaft compiler on IA32 platform to run this test case, it has the same failure. BUG= Review URL: https://codereview.chromium.org/1086503002 Cr-Commit-Position: refs/heads/master@{#27807}
-
smcgruer authored
As uClibc defines __GLIBC__ in an attempt to look like glibc, V8_LIBC_GLIBC was true for uClibc as well. Checking for uClibc before glibc fixes this and restores the correct behavior. BUG= Review URL: https://codereview.chromium.org/1066573005 Cr-Commit-Position: refs/heads/master@{#27806}
-
dcarney authored
BUG=427616 LOG=N Review URL: https://codereview.chromium.org/1087533002 Cr-Commit-Position: refs/heads/master@{#27805}
-
hpayer authored
This CL will be reverted after getting sufficient data. BUG= Review URL: https://codereview.chromium.org/1060533003 Cr-Commit-Position: refs/heads/master@{#27804}
-
yangguo authored
Revert of Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1086683002/) Reason for revert: I don't think this is the cause. Original issue's description: > Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1082703003/) > > Reason for revert: > [Sheriff] Flaky nosnap failures: > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20nosnap%20-%20debug%20-%201/builds/1720 > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3312 > http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3313 > > Original issue's description: > > Wrap typed array implementations in functions. > > > > R=mvstanton@chromium.org > > > > Committed: https://crrev.com/6fc394a15614b74776f9bbeeb0486f430bdc8597 > > Cr-Commit-Position: refs/heads/master@{#27784} > > TBR=mvstanton@chromium.org,yangguo@chromium.org > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > > Committed: https://crrev.com/8e3fa7adf20f4f9c9125076a878d601eee7c9f35 > Cr-Commit-Position: refs/heads/master@{#27789} TBR=mvstanton@chromium.org,machenbach@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1083013002 Cr-Commit-Position: refs/heads/master@{#27803}
-
chunyang.dai authored
port e0844a24 (r27793). original commit message: These options were added for a hydrogen code stub version of the VectorIC dispatcher, which was discontinued. BUG= Review URL: https://codereview.chromium.org/1087573003 Cr-Commit-Position: refs/heads/master@{#27802}
-
chunyang.dai authored
The assembler code generated by the DeoptimizeIf(...) function under X87 is larger and the distance between the link point and the bind point which has two DeoptimizeIf() is larger then near link distance (127) for labels. BUG= Review URL: https://codereview.chromium.org/1065893003 Cr-Commit-Position: refs/heads/master@{#27801}
-
paul.lind authored
Port 5277c410. BUG= Review URL: https://codereview.chromium.org/1084723003 Cr-Commit-Position: refs/heads/master@{#27800}
-
- 13 Apr, 2015 20 commits
-
-
adamk authored
This avoids both a mysterious boolean argument ("insert") and lets non-mutating lookups skip passing an allocator (in one such case, we were passing a scary-looking ZoneAllocationPolicy(NULL)!). Review URL: https://codereview.chromium.org/1074943002 Cr-Commit-Position: refs/heads/master@{#27799}
-
arv authored
{Map, Set, WeakMap, WeakSet}.length should be 0. BUG=v8:4021 LOG=N R=adamk@chromium.org Review URL: https://codereview.chromium.org/1073233002 Cr-Commit-Position: refs/heads/master@{#27798}
-
mbrandy authored
Port e0844a24 Original commit message: These options were added for a hydrogen code stub version of the VectorIC dispatcher, which was discontinued. R=mvstanton@chromium.org, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1088573002 Cr-Commit-Position: refs/heads/master@{#27797}
-
conradw authored
Does not entirely disallow the use of 'eval' as an identifier in strong mode, as originally proposed. BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1059273004 Cr-Commit-Position: refs/heads/master@{#27796}
-
verwaest authored
BUG=chromium:388665 LOG=n Review URL: https://codereview.chromium.org/1087463003 Cr-Commit-Position: refs/heads/master@{#27795}
-
mbrandy authored
Use fsub rather than fadd to avoid stripping the sign from minus zero. Fixes mjsunit/result-table-min and mjsunit/result-table-max test failures. R=michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1084583003 Cr-Commit-Position: refs/heads/master@{#27794}
-
mvstanton authored
These options were added for a hydrogen code stub version of the VectorIC dispatcher, which was discontinued. R=verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/1081883002 Cr-Commit-Position: refs/heads/master@{#27793}
-
titzer authored
R=mstarzinger@chromium.org,verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/1077343002 Cr-Commit-Position: refs/heads/master@{#27792}
-
arv authored
This reverts commit e965a1f8. The reason is that it breaks jsfiddle.com BUG=476437, v8:4001 LOG=N R=rossberg@chromium.org Review URL: https://codereview.chromium.org/1086673002 Cr-Commit-Position: refs/heads/master@{#27791}
-
machenbach authored
Revert of VectorICs: megamorphic keyed loads in crankshaft don't need a vector. (patchset #3 id:40001 of https://codereview.chromium.org/1067573003/) Reason for revert: [Sheriff] Speculative revert for windows failure... will reland if it doesn't help: http://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20debug%20-%202/builds/2891 Original issue's description: > VectorICs: megamorphic keyed loads in crankshaft don't need a vector. > > They are content with a dummy vector, as MISSES won't result in > changing the real vector/slot at all. > > BUG= > > Committed: https://crrev.com/c8e4d57d3b3036a05902f5b916cb5d853a57393c > Cr-Commit-Position: refs/heads/master@{#27788} TBR=dcarney@chromium.org,mvstanton@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1060263003 Cr-Commit-Position: refs/heads/master@{#27790}
-
machenbach authored
Revert of Wrap typed array implementations in functions. (patchset #1 id:1 of https://codereview.chromium.org/1082703003/) Reason for revert: [Sheriff] Flaky nosnap failures: http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20nosnap%20-%20debug%20-%201/builds/1720 http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3312 http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3313 Original issue's description: > Wrap typed array implementations in functions. > > R=mvstanton@chromium.org > > Committed: https://crrev.com/6fc394a15614b74776f9bbeeb0486f430bdc8597 > Cr-Commit-Position: refs/heads/master@{#27784} TBR=mvstanton@chromium.org,yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1086683002 Cr-Commit-Position: refs/heads/master@{#27789}
-
mvstanton authored
They are content with a dummy vector, as MISSES won't result in changing the real vector/slot at all. BUG= Review URL: https://codereview.chromium.org/1067573003 Cr-Commit-Position: refs/heads/master@{#27788}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/1085623002 Cr-Commit-Position: refs/heads/master@{#27787}
-
dcarney authored
R=jochen@chromium.org, hpayer@chromium.org, erikcorry@chromium.org BUG= Review URL: https://codereview.chromium.org/1064713005 Cr-Commit-Position: refs/heads/master@{#27786}
-
dcarney authored
rename to ReferenceMap use ZoneVector for storage drop dead code BUG= Review URL: https://codereview.chromium.org/1081053002 Cr-Commit-Position: refs/heads/master@{#27785}
-
yangguo authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1082703003 Cr-Commit-Position: refs/heads/master@{#27784}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1081803002 Cr-Commit-Position: refs/heads/master@{#27783}
-
jochen authored
This allows the embedder to decide whether it's worthwhile to copy the contents to avoid materializing a buffer. BUG=v8:3996 R=dslomov@chromium.org,kbr@chromium.org LOG=y Review URL: https://codereview.chromium.org/1084513002 Cr-Commit-Position: refs/heads/master@{#27782}
-
vegorov authored
Deoptimization infrastructure already handles it correctly. This change fixes repetitive deoptimizations in the code like this: var u32 = new Uint32Array(1); u32[0] = -1; function tr(x) { return x|0; } function ld() { return tr(u32[0]); } while (true) ld(); Currently inlined tr will contain HArgumentsObject that is considered uint32-unsafe use and prevents u32[0] from becoming uint32 load - instead a speculative int32 load is generated which just deopts. BUG= Review URL: https://codereview.chromium.org/1077113002 Cr-Commit-Position: refs/heads/master@{#27781}
-
wingo authored
This is a follow-up to https://codereview.chromium.org/1078093002. R=rossberg@chromium.org BUG= Review URL: https://codereview.chromium.org/1083623002 Cr-Commit-Position: refs/heads/master@{#27780}
-