- 14 Dec, 2021 20 commits
-
-
Camillo Bruni authored
Multiple threads can modify async_wraps_ in parallel, which is not ok. Drive-by-fix: - Use normal constructor/destructor for AsyncHooksWrap - Use unique_ptr for storing AsyncHooksWrap Bug: chromium:1278276 Change-Id: I667980151c775be29e603790e589b1de76fae05a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338257Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Auto-Submit: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78375}
-
Benedikt Meurer authored
This decouples the stack trace visitation logic from the creation of actual stack frame objects, in preparation to introduce a second kind of stack frame object (`v8::internal::StackFrameInfo` as part of http://crrev.com/c/3302794) in addition to the existing `v8::internal::CallSiteInfo`. Doc: https://bit.ly/v8-stack-frame Bug: chromium:1258599, chromium:1278647, chromium:1278650 Change-Id: I398933653e29cc2fe5c222526d9dd686ef8239b4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3334781 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#78374}
-
Nico Hartmann authored
This reverts commit 69564827. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Clusterfuzz%20Linux%20MSAN%20no%20origins/25955/overview Original change's description: > [counters] Improve v8.execute histogram timer > > - Mark uncommon timer-paths as V8_NOINLINE > - Add explicit LongTaskNestedTimedHistogramScope class > - Use explicit LongTaskRecordMode enum > - Mark a few more isolate methods as const > - Add more timer scopes: > - Accessors::ArrayLengthSetter > - v8::NewContext > > Bug: v8:12498, chromium:1275056 > Change-Id: I7896ee341c3c3a1fd5acf8f3f59347ff01dda9c0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338258 > Reviewed-by: Marja Hölttä <marja@chromium.org> > Auto-Submit: Camillo Bruni <cbruni@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78372} Bug: v8:12498, chromium:1275056 Change-Id: I0147c57085f114201e1d5fa293282d38c81d0148 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338699 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#78373}
-
Camillo Bruni authored
- Mark uncommon timer-paths as V8_NOINLINE - Add explicit LongTaskNestedTimedHistogramScope class - Use explicit LongTaskRecordMode enum - Mark a few more isolate methods as const - Add more timer scopes: - Accessors::ArrayLengthSetter - v8::NewContext Bug: v8:12498, chromium:1275056 Change-Id: I7896ee341c3c3a1fd5acf8f3f59347ff01dda9c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338258Reviewed-by:
-
Andreas Haas authored
R=jkummerow@chromium.org Bug: v8:12281 Change-Id: If00f34053bb970a71a1826010050b79557dbb381 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338259Reviewed-by:
-
Seth Brenith authored
We probably expect a binary-search switch to take log(n) time in all cases, but there is currently a possibility of that expectation being broken. I'm not aware of any place where this actually happens, but if the default handler immediately follows the switch dispatch block in assembly order, then unconditional jump instructions for that handler would be omitted. This omission could cause linear execution time, where every case is checked before falling through to the default handler. This change introduces a new function to emit an unconditional jump instruction regardless of whether the target is the following block, and uses that new function when generating a binary-search switch to ensure consistently log(n) behavior. Change-Id: I5cab86fd66386762519035410e3b532dc6fd764c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3335222Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/main@{#78370}
-
Andreas Haas authored
With dynamic tiering, the "serialize" function provided by the c-api does not work anymore, and it is unclear how it should work. R=jkummerow@chromium.org Bug: v8:12281 Change-Id: Ib70bf118ba42b0752eb5dab5f43893da0404931e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338657Reviewed-by:
-
Manos Koukoutos authored
An asm-js module has all wasm feature flags disabled, despite the global flag configuration. Therefore, in WasmExportedFunction::New, we should retrieve the enabled features from the NativeModule instead of the flags. Bug: chromium:1279151 Change-Id: Ic44fe535baa7cb851644457cce533c24d4c9824e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338256Reviewed-by:
-
Igor Sheludko authored
This CL * migrates FeedbackVector::optimized_code to CodeT, * migrates OSROptimizedCodeCache to CodeT. Bug: v8:11880 Change-Id: I2082412fb9fdf90e7ed90f4454ecf55f4f3d53d8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330468Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Benedikt Meurer authored
This is a non-functional refactoring to make naming of stack traces more consistent, and thus easier to reason about whether the "simple stack trace" (stack trace API) or the "detailed stack trace" (inspector API) is meant. Granted, these names aren't great by themselves, but at least we should be consistent. This also adds a new `Isolate::GetSimpleStackTrace()` and uses that directly to implement the Wasm C-API, avoiding the roundtrip via the `JSMessageObject`, which actually carries a detailed stack trace (which by chance worked out so far). Doc: https://bit.ly/v8-stack-frame Bug: chromium:1258599, chromium:1278647, chromium:1278650 Change-Id: I29e1a956ed156d6eeceb50150a28afaa2f11b9c7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3334780 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/main@{#78366}
-
Igor Sheludko authored
This CL migrates JSFunction's code accessors to CodeT. Bug: v8:11880 Change-Id: I8cf367eb79cc1d59548dd4f3e18c010f76f101cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330466Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Leszek Swirski authored
Fixed: chromium:1279383 Change-Id: I0fb6e15d47698b90c51cc27e18a526ba6d0fc1d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338656 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Corentin Pescheloche authored
EmbedderState is forward declared in public header for EmbedderStateScope. Default std::unique_ptr's destructor needs a fully defined class. Defining default destructor in implementation file fixes this. Bug: chromium:1263871 Change-Id: I8ccc58f56a758927dc5d7a39387188185e7d3827 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3338697 Auto-Submit: Corentin Pescheloche <cpescheloche@fb.com> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78363}
-
Camillo Bruni authored
Use build_flags_ with @if/@ifnot in torque for the following flags: - V8_ENABLE_JAVASCRIPT_PROMISE_HOOKS - V8_ENABLE_SWISS_NAME_DICTIONARY - Make sure Torque and CSA code actually respect V8_ENABLE_JAVASCRIPT_PROMISE_HOOKS. - Rename V8_ALLOW_JAVASCRIPT_IN_PROMISE_HOOKS to V8_ENABLE_JAVASCRIPT_PROMISE_HOOKS - Rename gn/bazel arg v8_allow_javascript_in_promise_hooks to v8_enable_javascript_promise_hooks - Unship context promise hooks in chrome and enable them only in d8 for testing purposes - Make sure d8 and the API throw when using promise hooks without the compile time feature enabled Bug: chromium:1265186, v8:11025 Change-Id: I69834d44d683a36d0d7be3c3d68888321be0fd7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3301474Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78362}
-
Benedikt Meurer authored
This is the second step in the refactoring to make v8::StackFrame more lightweight and usable for (long time storage) by the V8 inspector (see https://bit.ly/v8-stack-frame for an overview). This is a purely mechanical change without any functional aspects. The intention is to make the use case for the CallSiteInfo objects clear, namely to serve as the backing store for the CallSite objects exposed via the Error.prepareStackTrace() API and used under the hood to implement the error.stack accessor. Doc: https://bit.ly/v8-stack-frame Bug: chromium:1258599, chromium:1278647, chromium:1278650 Change-Id: I39dffd1f1a8e5158ddc56f2a0a2b1b28321f487a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3300138Reviewed-by:
Simon Zünd <szuend@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#78361}
-
Igor Sheludko authored
Drive-by: fix TSAN issue. Bug: v8:11880 Change-Id: I8a31391c6a1855a20a243eb740e4e3e1223ecbbf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3333930Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/icu: https://chromium.googlesource.com/chromium/deps/icu/+log/edf883a..fbc6faf Add display names for languages and regions for Android (Frank Tang) https://chromium.googlesource.com/chromium/deps/icu/+/fbc6faf Update OWNERS (Maksim Ivanov) https://chromium.googlesource.com/chromium/deps/icu/+/fe915d8 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,ftang@chromium.org Change-Id: I02a5e611d648dc2393e96f2b108e15121eee210d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3336700 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78359}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/47daaa3..864a567 Rolling v8/buildtools/linux64: git_revision:fc295f3ac7ca4fe7acc6cb5fb052d22909ef3a8f..git_revision:2e56c317bd8e2bf152cfa2ead6ac5fa476fe28b4 Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/58799ca..603d9d1 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/45fc896..1ba82f6 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/ecc14aa..2777fd9 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/7fd4168..dc7eff9 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ic4bdb58338f40da8a26572d54ba949d27777a973 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3336699 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78358}
-
Aleksei Koziatinskii authored
Some embedders might want to process console.info and console.log differently. So inspector needs to return a different level for these console log messages. Change-Id: I936990a25f079a0d72f877a5095ed93819fc539a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3331929Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Alexey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/main@{#78357}
-
Lu Yahan authored
Change-Id: I53234b6494887edd2b18e5d6b7d07675414d2e68 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3329802Reviewed-by:
ji qiu <qiuji@iscas.ac.cn> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#78356}
-
- 13 Dec, 2021 10 commits
-
-
Alexander Schulze authored
Bug: chromium:1279426 Change-Id: Ia510b105a4aacbca3abc521b110bcf58cfe6e294 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3335816 Auto-Submit: Alexander Schulze <alexschulze@chromium.org> Reviewed-by:
-
Piotr Sikora authored
Signed-off-by:
Piotr Sikora <piotrsikora@google.com> Change-Id: Iee9005f1dd934fc6b81c1a8eb3d8d6bfb21b4bdc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3334336Reviewed-by:
-
Tim van der Lippe authored
We recently ran into two separate issues with this DCHECK. To enhance debugging, let's add some more information as to which property is failing. That should make investigating of the problematic property easier, as we now no longer need to printf the results. R=jkummerow@chromium.org Bug: chromium:1276617, chromium:1262066 Change-Id: I8613780fc9613af700e113bb6050d4cbbd4cb040 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330467 Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org> Reviewed-by:
-
Nico Weber authored
No behavior change. Bug: chromium:1278777 Change-Id: I18deed9571acb9f953cb6cddee12e27733de98b5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3332197 Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
-
Manos Koukoutos authored
Since the reftypes proposal has shipped, we remove the respective flag and the code that handled its absence. We maintain a WasmFeature for reftypes for feature detection purposes. We remove the flag declaration from tests, and adapt some tests that make no sense without the flag. Bug: v8:7581 Change-Id: Icf2f8d0feae8f30ec68d5560f1e7ee5959481483 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3329781Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78351}
-
Milad Fa authored
Support was added to big endian machines (PPC/AIX and S390) using the following CLs: TurboFan fixes: https://crrev.com/c/3313444 https://crrev.com/c/3327721 Wasm Compiler fix: https://crrev.com/c/3316032 cctest: https://crrev.com/c/3302852 Change-Id: Ie20dcbe37d04b20d15aae724a82a204bd12baa2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3329795Reviewed-by:
-
Patrick Thier authored
This is a reland of 863bc2b8 Diff to original: - Don't eliminate GC observable stores that were temporarily unobservable during traversal. - Skip the previously added test for single-generation - Add new test Original change's description: > [turbofan] Improve StoreStoreElimination > > Previously, StoreStoreElimination handled allocations as > "can observe anything". This is pretty conservative and prohibits > elimination of repeated double stores to the same field. > With this CL allocations are changed to "observes initializing or > transitioning stores". > This way it is guaranteed that initializing stores to a freshly created > object or stores that are part of a map transition are not eliminated > before allocations (that can trigger GC), but allows elimination of > non-initializing, non-transitioning, unobservable stores in the > presence of allocations. > > Bug: v8:12200 > Change-Id: Ie1419696b9c8cb7c39aecf38d9f08102177b2c0f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3295449 > Commit-Queue: Patrick Thier <pthier@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Reviewed-by: Maya Lekova <mslekova@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78230} Bug: v8:12200, chromium:1276923, v8:12477 Change-Id: Ied45ee28ac12b370f7b232d2d338f93e10fea6b4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3320460Reviewed-by:
-
Leszek Swirski authored
This is a reland of 2418d22a Reland fixes: * Rebase this 2+ year old change
😱 * Unpoison the kept segment before zapping it to make ASAN happy. * Carefully adjust allocation size tracking fields to compensate for kept segment. Original change's description: > [zone] Keep one page when we Zone::Reset for reuse > > Change-Id: I50c6124d3da5b35d4156c066f38d10d2dc966567 > Reviewed-on: https://chromium-review.googlesource.com/c/1349246 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57793} Change-Id: Iaffde5b38b3d683af081b1878464dd4c66be5af8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3322833Reviewed-by: -
Benedikt Meurer authored
This CL overrides the Summarize() method on the BuiltinExitFrame, similar to what is already implemented on UnoptimizedFrame. This way the stack trace capturing logic can be unified further, and only needs to distinguish between JavaScript(ish) and WebAssembly frames now. Bug: chromium:1258599, chromium:1278650, chromium:1278647 Change-Id: I15f4dd61199ff047930796ce285bd938e8bcd22f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3327142 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/dda89a8..47daaa3 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I67a741acaa598961fee60c788f202cf23c3e3f0a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330906 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78346}
-
- 12 Dec, 2021 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/10669fa..dda89a8 Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/d520ea5..58799ca Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/70bcf59..45fc896 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/58c7c38..ecc14aa R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I1168840eaadcc74c3a0845192669ad5c4a523361 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330905 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78345}
-
- 11 Dec, 2021 2 commits
-
-
Igor Sheludko authored
Bug: v8:11880 Change-Id: Ifcbf73a68c68b2534bb0c7272be43269b0963507 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3329799 Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/312246f..10669fa Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/d16203a..70bcf59 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/ed8451a..7fd4168 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I636d923bae0d44bdc02e4b3e94a8450cff867a9c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3330904 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78343}
-
- 10 Dec, 2021 7 commits
-
-
Milad Fa authored
Port df748fc0 R=georgia.kouveli@arm.com, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I3ae962a6c6f20c945c788e9ff512a3b02aff4754 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3331275Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78342}
-
Andreas Haas authored
With a recent addition to the type reflection proposal, 'anyfunc' gets renamed to 'funcref'. For backwards compatibility, 'anyfunc' becomes an alias for 'funcref'. With this CL, the string 'funcref' can be used to create a funcref table or a funcref global. Additionally, 'funcref' is returned as the type of imported and exported functions as well as globals and tables. R=manoskouk@chromium.org Change-Id: If3ed4d507de862ebfcabd4eb967bbfaae1c6ccba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3300135Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#78341}
-
Milad Fa authored
Fix is applied to some of halfword signed ops. Change-Id: Idad3cfe9b66d39cb991974c959d447e5c4eccad3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3327722Reviewed-by:
-
Milad Fa authored
Currently atomic ops on TF are using machine native byte order and cannot be used by Wasm calls. This Cl adds support for Little Endian enforced Wasm atomic ops to PPC/AIX by reversing bytes where needed. Change-Id: I4080f318022eedd2058e51d09595753eab385441 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3327721Reviewed-by:
Vasili Skurydzin <vasili.skurydzin@ibm.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78339}
-
Leszek Swirski authored
This allows us to reuse AstValueFactory's string table across multiple parsers, while still releasing memory after each individual parse. This is mild overkill for all the single parses that don't reuse AstValueFactories, but there at least the AstRawStrings now end up grouped together in memory, so that might have mild cache benefits. Change-Id: I0b378760b601fa4ec6559a0dca5d7ed6f895e992 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3322764Reviewed-by:
-
Leszek Swirski authored
Bug: chromium:1278387 Change-Id: If834ee2f9ba3663822a8066fbd1ece49c24023da Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3329790 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
To make sure that Wasm memories don't exceed JSArrayBuffer size. This change shouldn't affect real-world modules, because finding enough contiguous address space to allocate that much memory is virtually impossible anyway. Fixed: chromium:1242339 Change-Id: I68873796b9afb798cb1a64e5e1acc495cf509159 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3328783 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
