- 04 Mar, 2019 11 commits
-
-
Ross McIlroy authored
BUG=v8:8801 Change-Id: I9d9d9824c6c9ad0176bbfd3723da1b578b17c256 Reviewed-on: https://chromium-review.googlesource.com/c/1495555 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#60001}
-
Sigurd Schneider authored
This reverts commit 131f4a30. Reason for revert: Breaks snapshot builder: https://ci.chromium.org/p/v8/builders/ci/Linux%20Snapshot%20Builder/16103 Original change's description: > [gn] use relative paths for gtest and gmock > > TBR=machenbach@chromium.org > > Bug: v8:8941 > Change-Id: I0bbd119f7a613785b6e5e01cd8e59d5de40d68e1 > Reviewed-on: https://chromium-review.googlesource.com/c/1498473 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#59996} TBR=machenbach@chromium.org,yangguo@chromium.org Change-Id: Ia2f377aa2e0fc69206104c4942085a9ded4534e2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8941 Reviewed-on: https://chromium-review.googlesource.com/c/1497077 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60000}
-
peterwmwong authored
As the TODO's indicate, these helpers only used by TypedArray#join when it was implemented in JS. As of https://chromium-review.googlesource.com/c/v8/v8/+/1369330 TypedArray#join is now implemented Torque and was optimized in a way that no longer requires these helpers anymore. Bug: v8:7624 Change-Id: I1d1ff80235a12feb3846ff92764e8593ce7c72c9 Reviewed-on: https://chromium-review.googlesource.com/c/1498692Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Cr-Commit-Position: refs/heads/master@{#59999}
-
Dan Elphick authored
BytecodeArray::SourcePosition and BytecodeArray::SourceStatementPosition have no implementations and are never called. Bug: v8:8834 Change-Id: I919c871795084766856dfbff5344c037b6f33dd0 Reviewed-on: https://chromium-review.googlesource.com/c/1497009 Commit-Queue: Dan Elphick <delphick@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#59998}
-
Yu Yin authored
Change-Id: I3be3dc8815015c0215d3e3d655394850d85db871 Reviewed-on: https://chromium-review.googlesource.com/c/1490812Reviewed-by:
Predrag Rudic <prudic@wavecomp.com> Reviewed-by:
-
Yang Guo authored
TBR=machenbach@chromium.org Bug: v8:8941 Change-Id: I0bbd119f7a613785b6e5e01cd8e59d5de40d68e1 Reviewed-on: https://chromium-review.googlesource.com/c/1498473Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#59996}
-
Yu Yin authored
After 54a18895, Bug:7464, the permission of the page is read only, but this function need write permission. Since this function is not used, just remove it. Change-Id: I5a5976ab773bd808920893bbd2e3d9796e89e804 Reviewed-on: https://chromium-review.googlesource.com/c/1490813Reviewed-by:
-
Yu Yin authored
Change-Id: I2264b7850f2c091bfd28d90c5bfe36dcfe6e8a11 Reviewed-on: https://chromium-review.googlesource.com/c/1369908Reviewed-by:
-
Benedikt Meurer authored
Remove the duplication of the allocation logic via the AllocateOneByteConsString and AllocateTwoByteConsString helpers, and instead just have a diamond to figure out the result map. This reduces code size of the StringAdd_CheckNone builtin and even seems to be beneficial performance wise. It seems to improve the performance on the `bench-dom-serialize.js` test by around 1% just doing this. Drive-by-fix: Remove the `flags` from CodeStubAssembler::StringAdd() and its helpers, since we no longer support pretenuring of string additions (for quite a while now). Bug: v8:8834, v8:8939 Change-Id: Ia23e02c974b5f572930fcd45be0643094ab2fa98 Doc: https://bit.ly/fast-string-concatenation-in-javascript Reviewed-on: https://chromium-review.googlesource.com/c/1498133 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#59993}
-
Simon Zünd authored
Stringification of Json wrongly used quotes for "true", "false" and "null". Drive-by: Manually flush std::cout when sending messages. This might fix the server on windows. R=tebbi@chromium.org Bug: v8:8880 Change-Id: Ie499595a1b429514c5d8b1d3ece24f4690ece02e Reviewed-on: https://chromium-review.googlesource.com/c/1498132Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#59992}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/9ed5110..9e80056 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/71bae22..e9e89e3 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I1d682a1b5ea7121f431366f1b65d05252c50e78a Reviewed-on: https://chromium-review.googlesource.com/c/1498693Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#59991}
-
- 03 Mar, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/74fd4a8..9ed5110 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/bd30f49..b3bee2e Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/c903198..71bae22 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I80dba99b9c73cf6d705fe91f7757d6a315392ad8 Reviewed-on: https://chromium-review.googlesource.com/c/1497519Reviewed-by:
-
- 02 Mar, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/04fc46b..74fd4a8 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/9950df1..bd30f49 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/a6d41e2..c903198 Rolling v8/tools/swarming_client: https://chromium.googlesource.com/infra/luci/client-py/+log/d50a88f..7a61cf3 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I7233879445d4df56678de72707f3994891eaea72 Reviewed-on: https://chromium-review.googlesource.com/c/1497512Reviewed-by:
-
- 01 Mar, 2019 27 commits
-
-
Anton Bikineev authored
This is a cosmetic change aimed to reduce compilation time spent on instantiating things and potentially reduce code (in case instantiated specializations are in different shared objects). Change-Id: I719b4d376a0d707f4724555a2f404327d19d8477 Reviewed-on: https://chromium-review.googlesource.com/c/1484298 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#59988}
-
Tom Tan authored
When running under simulator, all arm64 JIT instructions are interpreted by simulator via normal memory read, then no need to do icache/dcache flush. Also when running under simulator, cache_type_register_ is set to 0 explicitly in above CacheLineSizes class, which results in 0 value in both dstart and istart, then causes flush on this incorrect range. Bug: chromium:893460 Change-Id: Ief6cb09a0e89f7ede0761ad676ea6a882e9f4600 Reviewed-on: https://chromium-review.googlesource.com/c/1492514 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#59987}
-
Toon Verwaest authored
Change-Id: I1654da286ae15bc028803286a188b5d89111c3d3 Reviewed-on: https://chromium-review.googlesource.com/c/1495983 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#59986}
-
Sathya Gunasekaran authored
I thought about potentially adding the identifer ref to the error but that would require allocating a new string or at the very least increasing the size of the resulting cons string. Given that the parser is pretty performance sensitive, I've decided to not display the identifier. Previously, the error was: _test.js:3: Error a[foo].c = () => { throw Error(); }; ^ Error at a.(anonymous function).c (_test.js:3:26) at _test.js:5:1 With this patch, the error becomes: _test.js:3: Error a[foo].c = () => { throw Error(); }; ^ Error at a.<computed>.c (_test.js:3:26) at _test.js:5:1 Bug: v8:8823 Change-Id: I557b3517e317652c447ca06c5a400e9625353d9b Reviewed-on: https://chromium-review.googlesource.com/c/1495017 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:Mathias Bynens <mathias@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#59985}
-
Jeff Fisher authored
New tests added for: * Runtime.getProperties while debugger is paused * Runtime.exceptionThrown * Runtime.releaseObject/releaseObjectGroup Change-Id: I72b3455e9fb3269c097bf9a383187c119158a722 Reviewed-on: https://chromium-review.googlesource.com/c/1490172 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59984}
-
Georgia Kouveli authored
This is a port of the improvements to the ArgumentsAdaptorTrampoline that previously landed for x64. It skips the arguments adaptor frame creation if the callee cannot observe the actual arguments (as indicated by the "is_safe_to_skip_arguments_adaptor" bit on the SharedFunctionInfo), and instead just massages the current stack frame appropriately (either by pushing more undefineds in case of under application, or by removing the superfluous arguments in case of over application). Due to the 16 byte stack alignment requirement on arm64, we only skip the arguments adaptor frame creation when the difference between the expected and the actual argument number is even. When it is odd, we would still need to copy the actual arguments in the existing frame to account for the padding, which would defeat the point of the improvement. Bug: v8:8895 Tbr: jgruber@chromium.org Doc: http://bit.ly/v8-faster-calls-with-arguments-mismatch Change-Id: I7f13f6f0ba86edb483e088aac145cfcf9c937fef Reviewed-on: https://chromium-review.googlesource.com/c/1491633 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#59983}
-
Sven Sauleau authored
Replaces assertErrorMessage by assertThrows. Previously assertErrorMessage didn't assert the error message that was provided. Change-Id: I30410b43ff16db448776d9f3cae817b1c0966b3d Reviewed-on: https://chromium-review.googlesource.com/c/1496973Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Cr-Commit-Position: refs/heads/master@{#59982}
-
Maciej Goszczycki authored
Bug: v8:8562 Change-Id: I05421c9fa96e6c1d424c6d529922cde02ba2dc37 Reviewed-on: https://chromium-review.googlesource.com/c/1494760Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Maciej Goszczycki <goszczycki@google.com> Cr-Commit-Position: refs/heads/master@{#59981}
-
Daniel Bratell authored
There is both a v8::internal::SourcePosition and a v8::internal::torque::SourcePositon and in jumbo builds an unqualified SourcePositon ended up referring to the wrong one since nobody had told the compiler that the correct one existed. This broke jumbo builds of v8 cctests on Windows (because only in Windows will the compiler look for the symbol in a parent namespace). R=szuend@chromium.org Bug: v8:8880 Change-Id: I7c9ebf68629642b65e86d6a8ae458ec5ff01f2ce Reviewed-on: https://chromium-review.googlesource.com/c/1496972Reviewed-by:
-
Mike Stanton authored
If we make use of this in the generic Array.prototype.filter case we get a performance boost of over 60%. Bug: v8:8213, chromium:920187 Change-Id: Ia116a852f355a9f037850aee86db7284f0023929 Reviewed-on: https://chromium-review.googlesource.com/c/1484297Reviewed-by:
Daniel Clifford <danno@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#59979}
-
Tobias Tebbi authored
To make it obvious these are not defined in C++. Bug: v8:7793 Change-Id: Ib846023992e32ddd10dadc3834ce42b7604a1f48 Reviewed-on: https://chromium-review.googlesource.com/c/1495993Reviewed-by:
-
Simon Zünd authored
This CL changes 'Value' to use an 'Identifier' for its name, where the source position represents the point where it is defined. This is used to support "goto definition" for constants and extern constants. R=tebbi@chromium.org Bug: v8:8880 Change-Id: Ifb9ff08b36cbd9fb2691dbae579d2df29edd651d Reviewed-on: https://chromium-review.googlesource.com/c/1495986Reviewed-by:
-
Michael Achenbach authored
This makes the test runner and numfuzz share the same exit code behavior on errors. This is needed as they also share the same infrastructure logic to collect swarming tasks. Bug: chromium:937228 Change-Id: I155b37c7b10dd22959a4dcf30bbd0321c452236b Reviewed-on: https://chromium-review.googlesource.com/c/1495987Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#59976}
-
Seth Brenith authored
I tried to use more specific union types where appropriate, even though many of these fields are accessed as Object from C++. Bug: v8:7793 Change-Id: I771d9b6459bdc1413019f8ff5ddfd611d1adf61f Reviewed-on: https://chromium-review.googlesource.com/c/1490573 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Junliang Yan authored
Port 4f62b4bb Original Commit Message: This is a port of the improvements to the ArgumentsAdaptorTrampoline that previously landed for x64. It skips the arguments adaptor frame creation if the callee cannot observe the actual arguments (as indicated by the "is_safe_to_skip_arguments_adaptor" bit on the SharedFunctionInfo), and instead just massages the current stack frame appropriately (either by pushing more undefineds in case of under application, or by removing the superfluous arguments in case of over application). R=bmeurer@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com, miladfar@ca.ibm.com BUG= LOG=N Change-Id: I94824c4b3d94f7c93c7526c865b82649426cd3a4 Reviewed-on: https://chromium-review.googlesource.com/c/1495014Reviewed-by:
Milad Farazmand <miladfar@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#59974}
-
Milad Farazmand authored
gcc requires the <algorithm> header for compiling std::sort. This issue is not present when using Clang. Change-Id: Ief7bfd6152754f71194c784b09dce39e357ddd5c Reviewed-on: https://chromium-review.googlesource.com/c/1496280Reviewed-by:
-
Sigurd Schneider authored
TBR=ulan@chromium.org Change-Id: Ic886973633b3631a336b5e549bb4c910d82fe57e Notry: true Reviewed-on: https://chromium-review.googlesource.com/c/1495988 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Michael Achenbach authored
NOTRY=true Bug: chromium:933093 Change-Id: I0945adb70bcecb7542281eae39ce55929ad002ed Reviewed-on: https://chromium-review.googlesource.com/c/1495985Reviewed-by:
-
Mike Stanton authored
This CL moves the following builtins from CSA to Torque: TypedArray.prototype.forEach TypedArray.prototype.reduce TypedArray.prototype.reduceRight A space-saving decision was made in the design -- instead of emitting versions of the central loop for each ElementsKind, a function pointer which knows how to read from the appropriate TypedArray ElementsKind is constructed at the outset, and passed into the loop. This enormously reduces codesize for the TypedArray builtins. We'll have to see if the overhead of the builtin call affects performance too adversely. BUG: v8:8906 Change-Id: I808cd70f58ddbde18f85e5b2a9be0b883a3f6647 Reviewed-on: https://chromium-review.googlesource.com/c/1484292Reviewed-by:
-
Simon Zünd authored
R=mathias@chromium.org Bug: v8:8880 Change-Id: I6954ede6669f19d970ad4257fa4699da2db62fd3 Reviewed-on: https://chromium-review.googlesource.com/c/1495982Reviewed-by:
-
Simon Zünd authored
Instead of accessing JsonValue struct fields directly, typed accessors check that the tag matches with the type access. Drive-by: The factory methods are now static methods on the JsonValue type itself, making call-sites more readable. R=tebbi@chromium.org Bug: v8:8880 Change-Id: I49b37b3ba8eaf1153b8aa93ea08913077c923fdc Reviewed-on: https://chromium-review.googlesource.com/c/1495559 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
-
Toon Verwaest authored
Change-Id: Ie8109300ce134f3f9d0c1619f1375c29af2c8fa6 Reviewed-on: https://chromium-review.googlesource.com/c/1494758Reviewed-by:
-
Ben L. Titzer authored
R=clemensh@chromium.org Change-Id: I1dec320464f5bc80e248cdf0b31b4a095bc54994 Reviewed-on: https://chromium-review.googlesource.com/c/1495981Reviewed-by:
-
Andreas Haas authored
The interpreter is set up specially in cctests to allow more direct testing. This requires sometimes to write special testing code in the interpreter which is different than production code. This CL fixes one instance of testing code which deals with indirect calls. In production code, indirect calls go through the indirect function table which can change over time. In cctests, however, the indirect function table is not set up completely. In cctests the interpreter uses information from the module instead to acquire the target of an indirect call. In that testing code, calls to imported JS functions were not handled. This handling gets added with this CL. CC=fgm@chromium.org R=titzer@chromium.org Bug: v8:7431 Change-Id: I3b90d4ea8fec2633c010dd8359814440c7988509 Reviewed-on: https://chromium-review.googlesource.com/c/1495560Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#59965}
-
tzik authored
The performance regression comes from the extra time of ExtractHandlerContext called by TriggerPromiseReaction, On the previous code, it takes the current Context from Isolate, and on the typical case of the new code, the Context is taken from the promise reaction function, that adds a few memory read ops and a few conditional branches. This CL adds Label::kDeferred to non-typical cases of ExtractHandlerContext, so that newly added instructions have smaller impact under the speculative execution. On a local benchmark, this fixes half of the regression. Bug: chromium:936717 Change-Id: I34ce858f77d7d604dd596711a239160ed8dac383 Reviewed-on: https://chromium-review.googlesource.com/c/1496774 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by:
-
Yu Yin authored
update the missing file in a2d9924c. see https://chromium-review.googlesource.com/c/1470129 port 591408cb to mips. see https://chromium-review.googlesource.com/c/1482915 Update the missing file in a4b19dcc. see https://chromium-review.googlesource.com/c/1460474 Update the missing file in ad3546ab. see https://chromium-review.googlesource.com/c/1434036 Fix compiler warnings. Change-Id: Ie47b1d5aaa3c7f558def92255ce135b0fc0406ec Reviewed-on: https://chromium-review.googlesource.com/c/1490995 Commit-Queue: Michael Hablich <hablich@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
The {AsyncCompileJob} can now always be deleted when initial compilation finished. The previous conditions are redudant, since {baseline_compilation_finished()} is always true when calling {FinishModule()}. R=ahaas@chromium.org Bug: v8:8689 Change-Id: I95c0cf83943630b83216c83db0edbabdfbd71284 Reviewed-on: https://chromium-review.googlesource.com/c/1494008Reviewed-by:Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#59962}
-
