- 22 May, 2015 33 commits
-
-
jochen authored
The blink version is stricter and for parsing it's important that both decoders behave the same. BUG=chromium:489944 R=vogelheim@chromium.org LOG=n Review URL: https://codereview.chromium.org/1148653007 Cr-Commit-Position: refs/heads/master@{#28601}
-
jochen authored
Internally, it invokes GetFunction() which returns a MaybeLocal<> BUG=4134 R=vogelheim@chromium.org LOG=n Review URL: https://codereview.chromium.org/1156693003 Cr-Commit-Position: refs/heads/master@{#28600}
-
machenbach authored
BUG=chromium:425187 LOG=n Review URL: https://codereview.chromium.org/1154833002 Cr-Commit-Position: refs/heads/master@{#28599}
-
mstarzinger authored
R=arv@chromium.org TEST=mjsunit/harmony/spread-array Review URL: https://codereview.chromium.org/1154873002 Cr-Commit-Position: refs/heads/master@{#28598}
-
mvstanton authored
Also introduce new interface descriptors for the trampoline and full versions of those stubs. Currently, the stubs aren't functional. BUG= Review URL: https://codereview.chromium.org/1149903005 Cr-Commit-Position: refs/heads/master@{#28597}
-
mvstanton authored
Consequence of going whole-hog for vector-based Load/KeyedLoad ICs. BUG= Review URL: https://codereview.chromium.org/1152063003 Cr-Commit-Position: refs/heads/master@{#28596}
-
Djordje.Pesic authored
Implement assembler, disassembler tests for all instructions for mips32 and mips64. Additionally, add missing single precision float instructions for r2 and r6 architecture variants in assembler, simulator and disassembler with corresponding tests. Review URL: https://codereview.chromium.org/1145223002 Cr-Commit-Position: refs/heads/master@{#28595}
-
binji authored
This adds a new external type (v8::SharedArrayBuffer) that uses a JSArrayBuffer under the hood. It can be distinguished from an ArrayBuffer by the newly-added is_shared() bit. Currently there is no difference in functionality between a SharedArrayBuffer and an ArrayBuffer. However, a future CL will add the Atomics API, which is only available on an SharedArrayBuffer. All non-atomic accesses are identical to ArrayBuffer accesses. LOG=N BUG= Review URL: https://codereview.chromium.org/1136553006 Cr-Commit-Position: refs/heads/master@{#28594}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1153763003 Cr-Commit-Position: refs/heads/master@{#28593}
-
conradw authored
Deleting an in-bounds character index from a String object should always return false. BUG= LOG=N Review URL: https://codereview.chromium.org/1153673003 Cr-Commit-Position: refs/heads/master@{#28592}
-
jochen authored
Nothing uses it R=rossberg@chromium.org LOG=y BUG=none Review URL: https://codereview.chromium.org/1152523002 Cr-Commit-Position: refs/heads/master@{#28591}
-
yangguo authored
TBR=machenbach@chromium.org NOTRY=true NOTREECHECKS=true Review URL: https://codereview.chromium.org/1150303002 Cr-Commit-Position: refs/heads/master@{#28590}
-
yangguo authored
Revert of Implement SharedArrayBuffer (patchset #7 id:120001 of https://codereview.chromium.org/1136553006/) Reason for revert: breaks build Original issue's description: > Implement SharedArrayBuffer. > > This adds a new external type (v8::SharedArrayBuffer) that uses a JSArrayBuffer under the hood. It can be distinguished from an ArrayBuffer by the newly-added is_shared() bit. > > Currently there is no difference in functionality between a SharedArrayBuffer and an ArrayBuffer. However, a future CL will add the Atomics API, which is only available on an SharedArrayBuffer. All non-atomic accesses are identical to ArrayBuffer accesses. > > BUG= > > Committed: https://crrev.com/57170bff7baf341c666252a7f6a49e9c08d51263 > Cr-Commit-Position: refs/heads/master@{#28588} TBR=jarin@chromium.org,jochen@chromium.org,binji@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1149203003 Cr-Commit-Position: refs/heads/master@{#28589}
-
binji authored
This adds a new external type (v8::SharedArrayBuffer) that uses a JSArrayBuffer under the hood. It can be distinguished from an ArrayBuffer by the newly-added is_shared() bit. Currently there is no difference in functionality between a SharedArrayBuffer and an ArrayBuffer. However, a future CL will add the Atomics API, which is only available on an SharedArrayBuffer. All non-atomic accesses are identical to ArrayBuffer accesses. BUG= Review URL: https://codereview.chromium.org/1136553006 Cr-Commit-Position: refs/heads/master@{#28588}
-
bbudge authored
Changes template parameters from int to AllocationAlignment. LOG=N BUG=v8:4124 Review URL: https://codereview.chromium.org/1152513002 Cr-Commit-Position: refs/heads/master@{#28587}
-
yangguo authored
We want to use the conservative growth strategy during - isolate initialization - bootstrapping a context But not when - not creating a snapshot - running additional code for custom snapshot. R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1155823003 Cr-Commit-Position: refs/heads/master@{#28586}
-
hpayer authored
BUG=chromium:481811 LOG=n Review URL: https://codereview.chromium.org/1148633005 Cr-Commit-Position: refs/heads/master@{#28585}
-
machenbach authored
Revert of Hook up more import/exports in natives. (patchset #3 id:40001 of https://codereview.chromium.org/1154483002/) Reason for revert: [Sheriff] Speculative revert for gc stress failures: http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/481 Original issue's description: > Hook up more import/exports in natives. > > R=jkummerow@chromium.org > > Committed: https://crrev.com/7a918ac9658d11778f39593bfcc19d7c506defd9 > Cr-Commit-Position: refs/heads/master@{#28573} > > Committed: https://crrev.com/e13a39dd7f4062898709d7c68900677df0513995 > Cr-Commit-Position: refs/heads/master@{#28578} TBR=jkummerow@chromium.org,erik.corry@gmail.com,yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1154743003 Cr-Commit-Position: refs/heads/master@{#28584}
-
titzer authored
This reduces the storage per-Node storage from 7 words to 6 and per-edge storage from 6 words to 4. On average this is about 10%-15% space savings over the whole graph. Remove the use of std::deque as the out-of-line storage for inputs. Reduce size of Use links and use pointer arithmetic to find Node from Use. R=mstarzinger@chromium.org,jarin@chromium.org BUG= Review URL: https://codereview.chromium.org/1150923003 Cr-Commit-Position: refs/heads/master@{#28583}
-
erikcorry authored
R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/1128683006 Cr-Commit-Position: refs/heads/master@{#28582}
-
svenpanne authored
First steps only, the TurboFan compilation is still triggered from C++ land. Includes some simplifications/cleanups, too. Review URL: https://codereview.chromium.org/1150263002 Cr-Commit-Position: refs/heads/master@{#28581}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1146113004 Cr-Commit-Position: refs/heads/master@{#28580}
-
rossberg authored
Also, add more literal tests. R=dslomov@chromium.org BUG=v8:3956 LOG=N Review URL: https://codereview.chromium.org/1145213005 Cr-Commit-Position: refs/heads/master@{#28579}
-
yangguo authored
R=jkummerow@chromium.org Committed: https://crrev.com/7a918ac9658d11778f39593bfcc19d7c506defd9 Cr-Commit-Position: refs/heads/master@{#28573} Review URL: https://codereview.chromium.org/1154483002 Cr-Commit-Position: refs/heads/master@{#28578}
-
mstarzinger authored
This just delegates to SharedFunctionInfo::optimization_disabled and was primarily used for assertions. Removing it due to misleading name because already optimized functions reported being "non-optimizable". This relands commit 181d7b85. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1146423002 Cr-Commit-Position: refs/heads/master@{#28577}
-
mvstanton authored
This follows the logic of the load ics, in that the base extra ic state is better encapsulated. Introduce flag vector_stores to aid development of vector-based store ics. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1151253004 Cr-Commit-Position: refs/heads/master@{#28576}
-
bmeurer authored
R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1149663003 Cr-Commit-Position: refs/heads/master@{#28575}
-
machenbach authored
Revert of Hook up more import/exports in natives. (patchset #2 id:20001 of https://codereview.chromium.org/1154483002/) Reason for revert: [Sheriff] Breaks nosnap: http://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20nosnap%20-%20shared/builds/6943 Original issue's description: > Hook up more import/exports in natives. > > R=jkummerow@chromium.org > > Committed: https://crrev.com/7a918ac9658d11778f39593bfcc19d7c506defd9 > Cr-Commit-Position: refs/heads/master@{#28573} TBR=jkummerow@chromium.org,erik.corry@gmail.com,yangguo@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1154793003 Cr-Commit-Position: refs/heads/master@{#28574}
-
yangguo authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1154483002 Cr-Commit-Position: refs/heads/master@{#28573}
-
svenpanne authored
Review URL: https://codereview.chromium.org/1155773003 Cr-Commit-Position: refs/heads/master@{#28572}
-
jing.bao authored
BUG= Review URL: https://codereview.chromium.org/1145513006 Cr-Commit-Position: refs/heads/master@{#28571}
-
danno authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1154463004 Cr-Commit-Position: refs/heads/master@{#28570}
-
machenbach authored
Revert of Revert of Pass GC flags to incremental marker and start incremental marking with (patchset #1 id:1 of https://codereview.chromium.org/1151143002/) Reason for revert: Wasn't the reason... Original issue's description: > Revert of Pass GC flags to incremental marker and start incremental marking with (patchset #3 id:40001 of https://codereview.chromium.org/1156463002/) > > Reason for revert: > [Sheriff] Speculative revert because chromebook is really misbehaving: > http://build.chromium.org/p/client.v8/builders/V8%20Arm/builds/2109 > > I also triggered a retry with the failing build to be sure. If the revert doesn't help or the bot had a scary hiccup, this can reland. > > Original issue's description: > > Pass GC flags to incremental marker and start incremental marking with > > reduce memory footprint in idle notification. > > > > BUG= > > > > Committed: https://crrev.com/4656308147b12405037678b1ab192fb4f2437bbc > > Cr-Commit-Position: refs/heads/master@{#28567} > > TBR=hpayer@chromium.org,ulan@chromium.org > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > BUG= > > Committed: https://crrev.com/634c58a4f10b346a98208ec34d169e1bdb04e1b7 > Cr-Commit-Position: refs/heads/master@{#28568} TBR=hpayer@chromium.org,ulan@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1157613002 Cr-Commit-Position: refs/heads/master@{#28569}
-
- 21 May, 2015 7 commits
-
-
machenbach authored
Revert of Pass GC flags to incremental marker and start incremental marking with (patchset #3 id:40001 of https://codereview.chromium.org/1156463002/) Reason for revert: [Sheriff] Speculative revert because chromebook is really misbehaving: http://build.chromium.org/p/client.v8/builders/V8%20Arm/builds/2109 I also triggered a retry with the failing build to be sure. If the revert doesn't help or the bot had a scary hiccup, this can reland. Original issue's description: > Pass GC flags to incremental marker and start incremental marking with > reduce memory footprint in idle notification. > > BUG= > > Committed: https://crrev.com/4656308147b12405037678b1ab192fb4f2437bbc > Cr-Commit-Position: refs/heads/master@{#28567} TBR=hpayer@chromium.org,ulan@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review URL: https://codereview.chromium.org/1151143002 Cr-Commit-Position: refs/heads/master@{#28568}
-
ulan authored
reduce memory footprint in idle notification. BUG= Review URL: https://codereview.chromium.org/1156463002 Cr-Commit-Position: refs/heads/master@{#28567}
-
ssid authored
The Heap::Available method adds up the available size from only 4 of the spaces. This CL fixes the method to return total of all spaces. BUG=481504 LOG=N Review URL: https://codereview.chromium.org/1141693003 Cr-Commit-Position: refs/heads/master@{#28566}
-
dslomov authored
Also support patterns in ``for (var p in/of ...)`` This CL extends the rewriting we used to do for ``for (let p in/of...)`` to ``for (var p in/of ...)``. For all for..in/of loop declaring variable, we rewrite for (var/let/const pattern in/of e) b into for (x' in/of e) { var/let/const pattern = e; b } This adds a small complication for debugger: for a statement for (var v in/of e) ... we used to have var v; for (v in/of e) ... and there was a separate breakpoint on ``var v`` line. This breakpoint is actually useless since it is immediately followed by a breakpoint on evaluation of ``e``, so this CL removes that breakpoint location. Similiraly, for let, it used to be that for (let v in/of e) ... became for (x' in/of e) { let v; v = x'; ... } ``let v``generetaed a useless breakpoint (with the location at the loop's head. This CL removes that breakpoint as well. R=arv@chromium.org,rossberg@chromium.org BUG=v8:811 LOG=N Review URL: https://codereview.chromium.org/1149043005 Cr-Commit-Position: refs/heads/master@{#28565}
-
verwaest authored
BUG=v8:4137 LOG=n Review URL: https://codereview.chromium.org/1147863002 Cr-Commit-Position: refs/heads/master@{#28564}
-
hans authored
This macro is used for defining static data members with STATIC_CONST_MEMBER_DEFINITION. Clang-cl mimics MSVC's behaviour here, so it also needs __declspec(selectany). This change was prompted by Clang r237787 which changed a bug where Clang would previously not emit symbols for some static data members. BUG=82385 LOG=N Review URL: https://codereview.chromium.org/1145213004 Cr-Commit-Position: refs/heads/master@{#28563}
-
ulan authored
Original issue's description: > Avoid excessive GCs in small heaps. > > Small heaps and small heap growing factor can lead to excessive GCs in corner cases. > > Consider function F(old_gen_size, factor) that returns the number of bytes that > have to be allocated in the old generation to start incremental marking. > > F(4MB, 1.1) = 4MB (because of kMinimumOldGenerationAllocationLimit) > F(6MB, 1.1) = 2MB (because of kMinimumOldGenerationAllocationLimit) > F(8MB, 1.1) = 800KB > > Funtion F should be monotonic in old_gen_size, but it currently has a minimum > at kMinimumOldGenerationAllocationLimit. > > This CL makes F monotonic. > > BUG= > > Committed: https://crrev.com/22b1da99732b4db0754bf267ec470a2831216fb2 > Cr-Commit-Position: refs/heads/master@{#28549} TBR=hpayer@chromium.org Review URL: https://codereview.chromium.org/1148953005 Cr-Commit-Position: refs/heads/master@{#28562}
-