- 26 Sep, 2019 3 commits
-
-
Jakob Gruber authored
It looks like codegen on ia32 may sometimes miss a byte during emit_arith. Our working theory is that this happens because `length` in emit_operand, for whatever reason, is 0 and we thus do not advance `pc_` correctly. The tentative fix is to use EMIT to increment the pc_ on each single write instead of relying on `length`. Bug: v8:9774 Change-Id: I522eef96481f44f57628f914c9c170f1644ec47a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1824941 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#63978}
-
Clemens Backes [né Hammacher] authored
This reverts commit 253fddc6. Reason for revert: Still fails on android builders: https://ci.chromium.org/p/v8/builders/ci/V8%20Android%20Arm%20-%20builder/28305 Original change's description: > Update V8 DEPS. > > Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7f88e8b..c9a62d3 > > Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/6bb5733..e00ffeb > > Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/7211cf6..f0faf48 > > Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/d0c91c0..925d2e5 > > TBR=machenbach@chromium.org,tmrts@chromium.org > > Change-Id: I7a74868be617b958054f1387f6ca3f15ad3ab079 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1826260 > Reviewed-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@{#63976} TBR=machenbach@chromium.org,v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com,tmrts@chromium.org Change-Id: I94d44623846a3f39e629e77e25b26d62b92ba84b No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1825240Reviewed-by:
Clemens Backes [né Hammacher] <clemensb@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#63977}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7f88e8b..c9a62d3 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/6bb5733..e00ffeb Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/7211cf6..f0faf48 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/d0c91c0..925d2e5 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I7a74868be617b958054f1387f6ca3f15ad3ab079 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1826260Reviewed-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@{#63976}
-
- 25 Sep, 2019 20 commits
-
-
Ng Zhi An authored
A lot of the instructions in RO_OP_LIST do not require temp registers in the codegen, but a temp register is emitted. We split RO_OP_LIST into two lists, one which requires temp registers RO_OP_LIST_ONE_TEMP, and RO_OP_LIST is now for instructions that do not use temp registers. There are a couple more instructions currently in RO_OP_LIST, but use scratch registers in the codegen, those can be cleaned up to use temp registers and then moved into RO_OP_LIST_ONE_TEMP. Change-Id: Iccc49111c1cce05324c64c36458f49920231d6bf Bug: v8:9396 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1819870 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#63975}
-
Z Nguyen-Huu authored
Bug: v8:8976 Change-Id: Ibe20feb63b676f76b21dd8be7a9d1f3887af470a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1816926 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#63974}
-
Ng Zhi An authored
FMA operations is always supported on arm64, so in the test, we expect fused results on arm64 whenever we run on TurboFan. Bug: v8:9415 Change-Id: Ia2016533b9b76ee14b8c8da1c0d4ff7753276714 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1819723 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
Frank Tang authored
It is controlled by flag harmony_intl_other_calendars. But this is also pretty intern-dependent with harmony_intl_add_calendar_numbering_system and should be launched all together to be meaningful. https://github.com/tc39/ecma402/pull/349/ #349 Normative: Allow calendar to determine choice of pattern https://github.com/tc39/ecma402/pull/351 #351 Normative: Permit relatedYear and yearName in output Bug: v8:9155 Change-Id: I67cd6bba6276bbb995186a9fe6202429d724ba61 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1588401Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#63972}
-
Dominik Inführ authored
Since https://crrev.com/c/1771783 the mutator owns the old-to-new remembered set, while the sweeper modifies the sweeping-slot-set. This allows us to update the old-to-new remembered set non-atomically. In this CL the mutator now inserts non-atomically into the remembered set. The AccessMode is now explicit for Insert-operations as well. Bug: v8:9454 Change-Id: I94730345f7dd34fe309839969330687c94b3080b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1803652 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#63971}
-
Milad Farazmand authored
Port 12a9ee3a Original Commit Message: 32 bit Smis are incompatible with pointer compression so we land disable them before enabling pointer compression in order to separate memory and performance regressions caused by 31 bit Smis from pointer compression change. R=ishell@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I5d180c6435796284224a45053ff44e7a25fa6e2a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822118Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#63970}
-
Ingvar Stepanyan authored
This addition will allow to experiment with parsing DWARF information from WebAssembly on the frontend side for improved debugging. The frontend must explicitly opt-in to this experiment by setting `supportsWasmDwarf: true` in `Debugger.enable` params. When this option is present, and Wasm appears to contain DWARF information (heuristic: `.debug_info` custom section is present), V8 will not try to disassemble and report each WebAssembly function as a separate fake script, but instead will report Wasm module as a whole. Note that V8 already does this when Wasm is associated with a source map. Additionally, this CL adds a dedicated `Debugger.getWasmBytecode` command that accepts scriptId and returns raw wire bytes of the chosen WebAssembly module. Change-Id: I7a6e80daf8d91ffaaba04fa15688f2ba9552870f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1809375 Commit-Queue: Ingvar Stepanyan <rreverser@google.com> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Peter Marshall authored
This was missed in a file move Bug: chromium:991547 Change-Id: I4442f2e4e7acdb91b16151714b87e229bce1a409 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1824945 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#63968}
-
Clemens Hammacher authored
This flips the --wasm-far-jump-table flag. It will allow for more than 128MB of code space per wasm module on arm64, and will increase the limit on the number of modules per process on x64 (was ~1000 before, because we reserved 1GB for the code space per module). R=mstarzinger@chromium.org Bug: v8:9477 Change-Id: I870ec616f4812e38ef1e3fccf0629854a247bb4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815247Reviewed-by:
-
Ross McIlroy authored
Seperates the memory lowering operations into a seperate MemoryLowering class which is used by the MemoryOptimizer. This will enable TurboProp to reduce memory operations without having to do a full memory optimization pass. BUG=v8:9684 Change-Id: I1b333f1360fd342612672842bf879f44ab1ee60c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815243Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#63966}
-
Thibaud Michaud authored
Allows JS functions returning array-like objects to be imported as multi-return functions in WebAssembly modules. Importing a generator does not work as required by the specification yet. R=mstarzinger@chromium.org Bug: v8:9492 Change-Id: Iaf61a0f718eb50676913aa1486fb39cebecfc090 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815246 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
-
Dominik Inführ authored
The previous CL https://crrev.com/c/1771783 introduced the old-to-new invalidation set, while still manually deleting slots in the remembered set. This CL only clears slots during sweeping when shrinking objects. The invalidation set is now used to filter slots in scavenge and mark-compact. Bug: v8:9454 Change-Id: I3a4c562d29cce0eddd9884e5f6fc1a09d1b5cd5e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1807275 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Yu Yin authored
when wasm have multiple returns but not aligned such as return {kWasmI32, kWasmI64, kWasmI64, kWasmI32 } like test/wasm-api-tests/multi-return.cc do, wasm compiler will generate store instructions but not unaligned store instructions to store the return values, this will cause check failed on mips simulator, the test maybe will successful on mips native machine if the host kernel can handle the unaligend stores. This patch also fix the return address offset. Change-Id: I7de93fdbef3341e7d0057f6ecbc95a9d2f86c943 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1824309 Commit-Queue: Clemens Backes [né Hammacher] <clemensh@chromium.org> Reviewed-by:Clemens Backes [né Hammacher] <clemensh@chromium.org> Reviewed-by:
-
Dan Elphick authored
In preparation for Code objects that aren't executable and can be in RO_SPACE, pass an Isolate into Code::Disassemble. Bug: v8:7464 Change-Id: I99f5faf23dd4709a48925e1ae44d1ce595ea6f5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822043Reviewed-by:
-
Clemens Hammacher authored
With the far jump table, we need to distinguish the maximum size of a single code space from the maximum total code size per module. On arm64, they differ, because we now support 1GB of code space, but each code space is still limited to 128MB. Bug: v8:9477 R=mstarzinger@chromium.org Change-Id: I7b9aaec56a1d9d1f70573b6b895216d5b3f38346 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815253 Commit-Queue: Clemens Backes [né Hammacher] <clemensh@chromium.org> Reviewed-by:
-
Yu Yin authored
Port 12a9ee3a Original Commit Message: 32 bit Smis are incompatible with pointer compression so we land disable them before enabling pointer compression in order to separate memory and performance regressions caused by 31 bit Smis from pointer compression change. Change-Id: I19647f18e7feafc6ca5b922c73785839ab528421 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1824306Reviewed-by:
-
Dan Elphick authored
Moves the following functions from CodeStubAssembler to BuiltinsStringAssembler: SubString CopyStringCharacters AllocAndCopyStringCharacters Bug: v8:9396 Change-Id: Ieb534b7fa7e72db9b05cdc2a34bd88b7a52ee985 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822040Reviewed-by:
-
Dan Elphick authored
Move CodeStubAssembler::FindOrderedHashTableEntry into CollectionsBuiltinsAssembler and remove the specializations since they can now be generated directly by the call sites. Bug: v8:9396 Change-Id: I23e84167dafc2fec1886a842a8649f0500c4f447 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822041 Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Dan Elphick authored
Last use of BasicStoreNumberDictionaryElement was removed in https://chromium-review.googlesource.com/c/v8/v8/+/1627977 Bug: v8:9396 Change-Id: I08c1da67393c3549a8c756abd2a5ca4e35fa3b2a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822042 Auto-Submit: Dan Elphick <delphick@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/04fbb76..7f88e8b Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/8669b37..6bb5733 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/ba5bc99..7211cf6 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/e514199..d0c91c0 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I8139c9c1b3d322cf0cc5d49d190a20d55ff35a4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1823582Reviewed-by:
-
- 24 Sep, 2019 17 commits
-
-
Ng Zhi An authored
Bug: v8:9728 Change-Id: I8d993368fc23ab9e8cc08e31f4405678ec4ce824 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1803790Reviewed-by:
-
Ng Zhi An authored
This gives nicer error messages. Was Fatal error in ../../src/compiler/backend/instruction.h, line 778 Debug check failed: i < InputCount(). Now Fatal error in ../../src/compiler/backend/instruction.h, line 778 Debug check failed: i < InputCount() (5 vs. 3). Bug: v8:9396 Change-Id: Iab2aea49245a42397bf07f4abf9e3de501c758b9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1817258Reviewed-by:
-
Andreas Haas authored
This CL fixes a memory leak in the interpreter. The leak was caused by a cycle the object graph that was rooted with a global object. The cycle was the following: A global handle, owned by the interpreter -> reference stack of the Interpreter -> ref.func element (WasmExportedFunction) -> WasmInstanceObject -> WasmDebugInfo -> InterpreterHandle -> Interpreter With this CL we get rid of the global handle. Instead we store the stack in the WasmDebugInfo. We then have to load the reference stack every time we enter the Interpreter and want access the reference stack. R=mstarzinger@chromium.org Bug: chromium:1000610 Change-Id: If8995725f7ec35862b2f99a07582c861027daaf1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1800582 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
We are going to change again Tagged to not mean 'Full Tagged'. Then, we have to reintroduce this operator, which was removed in https://chromium-review.googlesource.com/c/v8/v8/+/1594439. Bug: v8:7703 Change-Id: I8df65b76eed67613297b04d67c791cb6580bb49e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1817613 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Milad Farazmand authored
Port 12a9ee3a Original Commit Message: 32 bit Smis are incompatible with pointer compression so we land disable them before enabling pointer compression in order to separate memory and performance regressions caused by 31 bit Smis from pointer compression change. R=ishell@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I1a353f2d6a682ba27e579a7de1bf7ea2240a6bbd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822117Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Reviewed-by:
-
Georg Neis authored
R=mslekova@chromium.org Bug: v8:7790 Change-Id: Ie6cc694ac3d11bdd454c2f6d23e24b4fdd59b00e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1822039Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#63950}
-
Santiago Aboy Solanes authored
We are going to change again Tagged to not mean 'Full Tagged'. Then, we have to reintroduce these operators. These allow to write a tagged uncompressed pointer even if pointer compression is enabled. This CL is basically a revert of https://chromium-review.googlesource.com/c/v8/v8/+/1593301. Bug: v8:7703 Change-Id: Ic1c66690b6bc74f697c9f5bf6d3ff45bb764c268 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1817612Reviewed-by:
-
Jakob Gruber authored
This extends suppressions to also handle excess zone allocations in the parser. Bug: chromium:1002510 Change-Id: Id418564d244ed618703e62260de31a6b1a2842f8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1821459 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#63948}
-
Dan Elphick authored
Always unmark arrowhead parameters as assigned directly after their initialization as the parser doesn't know when it first sees the "assignment" that it may be in an arrowhead. Bug: chromium:1003403, v8:8510 Change-Id: Iad5a4136d5ec06331fc43b81a809fd72cee2dd65 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815131 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#63947}
-
Joshua Litt authored
Adds support for parsing top level await to V8, as well as many tests. This is the final cl in the series to add support for top level await to v8. Spec is here: https://tc39.es/proposal-top-level-await/#sec-execute-async-module Bug: v8:9344 Change-Id: Ie8f17ad8c7c60d1f6996d134ae154416cc1f31e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703878Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Joshua Litt <joshualitt@chromium.org> Cr-Commit-Position: refs/heads/master@{#63946}
-
Jakob Gruber authored
This introduces a limit for the interpreter's BacktrackStack to match the limit used by generated code (RegExpStack::kMaximumStackSize). Bug: chromium:1006670 Change-Id: I0b7613698e61257aecca89535ad9109c7e454692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1821458 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#63945}
-
Michael Starzinger authored
This reduces the number of label indices accepted by {br_table} from the full function body size to specifically 65520 labels. Note that TurboFan already had a similar limitation on switches, but caused a crash during compilation up until now. This change just makes the limit explicit and avoids the crash during compilation. R=clemensh@chromium.org TEST=mjsunit/regress/wasm/regress-9759 BUG=v8:9759 Change-Id: I3a9a4406b19a7f98fc36707b3b946be846170a15 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1821457 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: -
Matheus Marchini authored
Also report code relocation events through the public CodeEventHandler API, so that embedders can expose this information to external profilers, allowing those profilers to correctly translate function names even after they were relocated. R=bmeurer@chromium.org, jgruber@chromium.org, yangguo@chromium.org Change-Id: I8795186f5f5c58ede9054e4b83e2d290d92b6e00 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1802657Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
In the {Fixed} variant, the {WasmCodeManagerTest} always reserves 1GB of memory. This makes the test run OOM on many 32-bit platforms. Instead of skipping it selectively, this CL just removes the whole test. It caused a lot of trouble in the past, and needs two test-only methods in the WasmCodeManager. Also, the {Fixed} variant will not be needed any more with the wasm far jump table, since modules can always grow then. Drive-by: Clean up the unittests status file a bit. R=mstarzinger@chromium.org Bug: v8:9477 Change-Id: I5b6f8ed9f800863575c69d49d5df82f21fd23030 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815251Reviewed-by: -
Ulan Degenbaev authored
If a BackingStore is marked as !free_on_destruct, then we don't have to guarantee that there is only one such BackingStore pointing to the underlying buffer. So we can skip costly registration in process-global table of backing stores. Bug: v8:9380,chromium:1002693 Change-Id: Iad1ec5c4811d6c52a9a9d78dd700acf69170db60 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815136 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Igor Sheludko authored
This is a reland of 12a9ee3a Fixed arm64 disasm test. Original change's description: > [ptr-compr] Switch to 31 bit Smis on 64-bit architectures > > 32 bit Smis are incompatible with pointer compression so we land disable > them before enabling pointer compression in order to separate memory and > performance regressions caused by 31 bit Smis from pointer compression > change. > > Bug: v8:9767 > Change-Id: I3d4a675df4208f808b1ba6e7816be545eae0dc24 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815249 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Igor Sheludko <ishell@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63934} Bug: v8:9767 Change-Id: Ife46a4240141dd89d841eac152032ad6ca471810 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1820939Reviewed-by:
-
Ulan Degenbaev authored
This moves the initialization to JSArrayBuffer::SetupEmpty, which is the proper bottleneck for all paths constructing array buffers. Bug: chromium:1006600,v8:9380 Change-Id: I1887cb867627d69ade20654e5bc372b1ba1ac4e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815132Reviewed-by:
-
![Clemens Backes [né Hammacher]'s avatar](https://secure.gravatar.com/avatar/474af430daf77b962004ce934be86b3d?s=72&d=identicon "Clemens Backes [né Hammacher]")
