- 17 Jul, 2019 23 commits
-
-
Yang Qin authored
Change-Id: I4a95a7508d66950db4a0032893ca0a34901b2d59 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1688559Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#62772}
-
Maya Lekova authored
Bug: v8:7790 Change-Id: If6b58ed24786e0143cb72796d16d9c56b3f76914 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706468 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#62771}
-
Ben L. Titzer authored
This CL adds more stress-tests for both shared array buffers and WebAssembly memories. Because of an existing memory leak that will be fixed in upcoming CLs, some new tests are disabled. R=mstarzinger@chromium.org BUG=v8:9380 Change-Id: I2662e3d0a764a032a0c267b2d99e3ccd1a4951d0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1697252 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#62770}
-
Ulan Degenbaev authored
This reverts commit 5c6e407d. Reason for revert: memory regression Bug: chromium:982663 Original change's description: > [heap] Spawn parallel scavenging task per page in the from space > > This makes the heuristic for computing the number of parallel tasks > in Scavenger consistent with that in Mark-Compactor. > > The patch helps mobile devices where even 1 MB new space can take > 10ms to scavenge. > > Change-Id: I979de5e8485b93808ea079af2756f53d9b720e10 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1685612 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62566} TBR=ulan@chromium.org,mlippautz@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I046ba0297807ef66abc33241d8948c934fa78028 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1697245Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#62769}
-
Tamer Tas authored
{do_raw_json} and {do_json} both read the log files to construct a dictionary of stats. This CL extracts that logic and eliminates code duplication No-Try: true Bug: v8:9448 Change-Id: I375920c25942a92cc12790ac60a4c7960cfd44b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706473 Auto-Submit: Tamer Tas <tmrts@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: -
Clemens Hammacher authored
Some architectures allow more than one code space to be reserved per module. The strategy to allocate additional spaces seems suboptimal: We allocate just enough for the one code allocation request which does not fit in the existing space. This can lead to big numbers of reservations being made. Also, for lifting the 128MB code space limit on arm64, we will allocate several code spaces also on x64 and arm64. This CL introduces a new counter to measure the number of code spaces per module, to see whether we have problems there already, and to track that metric when implementing the mentioned change. In order to update the respective counter, the {WasmCodeAllocator} now also holds a shared pointer to the counters of the original isolate. Those counters might live much longer than the isolate itself, which is no problem and can already happen before this change. R=mstarzinger@chromium.org CC=jwd@chromium.org Bug: v8:9477 Change-Id: I95e29b2d27f0414586246e2fa99d6761960a636b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704100 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: -
Dan Elphick authored
Mark a couple of constructors as explicit and use the default constructor instead of defining an empty body for PreParserSourceRange. Bug: v8:9396 Change-Id: I60f891245543852d8250105ba7b89620c15204bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706052 Auto-Submit: Dan Elphick <delphick@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#62766}
-
Jakob Gruber authored
Maps have a hard limit of 256 (non-inclusive) for the instance size in words. For the native context object, we are very close to this upper bound. This CL removes a few unused fields to give us a bit of breathing room (parts of which I will use in a follow-up CL). Bug: v8:5577 Change-Id: I096a45e47661f78f6bf23d71cbc29100e6e0592b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706055 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#62765}
-
Clemens Hammacher authored
R=ahaas@chromium.org Bug: v8:9396 Change-Id: I705f29591f86160eb899289cd1d6c7c6ad7d47ec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706051Reviewed-by:
-
Maya Lekova authored
Bug: v8:7790 Change-Id: If2a8123e5657f0ea9a007b5f1a82e9d1a91c80f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679493Reviewed-by:
-
Clemens Hammacher authored
Instantiating a JumpTableAssembler has some overhead (at least one heap allocation), so use a single JumpTableAssembler to generate the whole table, just as the lazy compile table. R=mstarzinger@chromium.org Bug: v8:9477 Change-Id: I66622909ac06e6bda9fca3e71c83d4c9d1ded500 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706054Reviewed-by:
-
Tamer Tas authored
{json} command prints the results of benchmarks after aggregating it. This makes accessing raw data for analysis, a tedious process. This CL implements {raw-json} for accessing raw results. TBR=ulan@chromium.org No-Try: true Bug: v8:9448 Change-Id: I7c00fc0eca23b8bd5c967db903f71c5b46eddea3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706059Reviewed-by:Tamer Tas <tmrts@chromium.org> Auto-Submit: Tamer Tas <tmrts@chromium.org> Commit-Queue: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#62761}
-
Sathya Gunasekaran authored
This reverts commit 21e34c71. Reason for revert: breaks TSAN https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN/27444 Original change's description: > [cleanup][test] split es6/classes.js into different tests > > es6/classes.js is large and causes timeouts and OOM on some of the > configurations. > > Bug: v8:9246 > Change-Id: Iaabfc39dd8f9554e16f67d66ce64acd3dd56b9ee > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704103 > Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> > Commit-Queue: Mythri Alle <mythria@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62758} TBR=mythria@chromium.org,gsathya@chromium.org Change-Id: I296d51ed682f51a3e6794858ab96b9407cc8ec56 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9246 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706058Reviewed-by:
-
Yu Yin authored
Port 56eaec9d https://crrev.com/c/1698393 Original Commit Message: We had both jump slots and lazy compile slots in the same table. This increases the space per slot to the maximum of the two, even though we often do not use lazy compilation and could have smaller jump slots. This CL splits the two into two separate tables. The lazy compile table will only be created on demand, and will never be patched. The jump table now only contains jumps, and is more compact (which might improve performance because of improved locality). Change-Id: I54a2985d777fd3fa30d420f5af27a3ddc79641b6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703991Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Yu Yin <xwafish@gmail.com> Cr-Commit-Position: refs/heads/master@{#62759}
-
Mythri A authored
es6/classes.js is large and causes timeouts and OOM on some of the configurations. Bug: v8:9246 Change-Id: Iaabfc39dd8f9554e16f67d66ce64acd3dd56b9ee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704103Reviewed-by:
-
Sathya Gunasekaran authored
This reverts commit d4d28b73. Reason for revert: breaks TSAN bot: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN%20-%20concurrent%20marking/9526 Original change's description: > [regexp] Call the regexp interpreter without CEntry overhead > > Previously all RegExp calls went through Runtime_RegExpExec when --regexp-interpret-all was set. > > This CL avoids the runtime overhead by calling into the interpreter directly from the RegExpExec Builtin when the regular expression subject was already compiled to ByteCode (i.e. after the first call). > > Bug: v8:8954 > Change-Id: Iae9dfcef3370b772a05b2942305335d592f6f15a > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1698391 > Commit-Queue: Patrick Thier <pthier@google.com> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62753} TBR=jgruber@chromium.org,petermarshall@chromium.org,pthier@google.com Change-Id: I3257220c4359a3b801dd80e0eff6c4534d8badee No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8954 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706050Reviewed-by:
-
Yu Yin authored
Fix build error which is introduced by 9f8d52df https://crrev.com/c/1701844 Change-Id: I31266daf46ddc67390379f935568e3443593a262 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703988Reviewed-by:
-
Michael Achenbach authored
NOTRY=true Bug: chromium:973052 Change-Id: I90699d3b7219fd554cd540f4eaff2179e35a056e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706048 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Tobias Tebbi authored
This adds a simple counter to Turbofan that's incremented throughout the compilation, hopefully frequently enough so we can use it to detect divergence and performance bugs. In addition, we assert that this counter never gets too high. That's the equivalent of a simple timeout, just more deterministic. The limitations on Turbofan input size should guarantee that we never exceed this limit. Since we probably do exceed it rarely, this check is only a DCHECK and intended to detect performance and divergence issues, but not supposed to be performed in release builds. In addition, this CL adds UMA stats to observe the real world distribution of the tick measurement. Bug: v8:9444 Change-Id: I182dac6ecac64715e3f5885ff5c7c17549351cd0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1695475 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#62754}
-
Patrick Thier authored
Previously all RegExp calls went through Runtime_RegExpExec when --regexp-interpret-all was set. This CL avoids the runtime overhead by calling into the interpreter directly from the RegExpExec Builtin when the regular expression subject was already compiled to ByteCode (i.e. after the first call). Bug: v8:8954 Change-Id: Iae9dfcef3370b772a05b2942305335d592f6f15a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1698391 Commit-Queue: Patrick Thier <pthier@google.com> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#62753}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/71a5c6e..fdb6fae Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/95c72f3..7b7a5c0 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/43959e2..96450ca Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/2c92208..9217ff8 Rolling v8/third_party/instrumented_libraries: https://chromium.googlesource.com/chromium/src/third_party/instrumented_libraries/+log/27b2da1..db728d7 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I655d538af49df4f3dbdccf21b621b9ad79739394 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704628Reviewed-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@{#62752}
-
Ng Zhi An authored
Change-Id: I99fe89a679e6a628bd6fa7600f756d9a35450243 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1695203Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#62751}
-
Ng Zhi An authored
pcmpgtq was added in https://crrev.com/c/1684362 but not to the disasembler. Bug: v8:8460 Change-Id: Id30f9ece015713e8597f5e218dc066ab75ccec96 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703766Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#62750}
-
- 16 Jul, 2019 17 commits
-
-
Tianyou Li authored
Add CPU trace mark extension for adding a magic instruction like 'cpuid' to the code stream when perform trace collection. This feature can be enabled by --expose-cputracemark-as=THE_NAME_YOU_SPECIFIED option. Change-Id: I33e94793cddf4956dbb3ddddf2f599420aa4a945 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1699749 Commit-Queue: Tianyou Li <tianyou.li@intel.com> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#62749}
-
zhiguo authored
This CL adds the support for Base64 VLQ decoding, which is the base of parsing source map files (Version 3). With this support, the mappings of C/C++ source code and WASM bytecode could be built in V8 engine. The newly-added function is called VLQBase64Decode, which accepts two character to be decoded. Upon its return, the position is updated with the next start position. The unittest of this support is also added in this CL. argument: the Base64-encoded VLQ string and the position of first Change-Id: If0f32972ecd7488844478a7b93a0f10cc38b6a5d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1657421Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Zhiguo Zhou <zhiguo.zhou@intel.com> Cr-Commit-Position: refs/heads/master@{#62748}
-
Z Nguyen-Huu authored
Bail out if name in proxy is private symbol. Also, do stack check to avoid deeply nested proxy. Spec: https://tc39.es/ecma262/#sec-reflect.get Change-Id: I0761762b074d5af892e8d7e419c87c9bbea99241 Bug: v8:8958 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682680 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#62747}
-
Dominik Inführ authored
This reverts commit dcac02ee. Reason for revert: TSAN discovered issue with cleaning invalidated slots in sweeper threads and inserting new slots in the main thread. Original change's description: > Use list of invalidated objects for old-to-new refs > > Instead of inserting "deletion" entries into the store buffer, keep > a list of invalidated objects to filter out invalid old-to-new slots. > > Bug: v8:9454 > Change-Id: Icd21d8cb2159190457f54d0f8b56742ecc820419 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1695474 > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62744} TBR=ulan@chromium.org,petermarshall@chromium.org,dinfuehr@chromium.org Change-Id: I4278e9100c76657663e0a6a62f5d86bb3a343c0e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9454 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704109Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#62746}
-
Darius Mercadier authored
In particular, some methods were public even though they should have been protected/private (FreeListCategoryType), and some other methods were declared but not defined (SearchForNodeInList). Bug: v8:9329 Change-Id: I7a1e97c82395c5907b750d89057b37b64bc0c253 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704096Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Dominik Inführ authored
Instead of inserting "deletion" entries into the store buffer, keep a list of invalidated objects to filter out invalid old-to-new slots. Bug: v8:9454 Change-Id: Icd21d8cb2159190457f54d0f8b56742ecc820419 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1695474 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
Also add the poison to x64 decompresses which were missing. Cq-Include-Trybots: luci.v8.try:v8_linux64_pointer_compression_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux64_arm64_pointer_compression_rel_ng Bug: v8:7703 Change-Id: I87fd8e56ad8132b4996749be034093566bb88301 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1700061 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#62743}
-
Simon Zünd authored
This CL changes how the start and end address for the iteration are retrieved from an std::vector that won't cause a failed assertion. There are some std::vector implementations that contain bounds checks. The string table iteration code uses an access like {&young_strings_[young_strings_.size()]} to retrieve the end address for an iteration. This results in a out of bounds exception on such a std::vector implementation even though the "element" itself is not actually accessed. Change-Id: I31db8994a7ff613897ad9deac953a1ee91f322b3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704097Reviewed-by: -
Thibaud Michaud authored
This reverts commit 117ddc8f. Reason for revert: The isolate is needed for accessing builtins, and can die during async compilation. Original change's description: > reland [wasm] Compile JS to WASM wrappers asynchronously > > The context was not set during streaming compilation. > The initial upload is the original CL and patch set 1 is the fix. > > Original CL: > > > [wasm] Compile JS to WASM wrappers asynchronously > > > > R=mstarzinger@chromium.org, ahaas@chromium.org > > > > Bug: v8:9231 > > Change-Id: I9e18073bbe25bf8c9c5f9ace102316e6209d0459 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1669699 > > Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> > > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > > Reviewed-by: Andreas Haas <ahaas@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#62672} > > R=mstarzinger@chromium.org, ahaas@chromium.org > > Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel > Bug: v8:9231 > Change-Id: I61fc11a6de54cc6e93f3600487a89fa5d2350f0e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1701850 > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> > Auto-Submit: Thibaud Michaud <thibaudm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62721} TBR=mstarzinger@chromium.org,ahaas@chromium.org,thibaudm@chromium.org Change-Id: Ie258317f04a944e8e08993dbffb524f722cceddc No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9231 Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704094Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#62741}
-
Milad Farazmand authored
Port 56eaec9d Original Commit Message: We had both jump slots and lazy compile slots in the same table. This increases the space per slot to the maximum of the two, even though we often do not use lazy compilation and could have smaller jump slots. This CL splits the two into two separate tables. The lazy compile table will only be created on demand, and will never be patched. The jump table now only contains jumps, and is more compact (which might improve performance because of improved locality). R=clemensh@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I7bece77c02f8075da54d664215989339f2958ccd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702126Reviewed-by:
-
Santiago Aboy Solanes authored
Cq-Include-Trybots: luci.v8.try:v8_linux64_pointer_compression_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux64_arm64_pointer_compression_rel_ng Bug: v8:9396 Change-Id: Ie00cb7de1b16525553baf9b555b3f84e8d86d073 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702617Reviewed-by:
-
Sigurd Schneider authored
Change-Id: I7af0fe843f73b702b03ffa50ecca19aabd7583b8 Bug: chromium:983850 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1701858 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Simon Zünd authored
On newer compilers the {operator delete} with explicit {size_t} argument would be instantiated for {WasmInstructionBuffer} and used in the destructor of {std::unique_ptr<WasmInstructionBuffer>}. The {size_t} argument is wrong though, since the pointer actually points to a {WasmInstructionBufferImpl} object. The solution is to explicitly provide a {operator delete}, preventing an implicitly generated {size_t} operator. R=clemensh@chromium.org Change-Id: I2cc22078d03a523121309bae94f5b612cb98e112 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702613Reviewed-by: -
Clemens Hammacher authored
This reverts commit ee2b5a56. Reason for revert: wasm-spec-tests\tests\conversions.js fails on win32-debug: https://ci.chromium.org/p/v8/builders/ci/V8%20Win32%20-%20debug/21210 Original change's description: > [wasm] Update spec tests > > R=clemensh@chromium.org > > Change-Id: Ia4c70327861d5025f4a09513a02bc6176e7b8f18 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702606 > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62733} TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: I16382ab16681660ef2042027ce0cb87d5b4af3ee No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702614Reviewed-by:
-
Tamer Tas authored
perfrunner returns a failure if the build timeouts at any point even if it's successful after retries. It tries to surface up the timeout issue. Due to this, some bots stay red consistently, and confuses the sheriffs. This CL masks the timeouts if the suite succeeds in the end. TBR=verwaest@chromium.org,sergiyb@chromium.org Bug: v8:9494 Change-Id: I8e107e80dfaa51095501bb2e855d9fbbe4023da9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702612Reviewed-by:
-
Ng Zhi An authored
See https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20UBSan/7102 Change-Id: I2c6577be06dbcafe11f7911cc6b3ec4b7bea5c5a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703764Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#62734}
-
Andreas Haas authored
R=clemensh@chromium.org Change-Id: Ia4c70327861d5025f4a09513a02bc6176e7b8f18 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1702606Reviewed-by:
-
