- 09 Apr, 2019 5 commits
-
-
Jakob Gruber authored
In mksnapshot, we only need to ensure we generate counter code in (embedded) builtins, if needed. The counter function does not need to do anything useful as long as it returns unique pointers for each counter, and we don't need to dump counters. Tbr: petermarshall@chromium.org Change-Id: I94a53ef5193b89365948d0395e1908e6d3c6e396 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549159Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#60694}
-
Mike Stanton authored
Just set the flag --use-osr to false by default. If it's set to true on the command line, then it'll be on. I'd like to get some performance metrics on various tests spread throughout our performance bot infrastructure. Change-Id: I1ebc33264505af080901e531dca625452880f81b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1558089Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#60693}
-
Benedikt Meurer authored
In RecordVirtualBytecodeArrayDetails() check whether the BytecodeArray has a source position table before accessing it, otherwise it will just crash with --enable-lazy-source-positions. Bug: v8:8510 Change-Id: I1250e89faf836a8d5976ca98c14b6b7314bacb98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559730 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#60692}
-
Milad Farazmand authored
Removing NumberToSize on PPC and S390. Port ad44c258 Change-Id: Ic5d3132f1bb396f07a26399d2e3f6aca4689aa3f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554227 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60691}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7db6cfc..2c7bf07 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/979fc35..6145021 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/0b62ed7..1fb0463 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I769bbaa03b4d71b2aad521e64c48bafa12ef27fd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559195Reviewed-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@{#60690}
-
- 08 Apr, 2019 20 commits
-
-
Francis McCabe authored
This reverts commit a1fdd521. Reason for revert: <INSERT REASONING HERE> Original change's description: > Torquefy a few more types > > WeakFixedArray, WeakArrayList, JSFinalizationGroup, JSFinalizationGroupCleanupIterator, WeakCell, JSWeakRef, BytecodeArray, SourcePositionWithFrameCache > > Bug: v8:8952 > > Change-Id: I9708b08e11603977aeab7bce94b8233a41700ccb > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1504433 > Commit-Queue: Irina Yatsenko <irinayat@microsoft.com> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60688} TBR=rmcilroy@chromium.org,jgruber@chromium.org,irinayat@microsoft.com Change-Id: I55b3571763ea054e47d8bef855769e8ca9a1545d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8952 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559210Reviewed-by:
Francis McCabe <fgm@chromium.org> Commit-Queue: Francis McCabe <fgm@chromium.org> Cr-Commit-Position: refs/heads/master@{#60689}
-
Irina Yatsenko authored
WeakFixedArray, WeakArrayList, JSFinalizationGroup, JSFinalizationGroupCleanupIterator, WeakCell, JSWeakRef, BytecodeArray, SourcePositionWithFrameCache Bug: v8:8952 Change-Id: I9708b08e11603977aeab7bce94b8233a41700ccb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1504433 Commit-Queue: Irina Yatsenko <irinayat@microsoft.com> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#60688}
-
Tom Anderson authored
See the changes in BUILD.gn for an explanation of why a new flag is necessary. It's likely that current usages of V8_TARGET_OS_* and V8_TARGET_ARCH_* also need to change, but this is good enough for now to ensure both Win/cross/x86 and Win/cross/x64 build. BUG=chromium:945659 R=machenbach,thakis TBR=jgruber Change-Id: Ie2765db91a1c0d8c72ccf42c9d7fece792d9b252 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1542500 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#60687}
-
Benedikt Meurer authored
This changes the existing cctest/test-field-type-tracking tests to use actual Code objects and proper code dependencies to test that the runtime actually does the right thing (aka deoptimizes the Code objects correctly). Before it was using the CompilationDependencies, which as of now no longer check whether the runtime actually deoptimized or not. This is a prerequisite for changing the way we handle field representation changes, specifically going from Smi or HeapObject to Tagged. Bug: v8:8749, v8:8865 Change-Id: I260294217550cee2b42f7ba7e9c92bf0d1db0b8c Doc: http://bit.ly/v8-in-place-field-representation-changes Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557149 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60686}
-
Sigurd Schneider authored
Change-Id: I5fda56fb53fb5a7daa45b08ad18848e849ef7128 Bug: v8:9020 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557145Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60685}
-
Michael Starzinger authored
This adds preliminary support for references types as argument or return values to functions that are redirected to the interpreter. The current interpreter entry stub remains unchanged, using one buffer area that is hidden from the GC. The corresponding {Runtime_WasmRunInterpreter} now correctly boxes/un-boxes reference types into handles. This switch to a handlified representation happens before any method that potentially triggers a GC is called. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-anyref-interpreter BUG=v8:8091,v8:7581 Change-Id: I41c766ed5ac877042d5964e72f3fd7df390c4e98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557147 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60684}
-
Benedikt Meurer authored
This CL contains a bunch of different improvements to the existing object stats, namely: - Introduce DEPRECATED_DESCRIPTOR_ARRAY_TYPE virtual instance type to also estimate the memory overhead of DescriptorArrays for deprecated Maps. - Do proper over-allocation computating for inobject fields in JSObjects. - Introduce OBJECT_PROPERTY_ARRAY_TYPE virtual instance type and properly compute over-allocation for PropertyArrays - Compute over-allocation for JSObject/JSArray elements properly. - Correctly report JSFunction and JSCollection like the other JSObjects, specifically report over-allocation properly for the instances itself and for the elements/properties backing stores. - Implement correct over-allocation computation for hash tables in ObjectStatsCollectorImpl::RecordHashTableVirtualObjectStats(). Bug: v8:7266 Change-Id: I9cadd703266dc90911a8e7420c3b00dcee82b06d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557139 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Seth Brenith authored
Flag syntax is explained in a comment in flags.h, but we can make d8 easier to learn for new people if we also expose that explanation in the --help text. Change-Id: I7fd9ad0e545c2d9110119c0283bb14d665bcf19e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1555061Reviewed-by:
-
Benedikt Meurer authored
For CheckNonEmptyString we not only need to rule out that the input is not the empty string, but also make sure that the input is actually a string, hence we need to do a proper instance type check in the general case. Bug: chromium:949996, chromium:947949, v8:8834, v8:8931, v8:8939, v8:8951 Change-Id: Icc260d735d19337bba4bb71570a6c6385e47c310 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557146 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60681}
-
Maya Lekova authored
The JSInliningHeuristic is now completely heap-access free. JSInliner still includes Allow* guards and will be brokerized as a follow-up CL. R=neis@chromium.org Bug: v8:7790 Change-Id: I6df5d8515bb8bd8d512e8442e4f4dba9ebe9dd2e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1528437Reviewed-by:
-
Sigurd Schneider authored
Change-Id: Ib3affef6a02a017ade2468dff58c58320e1cde42 Bug: v8:9020 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557144Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60679}
-
Dan Elphick authored
Marks following previously annotated V8_DEPRECATE_SOON methods as V8_DEPRECATED: Value::ToBoolean Value::ToNumber Value::ToString Value::ToObject Value::ToInteger Value::ToInt32 String::NewFromTwoByte String::NewExternal Date::DateTimeConfigurationChangeNotification Bug: v8:7279, v8:7281 Change-Id: I54778ac42bd43afd2fa4f08ffc9f55e71fa43775 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552788Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#60678}
-
Sigurd Schneider authored
Change-Id: I90be28728842a1ab5a4d4d674298e71f70043e80 Notry: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549163 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
Change-Id: I51e32bc344c80d67a23d33039fda49bb9620a78f Notry: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549165 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
This ensures that ApiObjects in V8 are not dropped if they are currently used as WeakCollection keys. As proxy to determine key status we use the presence of the identity hash on the object. R=ulan@chromium.org Bug: v8:8557, chromium:949244 Change-Id: Ifa0e24be44431a0200fd6a1d9898cd366b940bd5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557143Reviewed-by:
-
Georg Neis authored
R=bmeurer@chromium.org Change-Id: Ibfe4a0f12eedd2b4d6a5614e99f2076c026aea24 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557141Reviewed-by:
-
Pierre Langlois authored
We would only increment write barrier counters from the the MacroAssembler's RecordWrite method which is only used in limited cases. Instead, we should increment it inside the RecordWrite stub, this way we catch all uses, including WASM. Also, we had a static counter aimed at telling us how many barriers exist in generated code, as opposed to how many are executed. This counter was not functional since the compiler isn't aware of counters at the moment. Let's just remove it to avoid confusion. Change-Id: I6b173ab858c8984ef03ede225afdc999ba82b5c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1524483Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#60673}
-
Peter Marshall authored
Remove unused includes and add includes that were indirect. Remove UnboundQueue which was not used anywhere. Change-Id: If47faac45fc9c16a27453ecabed927ea00df3045 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557136 Auto-Submit: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Michael Achenbach authored
The test is so slow that it might have caused the test driver to hang after the normal hard timeout. TBR=sergiyb@chromium.org NOTRY=true Bug: v8:9098 Change-Id: I28ad1551f66fab989494d7a3b015d661c5ab6efb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557142Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/9baa370..7db6cfc TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I11f6f1b06a50204af8a01c22324a187536697e6f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557341Reviewed-by:
-
- 07 Apr, 2019 2 commits
-
-
Michael Achenbach authored
TBR=tmrts@chromium.org NOTRY=true Bug: v8:9098 Change-Id: I69d9cd21ad70357a77b45e97393949f1cfbab529 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557137Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/25794eb..9baa370 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/78cdfa0..979fc35 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/9198ef8..0b62ed7 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Iadb495d5260033a5afef74dcbe4704f526ade325 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1556580Reviewed-by:
-
- 06 Apr, 2019 2 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/96d2ee3..25794eb Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/63e0762..78cdfa0 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/b8268ca..9198ef8 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/25ef1f6..f822215 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ie655b9676aec2df3d2226c73ad7e36fcca13ebaf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1556574Reviewed-by:
-
Deepti Gandluri authored
Change-Id: Ic00f8e0ac9ef621354b74ffa7c83a84301c46222 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1555435Reviewed-by:
Ben Smith <binji@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#60666}
-
- 05 Apr, 2019 11 commits
-
-
Pierre Langlois authored
The --trace-gc-verbose flag was mistakenly reporting the generic LO space size in place of the *code* LO space size. Change-Id: Iddb83b540b0e0a201aa358649d91ef606721e0be Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554693 Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Reviewed-by:
-
Ben Smith authored
This is a reland of 63608968 The previous CL failed on Windows, but it was a general bug. The dropped_elem_segments was not being set on the instance properly in cctests, so`table.init` instructions would fail by reading uninitialized data. I took this opportunity to also add an implementation of `elem.drop` in the interpreter, and ported the JS tests for those too. Original change's description: > [wasm] Implement table.init for interpreter > > This also fixes CheckCallViaJS when a trap occurs. In that case, the > trap callback is called instead of an exception being thrown, so if it > isn't handled, a bogus result will be returned instead. > > Bug: v8:8965 > Change-Id: I560e89f353756df23c062fb8c9484d9971c19253 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539078 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Ben Smith <binji@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60473} Bug: v8:8965 Change-Id: Ia547d9530b7ca67fde5bd94539f49153b796e82d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547142 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by:
-
Sergiy Belozorov authored
Testing V8 CQ after https://crrev.com/i/1139317 and https://crrev.com/i/1141184, which are changing how host_class dimension is computed and set and how xenial bots are provisioned. TBR=tandrii@chromium.org, machenbach@chromium.org No-Tree-Checks: true Change-Id: Id7fcda589764b7048f19df97b3bea6e2ad7c97be Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554694 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#60663}
-
Frank Tang authored
Bug: v8:9040 Change-Id: Ie1c5ab982aef844c704dba5bb9a0e945ce220545 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549435Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#60662}
-
Vadim Gorbachev authored
use '!=' instead of 'is not' with str FileNotFoundError isn't exist in python2.7, use IOError instead. Bug: chromium:948812 Change-Id: I241ff8a9321d612f2371a2a2e2deae948fa180e5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549168 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
-
Vadim Gorbachev authored
For details see: https://python-future.org/compatible_idioms.html#file Bug: chromium:948824 Change-Id: Ib06568963073621bd8edf2c8edb89bf8253d3bcb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549169Reviewed-by:
-
Simon Zünd authored
As part of one of the stack trace refactorings, this field moved from StackFrameInfo to the StackTraceFrame class, but was not properly removed. R=petermarshall@chromium.org Bug: v8:8742 Change-Id: I18b9bd7650eed0f5bdb0823da9fdefb6afa3491e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550800Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#60659}
-
Michael Starzinger authored
This makes sure that the implicit operand stack slot used for passing an exception from the throw-site to the catch-site is counted against the maximum stack height. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-rethrow-interpreter BUG=v8:8091 Change-Id: I7e8f47ba4662eb273792e7508207f67588264a2f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554683 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Georg Neis authored
Bug: v8:9087 Change-Id: Ibc21d7e5619e4e6a0edc98cb0bd12e67ab2f6643 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554690Reviewed-by:
-
Michael Achenbach authored
For standard test failures, the variant name is enough to deduce the full command line of the test. This is used to create the flako command line on the infra side. Test failures from numfuzz have additional variant_flags, calculated by the fuzzer, which don't match a variant name. Exposing those in the test results will enable printing a proper flako command line on infra side for numfuzz cases. Bug: v8:8971 Change-Id: Ie47d42a0b34037da458b474f2a9ab38f1a5d238a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554689Reviewed-by:
-
Michael Starzinger authored
R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-simd-interpreter BUG=v8:8091 Change-Id: Id0b5da98bbfb91c7a5a878681d7fffe81233284f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552794 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
