- 11 Jun, 2016 3 commits
-
-
peria authored
It is expected that temporarily used strings die while they are in new heap. So we can avoid to pay a heavy cost to externalize them. If they are used for times, externalization will happen when they move to an old heap. BUG=chrmoium:606093 Review-Url: https://codereview.chromium.org/2046933002 Cr-Commit-Position: refs/heads/master@{#36907}
-
v8-autoroll authored
Rolling v8/build to e3d91384eb1f9ee5d3a26ad790f87fc51f3cfc61 Rolling v8/tools/clang to 7f07c3fce21f45df52cf39f0f52277d19b7e3573 Rolling v8/tools/mb to ad1b97c34985d6c464b5b74e75c7c9ec9716fec2 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2057403004 Cr-Commit-Position: refs/heads/master@{#36906}
-
gsathya authored
Review-Url: https://codereview.chromium.org/2053393004 Cr-Commit-Position: refs/heads/master@{#36905}
-
- 10 Jun, 2016 28 commits
-
-
jyan authored
Port c8ac0d86 Original commit message: Instead, always tail call to the runtime. Also, cleanup the various versions of the runtime call that is used for Array construction fallback. There can be only one. R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2060483002 Cr-Commit-Position: refs/heads/master@{#36904}
-
littledan authored
This patch adds a test for async/await analogous to a previous Promise test. It also fixes a typo in promise.js and makes a previous Promise test more correct by ensuring that all assertions run before completion, fixing the test expectations for the real result (which seems correct). BUG=v8:4483 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review-Url: https://codereview.chromium.org/2037653002 Cr-Commit-Position: refs/heads/master@{#36903}
-
jyan authored
Port 757221e5 Original commit message: Neither globals nor lookup slots can be hole-initialized anymore, thus removing some dead code from the code generators and runtime-scopes. R=adamk@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2060473002 Cr-Commit-Position: refs/heads/master@{#36902}
-
bjaideep authored
Port c8ac0d86 Original commit message: Instead, always tail call to the runtime. Also, cleanup the various versions of the runtime call that is used for Array construction fallback. There can be only one. R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG=chromium:608675 LOG=N Review-Url: https://codereview.chromium.org/2057253002 Cr-Commit-Position: refs/heads/master@{#36901}
-
bjaideep authored
Port 2fd55667 Original commit message: We ported hashmap.h into libsampler as a workaround before, so the main focus of this patch is to reduce code duplication. This patch moves the hashmap into src/base as well as creates DefaultAllocationPolicy using malloc and free. R=lpy@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG=v8:5050 LOG=N Review-Url: https://codereview.chromium.org/2057263002 Cr-Commit-Position: refs/heads/master@{#36900}
-
bjaideep authored
Port 757221e5 Original commit message: Neither globals nor lookup slots can be hole-initialized anymore, thus removing some dead code from the code generators and runtime-scopes. R=adamk@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/2061443002 Cr-Commit-Position: refs/heads/master@{#36899}
-
alph authored
Review-Url: https://codereview.chromium.org/2047243002 Cr-Commit-Position: refs/heads/master@{#36898}
-
nikolaos authored
This patch attempts to reduce the (stack) memory footprint of expression classifiers. Instead of keeping space in each classifier for all possible error messages that will (potentially) be reported, if an expression turns out to be a pattern or a non-pattern, such error messages are placed in a list shared by the FunctionState and each classifier keeps a couple of indices in this list. This requires that classifiers are used strictly in a stack-based fashion, which is also in line with my previous patch for revisiting non-pattern rewriting. R=adamk@chromium.org BUG=chromium:528697 Review-Url: https://codereview.chromium.org/1708193003 Cr-Commit-Position: refs/heads/master@{#36897}
-
neis authored
In commit b3bfc0bd, I corrected the source position of yield-exceptions by not setting the "return position" on returns that correspond to yields. It turns out that this caused a bug with debug stepping. The proper fix is to keep the return position on those returns but additionally attach the yield's source position to the Throw emitted in VisitYield. R=rmcilroy@chromium.org, yangguo@chromium.org BUG=v8:4907 Review-Url: https://codereview.chromium.org/2051783002 Cr-Commit-Position: refs/heads/master@{#36896}
-
neis authored
R=mstarzinger@chromium.org BUG= Review-Url: https://codereview.chromium.org/2056283002 Cr-Commit-Position: refs/heads/master@{#36895}
-
ulan authored
after the first GC if time allows and there is memory to be freed. BUG=chromium:618958 LOG=NO Review-Url: https://codereview.chromium.org/2057103002 Cr-Commit-Position: refs/heads/master@{#36894}
-
cbruni authored
BUG= Review-Url: https://codereview.chromium.org/2058003002 Cr-Commit-Position: refs/heads/master@{#36893}
-
ahaas authored
This CL sets the default value of the flag wasm_num_compilation_tasks to 10. The actual number of compilation tasks is the minimum of the flag value and V8::GetCurrentPlatform()->NumberOfAvailableBackgroundThreads(), which is 8 on my machine. R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2054093002 Cr-Commit-Position: refs/heads/master@{#36892}
-
jkummerow authored
BUG=chromium:618845 Review-Url: https://codereview.chromium.org/2058063002 Cr-Commit-Position: refs/heads/master@{#36891}
-
yangguo authored
R=vogelheim@chromium.org Review-Url: https://codereview.chromium.org/2052433003 Cr-Commit-Position: refs/heads/master@{#36890}
-
oth authored
TBR=rmcilroy@chromium.org BUG=v8:4280 LOG=N Review-Url: https://codereview.chromium.org/2056243002 Cr-Commit-Position: refs/heads/master@{#36889}
-
danno authored
Instead, always tail call to the runtime. Also, cleanup the various versions of the runtime call that is used for Array construction fallback. There can be only one. BUG=chromium:608675 LOG=N Review-Url: https://codereview.chromium.org/2024253002 Cr-Commit-Position: refs/heads/master@{#36888}
-
yangguo authored
R=vogelheim@chromium.org Review-Url: https://codereview.chromium.org/2051043003 Cr-Commit-Position: refs/heads/master@{#36887}
-
jarin authored
TBR=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/2057063002 Cr-Commit-Position: refs/heads/master@{#36886}
-
oth authored
BUG=v8:4280 LOG=N Review-Url: https://codereview.chromium.org/2041913002 Cr-Commit-Position: refs/heads/master@{#36885}
-
rmcilroy authored
Remove expectations which were failing due to eager compilation now that we compile lazily in Ignition, and add intersection-observer/observer-exceptions.html which has recently started failing. BUG=v8:5096 TBR=machenbach@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2053323002 Cr-Commit-Position: refs/heads/master@{#36884}
-
cbruni authored
BUG= Review-Url: https://codereview.chromium.org/2050713002 Cr-Commit-Position: refs/heads/master@{#36883}
-
asaka authored
Fix-up of https://codereview.chromium.org/1965443003 required for certain toolchains that do not support std::trunc(). BUG= Review-Url: https://codereview.chromium.org/2056693002 Cr-Commit-Position: refs/heads/master@{#36882}
-
jarin authored
This should solve the problem with missing checkpoints after JSToNumber (PlainPrimitiveToNumber is marked no-write, so the frame-state propagation should see through it.) Unfortunately, this also duplicates the word32- and float64-truncation magic that we have for JSToNumber in "simplified lowering". Review-Url: https://codereview.chromium.org/2059653002 Cr-Commit-Position: refs/heads/master@{#36881}
-
bmeurer authored
This switches Math.log to use an fdlibm based version of log, imported as base::ieee754::log, and use that consistently everywhere, i.e. change the Float64Log TurboFan operators on Intel to use the C++ implementation as well (same for Crankshaft). R=yangguo@chromium.org BUG=v8:5065,v8:5086 Review-Url: https://codereview.chromium.org/2053893003 Cr-Commit-Position: refs/heads/master@{#36880}
-
yangguo authored
And use it to implement existing the existing snapshot API. R=jochen@chromium.org, vogelheim@chromium.org BUG=chromium:617892 Review-Url: https://codereview.chromium.org/2046423002 Cr-Commit-Position: refs/heads/master@{#36879}
-
julien.gilli authored
Some post-mortem metadata constants that are not offsets to objects' properties were incorrectly defined in the accessors table. This change fixes it by moving them from the accessors table to the constants table. More background is available at https://github.com/nodejs/post-mortem/issues/27. R=danno@chromium.org,bmeurer@chromium.org BUG= Review-Url: https://codereview.chromium.org/2051563003 Cr-Commit-Position: refs/heads/master@{#36878}
-
v8-autoroll authored
Rolling v8/build to 303caaa5b8500304a82fd72c4af43d82b218e218 Rolling v8/tools/clang to 717602f21eca67f87ddd66a0f690148bbe191b79 Rolling v8/tools/mb to 87ae1f0b47b310f37d174571b46e7c33717aba0c TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2055163003 Cr-Commit-Position: refs/heads/master@{#36877}
-
- 09 Jun, 2016 9 commits
-
-
adamk authored
Neither globals nor lookup slots can be hole-initialized anymore, thus removing some dead code from the code generators and runtime-scopes. Review-Url: https://codereview.chromium.org/2051073004 Cr-Commit-Position: refs/heads/master@{#36876}
-
oth authored
TBR=rmcilroy@chromium.org BUG=chromium:618757 LOG=N Review-Url: https://codereview.chromium.org/2052993002 Cr-Commit-Position: refs/heads/master@{#36875}
-
jyan authored
port 406146ff Original Commit Message: This makes sure we do not compile ToNumber stub on demand. This makes it easier to use during concurrent compilation. R=jarin@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2052963003 Cr-Commit-Position: refs/heads/master@{#36874}
-
lpy authored
We ported hashmap.h into libsampler as a workaround before, so the main focus of this patch is to reduce code duplication. This patch moves the hashmap into src/base as well as creates DefaultAllocationPolicy using malloc and free. BUG=v8:5050 LOG=n Review-Url: https://codereview.chromium.org/2010243003 Cr-Commit-Position: refs/heads/master@{#36873}
-
jyan authored
port 546dd77f Original Commit Message: Since some builtins use StringToNumberStub (so the code is always there), it makes more sense to have StringToNumber builtin. R=jarin@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2052833003 Cr-Commit-Position: refs/heads/master@{#36872}
-
ishell authored
There are no ICs left that store their state in this field: vector based ICs use feedback vector and the rest three (BinaryOpIC, CompareIC and ToBooleanIC) reconstruct their state from the ExtraICState field. This CL also removes unused InlineCacheState::DEBUG_STUB which was used mostly in Code::is_debug_stub(). The latter now checks if the code is one of the debug builtins instead. BUG=chromium:618701 LOG=Y Review-Url: https://codereview.chromium.org/2052763003 Cr-Commit-Position: refs/heads/master@{#36871}
-
jarin authored
This makes sure we do not compile ToNumber stub on demand. This makes it easier to use during concurrent compilation. Review-Url: https://codereview.chromium.org/2051113002 Cr-Commit-Position: refs/heads/master@{#36870}
-
mstarzinger authored
This removes explicit uses of the RUNTIME_ASSERT macro from some runtime methods. The implicit ones in CONVERT_FOO_ARG_CHECKED will be addressed in a separate CL for all runtime modules at once. R=bmeurer@chromium.org BUG=v8:5066 Review-Url: https://codereview.chromium.org/2057543002 Cr-Commit-Position: refs/heads/master@{#36869}
-
verwaest authored
We have fast-paths in identifier and string scanning that know that so far they have only handled one-byte input. In that case, we can add chars to the literal buffer assuming that it's still in one-byte state, avoiding 2 branches. This seemingly reduces identifier scanning from ~5% to ~4% on octane-codeload. BUG= Review-Url: https://codereview.chromium.org/2044233004 Cr-Commit-Position: refs/heads/master@{#36868}
-