- 20 Dec, 2016 40 commits
-
-
littledan authored
eval() may introduce a scope which needs to be represented as a context at runtime, e.g., eval('var x; let y; ()=>y') introduces a variable y which needs to have a context allocated for it. However, when traversing upwards to find the declaration context for a variable which leaks, as the declaration of x does above, this context has to be understood to not be a declaration context in sloppy mode. This patch makes that distinction by introducing a different map for eval-introduced contexts. A dynamic search for the appropriate context will continue past an eval context to find the appropriate context. Marking contexts as eval contexts rather than function contexts required updates in each compiler backend. BUG=v8:5295, chromium:648719 Review-Url: https://codereview.chromium.org/2435023002 Cr-Commit-Position: refs/heads/master@{#41869}
-
bmeurer authored
The %TypedArray% constructor must not ever try to construct an instance, but rather throw a TypeError instead. R=jarin@chromium.org BUG=v8:5763 Review-Url: https://codereview.chromium.org/2587413002 Cr-Commit-Position: refs/heads/master@{#41868}
-
littledan authored
The Intl implementation included manual checks to see if they were being called as a constructor. However, these checks are redundant, as %FunctionRemovePrototype has already marked the functions as un-constructable. This path removes the unnecessary checks. R=yangguo Review-Url: https://codereview.chromium.org/2587713002 Cr-Commit-Position: refs/heads/master@{#41867}
-
titzer authored
R=clemensh@chromium.org CC=rossberg@chromium.org BUG=chromium:575167 Review-Url: https://codereview.chromium.org/2591753002 Cr-Commit-Position: refs/heads/master@{#41866}
-
jochen authored
R=ishell@chromium.org BUG= Review-Url: https://codereview.chromium.org/2590923002 Cr-Commit-Position: refs/heads/master@{#41865}
-
jyan authored
R=joransiu@ca.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2589063002 Cr-Commit-Position: refs/heads/master@{#41864}
-
titzer authored
R=clemensh@chromium.org BUG= Review-Url: https://codereview.chromium.org/2590833002 Cr-Commit-Position: refs/heads/master@{#41863}
-
clemensh authored
The new object will hold information which is shared by all clones of a WasmCompiledModule, e.g. the decoded asm.js offset table, and in the future also breakpoints. From there, we can set them on each new instantiation of any clone. While already changing lots of the code base, I also renamed all getters from "get_foo" to "foo", to conform to the style guide. R=titzer@chromium.org, yangguo@chromium.org BUG=v8:5732 Review-Url: https://codereview.chromium.org/2591653002 Cr-Commit-Position: refs/heads/master@{#41862}
-
marja authored
See tracking bug for more information. BUG=v8:5402 Review-Url: https://codereview.chromium.org/2594663002 Cr-Commit-Position: refs/heads/master@{#41861}
-
jgruber authored
These benchmarks are intended to compare the overhead of async-await vs. a naive promise implementation vs. the babel async-await transformation. The functions in the benchmark don't do any work themselves, so results should reflect only overhead of the chosen implementation. Current numbers on my local machine (higher is better): BaselineES2017-AsyncAwait(Score): 2006 BaselineNaivePromises-AsyncAwait(Score): 7470 Native-AsyncAwait(Score): 3640 BUG=v8:5639 Review-Url: https://codereview.chromium.org/2577393002 Cr-Commit-Position: refs/heads/master@{#41860}
-
bbudge authored
LOG=N BUG=v8:4124 Review-Url: https://codereview.chromium.org/2593443002 Cr-Commit-Position: refs/heads/master@{#41859}
-
cbruni authored
BUG=chromium:674889 Review-Url: https://codereview.chromium.org/2593593002 Cr-Commit-Position: refs/heads/master@{#41858}
-
tebbi authored
R=jarin@chromium.org BUG=chromium:669242 Review-Url: https://codereview.chromium.org/2589163002 Cr-Commit-Position: refs/heads/master@{#41857}
-
cbruni authored
Add inlineable fast-paths for Object::ToPropertyKey, Object::ToLength and Object::ToIndex for the most common argument types. BUG= Review-Url: https://codereview.chromium.org/2587013002 Cr-Commit-Position: refs/heads/master@{#41856}
-
yangguo authored
Currently, to find out a Promise's status and result, one has to use the debug context. This is for example done in Node.js. This new API is a better replacement, also in the context of the debug context being deprecated eventually. R=franzih@chromium.org, gsathya@chromium.org, jochen@chromium.org BUG=v8:5764 Review-Url: https://codereview.chromium.org/2589113002 Cr-Commit-Position: refs/heads/master@{#41855}
-
jochen authored
BUG=none R=epertoso@chromium.org,mvstanton@chromium.org,cbruni@chromium.org Review-Url: https://codereview.chromium.org/2588363002 Cr-Commit-Position: refs/heads/master@{#41854}
-
clemensh authored
Plus another minor refactoring. R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2590563002 Cr-Commit-Position: refs/heads/master@{#41853}
-
leszeks authored
BUG=v8:5762 Review-Url: https://codereview.chromium.org/2590843002 Cr-Commit-Position: refs/heads/master@{#41852}
-
clemensh authored
We have the BytecodeIterator with next() and has_next() methods, and pc_offset() and current() accessors. This CL adds an interface to iterate over the opcodes or offsets in a C++ foreach loop. R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2587143002 Cr-Commit-Position: refs/heads/master@{#41851}
-
titzer authored
R=clemensh@chromium.org BUG= Review-Url: https://codereview.chromium.org/2592563003 Cr-Commit-Position: refs/heads/master@{#41850}
-
titzer authored
R=bmeurer@chromium.org BUG=chromium:674232 Review-Url: https://codereview.chromium.org/2592633002 Cr-Commit-Position: refs/heads/master@{#41849}
-
tebbi authored
R=jarin@chromium.org BUG=chromium:673243 Review-Url: https://codereview.chromium.org/2578133002 Cr-Commit-Position: refs/heads/master@{#41848}
-
clemensh authored
Before, source position information was only emitted for nodes contained in a block, which excluded calls that terminate a block. R=mstarzinger@chromium.org, titzer@chromium.org Review-Url: https://codereview.chromium.org/2586123003 Cr-Commit-Position: refs/heads/master@{#41847}
-
ishell authored
[crankshaft] Ensure that we use inlined Array.prototype.shift only when there's no elements in the prototype chain. BUG=chromium:663340 Review-Url: https://codereview.chromium.org/2593553002 Cr-Commit-Position: refs/heads/master@{#41846}
-
cbruni authored
Revert of [runtime] Add fast-paths for common conversion methods (patchset #1 id:1 of https://codereview.chromium.org/2587013002/ ) Reason for revert: breaks mips port: http://build.chromium.org/p/client.v8.ports/builders/V8%20Mips%20-%20builder/builds/6131 Original issue's description: > [runtime] Add fast-paths for common conversion methods > > Add inlineable fast-paths for Object::ToPropertyKey, Object::ToLength and > Object::ToIndex for the most common argument types. > > BUG= > > Review-Url: https://codereview.chromium.org/2587013002 > Cr-Commit-Position: refs/heads/master@{#41839} > Committed: https://chromium.googlesource.com/v8/v8/+/d173807b9d8cb3c4cc4ee9c94c5cc960224b2c40 TBR=jgruber@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2587373002 Cr-Commit-Position: refs/heads/master@{#41845}
-
machenbach authored
BUG=chromium:673246 NOTRY=true Review-Url: https://codereview.chromium.org/2589683003 Cr-Commit-Position: refs/heads/master@{#41844}
-
clemensh authored
This moves the platform-specific distinction to one place, and allows to just include assembler-inl.h instead of macro-assembler.h to get the correct inline functions defined in assembler.h (e.g. RelocInfo::set_target_address). R=mstarzinger@chromium.org, titzer@chromium.org Review-Url: https://codereview.chromium.org/2587113002 Cr-Commit-Position: refs/heads/master@{#41843}
-
ishell authored
BUG=chromium:665793 Review-Url: https://codereview.chromium.org/2589823003 Cr-Commit-Position: refs/heads/master@{#41842}
-
mlippautz authored
BUG= TBR=hpayer@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2587363002 Cr-Commit-Position: refs/heads/master@{#41841}
-
hpayer authored
BUG= Review-Url: https://codereview.chromium.org/2590133002 Cr-Commit-Position: refs/heads/master@{#41840}
-
cbruni authored
Add inlineable fast-paths for Object::ToPropertyKey, Object::ToLength and Object::ToIndex for the most common argument types. BUG= Review-Url: https://codereview.chromium.org/2587013002 Cr-Commit-Position: refs/heads/master@{#41839}
-
hpayer authored
BUG= Review-Url: https://codereview.chromium.org/2592603002 Cr-Commit-Position: refs/heads/master@{#41838}
-
mlippautz authored
BUG=chromium:468240 Review-Url: https://codereview.chromium.org/2576453002 Cr-Commit-Position: refs/heads/master@{#41837}
-
machenbach authored
BUG=chromium:673246 NOTRY=true Review-Url: https://codereview.chromium.org/2585193003 Cr-Commit-Position: refs/heads/master@{#41836}
-
machenbach authored
Revert of Turn on icu_case_mapping by default (patchset #3 id:40001 of https://codereview.chromium.org/2588963002/ ) Reason for revert: Causes gc stress failures: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/9920 Original issue's description: > Turn on icu_case_mapping by default > > BUG=v8:4477, v8:4476 > TEST=test262/{built-ins,intl402}/Strings/*, webkit/fast/js/*, > mjsunit/string-case, intl/general/case* > > Review-Url: https://codereview.chromium.org/2588963002 > Cr-Commit-Position: refs/heads/master@{#41834} > Committed: https://chromium.googlesource.com/v8/v8/+/7c79e23c34ea971947eedc6e42d8a882617c0e47 TBR=littledan@chromium.org,yangguo@chromium.org,jshin@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4477, v8:4476 Review-Url: https://codereview.chromium.org/2593543002 Cr-Commit-Position: refs/heads/master@{#41835}
-
jshin authored
BUG=v8:4477, v8:4476 TEST=test262/{built-ins,intl402}/Strings/*, webkit/fast/js/*, mjsunit/string-case, intl/general/case* Review-Url: https://codereview.chromium.org/2588963002 Cr-Commit-Position: refs/heads/master@{#41834}
-
leszeks authored
This simplifies the mark getter enough to generate a branch-free check on many architectures (e.g. using cmov on x64 or csel on ARM). As a drive-by, we can now make the mark access const. Review-Url: https://codereview.chromium.org/2583043004 Cr-Commit-Position: refs/heads/master@{#41833}
-
yangguo authored
R=jgruber@chromium.org BUG=v8:5530 Review-Url: https://codereview.chromium.org/2589083002 Cr-Commit-Position: refs/heads/master@{#41832}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/29ac3ae..53a8a4b Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/4fc1816..70f42a7 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/fe25d46..fcefe9f TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2589043002 Cr-Commit-Position: refs/heads/master@{#41831}
-
alph authored
Revert of [profiler] Add extra CHECK to track down crbug.com/665398 (patchset #1 id:1 of https://codereview.chromium.org/2556833003/ ) Reason for revert: Not needed anymore. The bug is fixed. Original issue's description: > [profiler] Add extra CHECK to track down crbug.com/665398 > > BUG=chromium:665398 > > Committed: https://crrev.com/dfc0bb63a1bc115d39f29cfc338aed5676578c4b > Cr-Commit-Position: refs/heads/master@{#41545} TBR=yangguo@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG=chromium:665398 Review-Url: https://codereview.chromium.org/2588973003 Cr-Commit-Position: refs/heads/master@{#41830}
-