- 24 Mar, 2017 20 commits
-
-
hpayer authored
This reverts commit 00d3098d. BUG=chromium:694255,v8:6138 Review-Url: https://codereview.chromium.org/2773093002 Cr-Commit-Position: refs/heads/master@{#44100}
-
Michael Starzinger authored
R=machenbach@chromium.org BUG=v8:6127 Change-Id: I65a6905e57ff47195503b37118c279d22f0baba0 Reviewed-on: https://chromium-review.googlesource.com/459536 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#44099}
-
Michael Achenbach authored
Bug: v8:6132 NOTRY=true TBR=jgruber@chromium.org,eholk@chromium.org Change-Id: Idd706e5bb08f1890f6edc69792238114aadf220b Reviewed-on: https://chromium-review.googlesource.com/459517Reviewed-by:
-
Wiktor Garbacz authored
A step towards removing isolate from ParseInfo. Removing isolate from ParseInfo will make it easier to create and execute parse tasks on background threads. BUG=v8:6093 Change-Id: I2a3a8a02d791d7ae6acc2243e2f430defc3be5ea Reviewed-on: https://chromium-review.googlesource.com/458002 Commit-Queue: Wiktor Garbacz <wiktorg@google.com> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#44097}
-
Wiktor Garbacz authored
A step towards removing isolate from ParseInfo. Removing isolate from ParseInfo will make it easier to create and execute parse tasks on background threads. BUG=v8:6093 Change-Id: Iefd2fd01a700509f05d6f1a272cfa39cc545d39b Reviewed-on: https://chromium-review.googlesource.com/458001Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
tebbi authored
BUG=chromium:699251 R=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/2766383003 Cr-Commit-Position: refs/heads/master@{#44095}
-
Michael Achenbach authored
Bug: chromium:645890 TBR=yangguo@chromium.org NOTRY=true Change-Id: I83bf77a82317c3394d1b81133e52a8b6ecfbe360 Reviewed-on: https://chromium-review.googlesource.com/459418Reviewed-by:
-
mvstanton authored
BUG= Review-Url: https://codereview.chromium.org/2765293002 Cr-Commit-Position: refs/heads/master@{#44093}
-
yangguo authored
R=jgruber@chromium.org BUG=v8:5821 Review-Url: https://codereview.chromium.org/2772853003 Cr-Commit-Position: refs/heads/master@{#44092}
-
Toon Verwaest authored
BUG=chromium:704110,v8:5561 Change-Id: Ie57bccd2f9da714b179f69c14242bcf056d3065f Reviewed-on: https://chromium-review.googlesource.com/459476Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#44091}
-
Igor Sheludko authored
Currently, the overlapping results of individual benchmark tests are overwritten. Example: tools/perf-compare.py Result,ss.json,kr.json Master,kr-m.json,ss-m.json -o compare.html or tools/perf-compare.py Result,ss.json Result,kr.json Master,kr-m.json Master,ss-m.json -o compare.html BUG=v8:6144 NOTRY=true Change-Id: Ia340e8c01c46da17b1f4eee6c6bb8e5e9bb12c3e Reviewed-on: https://chromium-review.googlesource.com/459537 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Wiktor Garbacz authored
A step towards removing isolate from ParseInfo. Removing isolate from ParseInfo will make it easier to create and execute parse tasks on background threads. BUG=v8:6093 Change-Id: If5e7ba2f76f9f8422c26f47c9f0eb5b197114b25 Reviewed-on: https://chromium-review.googlesource.com/458000Reviewed-by:
-
Michael Achenbach authored
TBR=hablich@chromium.org NOTRY=true NOPRESUBMIT=true Change-Id: I47d81840f624ac9c119fee39961b4ec3d7bcba8f Reviewed-on: https://chromium-review.googlesource.com/459516Reviewed-by:
-
Michael Achenbach authored
BUG=chromium:645890 NOTRY=true TBR=jochen@chromium.org,vogelheim@chromium.org Change-Id: I559412b0b85af87494f6d14d0a3b6a016449fc14 Reviewed-on: https://chromium-review.googlesource.com/458657Reviewed-by:
-
ivica.bogosavljevic authored
Port 798ffc9d TEST=mjsunit/compiler/regress-v8-6077 BUG= Review-Url: https://codereview.chromium.org/2773583003 Cr-Commit-Position: refs/heads/master@{#44086}
-
Igor Sheludko authored
The former will handle stores to global variables, lets and undeclared variables. The latter will handle named stores to explicit receiver. BUG=chromium:576312, v8:5561 Change-Id: I335fa21db47c3d001da8cc79fa8cb6f8abcbb7e2 Reviewed-on: https://chromium-review.googlesource.com/458639Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#44085}
-
bradnelson authored
Add the --fast-validate-asm option, which directs asm.js code to a new parser + validator + wasm code generator, which is then compiled using WebAssembly. This parser takes advantage of asm.js structure to linearly parse asm.js code, keeping a scope stack + a few additional tables to track varibles. BUG=v8:6090 BUG=v8:4203 R=mstarzinger@chromium.org,marja@chromium.org,vogelheim@chromium.org,kschimpf@chromium.org Review-Url: https://codereview.chromium.org/2757693003 Cr-Commit-Position: refs/heads/master@{#44084}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/4a2354d..96aa45c Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/2038d74..5c300b0 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Change-Id: I88915820ceec01e636e888a231dd56d9c0091dac Reviewed-on: https://chromium-review.googlesource.com/458937Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#44083}
-
kozyatinskiy authored
+ added a test. BUG=none R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2743163002 Cr-Commit-Position: refs/heads/master@{#44082}
-
kozyatinskiy authored
- added InspectorTest.setupInjectedScriptEnvironment method which mutates current context, - clear prototype of InjectedScript function and domAttributesWithObservableSideEffectOnGet. Second point increases chances that injected-script-source would be successfully compiled. BUG=chromium:693338 R=dgozman@chromium.org,luoe@chromium.org Review-Url: https://codereview.chromium.org/2770823003 Cr-Commit-Position: refs/heads/master@{#44081}
-
- 23 Mar, 2017 20 commits
-
-
machenbach authored
Revert of [debug] do not report unnecessary coverage data. (patchset #4 id:60001 of https://codereview.chromium.org/2764073004/ ) Reason for revert: breaks layout tests: https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/14438 Original issue's description: > [debug] do not report unnecessary coverage data. > > Only include function ranges for with non-0 counts or if the immediate outer function has non-0 count. > > R=caseq@chromium.org, jgruber@chromium.org > BUG=v8:5808 > > Review-Url: https://codereview.chromium.org/2764073004 > Cr-Commit-Position: refs/heads/master@{#44079} > Committed: https://chromium.googlesource.com/v8/v8/+/a7577ede0b74967727895eba5e06dbe1d01fb56d TBR=caseq@chromium.org,jgruber@chromium.org,yangguo@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:5808 Review-Url: https://codereview.chromium.org/2769063004 Cr-Commit-Position: refs/heads/master@{#44080}
-
yangguo authored
Only include function ranges for with non-0 counts or if the immediate outer function has non-0 count. R=caseq@chromium.org, jgruber@chromium.org BUG=v8:5808 Review-Url: https://codereview.chromium.org/2764073004 Cr-Commit-Position: refs/heads/master@{#44079}
-
Bradley.Meck authored
There was a security issue from allowing WindowProxy to have its prototype mutated in https://bugs.chromium.org/p/chromium/issues/detail?id=399951 . This has since been resolved by making `window`, `location`, and `Object.prototype.__proto__` immutable. This change was fixed in https://bugs.chromium.org/p/v8/issues/detail?id=5149 . Reverts https://codereview.chromium.org/1529303003 R=littledan@chromium.org R=verwaest@chromium.org Review-Url: https://codereview.chromium.org/2671553006 Cr-Commit-Position: refs/heads/master@{#44078}
-
Michael Lippautz authored
BUG=chromium:651354 Change-Id: Ie9d39306c3baf2462ea5eee4f5a5ff436912744e Reviewed-on: https://chromium-review.googlesource.com/458423Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#44077}
-
skyostil authored
This patch makes Math.random() behave deterministically when a fixed random seed is provided. This is done by re-seeding the random number generator the first time a script requests a random number. Doing this ensures Math.random() returns the same sequence across page loads and across iframes. BUG=chromium:696001 Review-Url: https://codereview.chromium.org/2760393002 Cr-Commit-Position: refs/heads/master@{#44076}
-
binji authored
BUG=v8:5897 Review-Url: https://codereview.chromium.org/2741413006 Cr-Commit-Position: refs/heads/master@{#44075}
-
yangguo authored
With precise binary code coverage, the reported count is either 0 or 1. We only report 1 the first time we collect coverage data after the function has been executed. Since we do not care about the accurate execution count, we can optimize the function once it has been executed once. Also change best effort coverage to be implicitly binary. R=caseq@chromium.org, jgruber@chromium.org, pfeldman@chromium.org BUG=v8:5808 Review-Url: https://codereview.chromium.org/2766573003 Cr-Commit-Position: refs/heads/master@{#44074}
-
Toon Verwaest authored
BUG=chromium:703226 Change-Id: I2232d4a721beb35478066b25143b9635bcc6b238 Reviewed-on: https://chromium-review.googlesource.com/458429Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#44073}
-
Toon Verwaest authored
Removed the invalid DCHECKs altogether. BUG=v8:5561 Change-Id: I678b80a2f216a84333e3fe65843ca9dfc0bdf0d5 Reviewed-on: https://chromium-review.googlesource.com/458280 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Michael Achenbach authored
BUG=chromium:645890 Change-Id: Iec8f473074a65abe9b4fbc968d5617038120efa5 Reviewed-on: https://chromium-review.googlesource.com/458011 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#44071}
-
sampsong authored
R=bjaideep@ca.ibm.com, jyan@ca.ibm.com, joransiu@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2760983003 Cr-Commit-Position: refs/heads/master@{#44070}
-
jgruber authored
BUG=v8:5437 Review-Url: https://codereview.chromium.org/2766423004 Cr-Commit-Position: refs/heads/master@{#44069}
-
pierre.langlois authored
When using --trace-ignition-codegen, the name for each bytecode handler is missing. The reason is that we find the name of a bytecode by looking up the code object entry in the interpreter's dispatch table, which is not yet populated at this point. BUG= Review-Url: https://codereview.chromium.org/2771503004 Cr-Commit-Position: refs/heads/master@{#44068}
-
jgruber authored
This is just an update to reflect the current spec proposal. https://tc39.github.io/proposal-regexp-named-groups/ BUG=v8:5437 Review-Url: https://codereview.chromium.org/2769143002 Cr-Commit-Position: refs/heads/master@{#44067}
-
Michael Achenbach authored
BUG=chromium:645890 NOTRY=true TBR=jochen@chromium.org,vogelheim@chromium.org Change-Id: Id0e972bf2480dd9c48e064537090a7bd97431db1 Reviewed-on: https://chromium-review.googlesource.com/458223Reviewed-by:
-
ahaas authored
Stack overflow checks are typically implemented as part of the TurboFan graph of a function. This means that the stack check code is executed after frame construction. When a frame is too big, though, there may not be enough space on the stack anymore to throw the stack overflow exception after frame construction. With this CL we do an additional stack check before frame construction for functions with big frames. As discussed offline with mstarzinger, I do this change currently only for WebAssembly. This CL contains only the changes for arm. I will do the other platforms in separate CLs. R=mstarzinger@chromium.org, v8-arm-ports@googlegroups.com Review-Url: https://codereview.chromium.org/2763593002 Cr-Commit-Position: refs/heads/master@{#44065}
-
kozyatinskiy authored
BUG=none TBR=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2773723002 Cr-Commit-Position: refs/heads/master@{#44064}
-
ahaas authored
When available, we use the NEON instructions vld1.8 and vst1.8 to implement unaligned loads and stores of float64 values. R=bmeurer@chromium.org, v8-arm-ports@googlegroups.com Review-Url: https://codereview.chromium.org/2769723003 Cr-Commit-Position: refs/heads/master@{#44063}
-
Michael Starzinger authored
R=machenbach@chromium.org BUG=v8:6127 Change-Id: Iced2bd9e71006077aca4bd1de8dd14b6c771ec86 Reviewed-on: https://chromium-review.googlesource.com/458222Reviewed-by:
-
bradnelson authored
BUG=v8:6090 R=marja@chromium.org Review-Url: https://codereview.chromium.org/2769013002 Cr-Commit-Position: refs/heads/master@{#44061}
-
