- 25 Jan, 2021 27 commits
-
-
Zhi An Ng authored
This reverts commit 5a0938e5. Reason for revert: Broke build https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8857098178780038608/+/steps/Check/0/logs/RunWasm_I32x4WidenI8x16S_liftoff/0 Original change's description: > [wasm-simd][x64] Prototype i32x4.widen_i8x16_{s,u} > > This prototypes i32x4.widen_i8x16_s and i32x4.widen_i8x16_u for x64. It > uses some masks and pshufb for the widening. These masks (3 for each > instruction) are stored as external references. > > Bug: v8:11297 > Change-Id: I6c8f55426bbb44b16ed552f393762c34c2524b55 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2617389 > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72301} TBR=neis@chromium.org,gdeepti@chromium.org,neis@google.com,ahaas@chromium.org,zhin@chromium.org Change-Id: I83aa2e86854e39ac6afd250fdc0dfac7cdd99e6d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:11297 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2648194Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#72302}
-
Ng Zhi An authored
This prototypes i32x4.widen_i8x16_s and i32x4.widen_i8x16_u for x64. It uses some masks and pshufb for the widening. These masks (3 for each instruction) are stored as external references. Bug: v8:11297 Change-Id: I6c8f55426bbb44b16ed552f393762c34c2524b55 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2617389 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#72301}
-
Ng Zhi An authored
Factor out the code sequence into macro-assembler functions to be reused by Liftoff. Bug: v8:10975 Change-Id: I82e253c94e09bf62197e7de87359d0e3956d2dcc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643662 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#72300}
-
Daniel Clark authored
The change https://chromium-review.googlesource.com/c/v8/v8/+/2572173 implemented HostGetSupportedImportAssertions [1] in a fairly literal sense, where the host supplies a list of supported import assertions and V8 filters the import assertions in a ModuleRequest and exposes only supported assertions via its API surface. However, we've decided that the interop guarantees provided by doing the filtering in V8 are probably not worth the added complexity. Thus, this change removes the filtering. Going forward, hosts will be expected to ignore unknown asserions received from V8. This is mostly a revert of https://chromium-review.googlesource.com/c/v8/v8/+/2572173, with v8::Isolate::CreateParams::supported_import_assertions being kept for now (since we first have to delete the Blink code that sets it), and a new comment in v8.h instructing hosts to ignore unknown assertions. [1] https://tc39.es/proposal-import-assertions/#sec-hostgetsupportedimportassertions Bug: v8:10958 Change-Id: I7e8e2a7fbfe2d5bf891805cff6c3160d0e6825cd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643563Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Commit-Queue: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/master@{#72299}
-
Ng Zhi An authored
If a lazy compilation happens in between 2 Wasm calls, we need to save the full Q register, since we can have live v128 values. Bug: chromium:1161555 Change-Id: I7393d6fbf5133f635a8fd62cd394323d7018f090 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2645694Reviewed-by:
-
Ng Zhi An authored
Prototype these 6 instructions on x64: - f64x2.convert_low_i32x4_s - f64x2.convert_low_i32x4_u - i32x4.trunc_sat_f64x2_s_zero - i32x4.trunc_sat_f64x2_u_zero - f32x4.demote_f64x2_zero - f64x2.promote_low_f32x4 Some of these code sequences make use of special masks, we keep them in external references. Code sequence based on suggestions at: https://github.com/WebAssembly/simd/pull/383 Bug: v8:11265 Change-Id: Ied67d7b5b6beaaccac7c179ec13504482cb9c915 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643562Reviewed-by:
-
Clemens Backes authored
For now, that flag only avoid the installation of the 'WebAssembly' global. Follow-up CLs will remove unneeded code from the binary if the gn arg is not set to true. R=ecmziegler@chromium.org, machenbach@chromium.org Bug: v8:11238, v8:11344 Change-Id: Ie95b608ed12b0476470cb552138e369f863d249b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2646833 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Emanuel Ziegler <ecmziegler@chromium.org> Cr-Commit-Position: refs/heads/master@{#72296}
-
Nico Hartmann authored
This CL makes direct heap access consistent with the serialized mode by correctly skipping optimizations if we encounter a FunctionTemplateInfo that is unknown to the broker, because we haven't seen it during serialization. Bug: chromium:1158322 Change-Id: I10ad6f307bbd5a17f27890390179bd9e2d35418c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2639958Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Reviewed-by:
-
Junliang Yan authored
This fixes an issue on 64-bit big endian architectures as discussed in https://chromium-review.googlesource.com/c/v8/v8/+/2603925, where stack slots always have the system pointer size, even with pointer compression enabled. Bug: chromium:1052746 Change-Id: I84030ba8bcde71cb1768bd7286314cf09c4dc640 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2645721Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#72294}
-
Gus Caplan authored
Bug: v8:9871 Change-Id: I4084771cfc4d34f8e1b9d5265e115f9eac1098d8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2646165Reviewed-by:
Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Ng Zhi An authored
Change-Id: Ie4b673d7f56a62528c288c4684f8cc9822277587 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2461065Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#72292}
-
Clemens Backes authored
There is no reason to allocate the vectors on the heap. Their content will be heap-allocated anyway, and they are cheap to move around. Drive-by: Remove an unused counter. R=thibaudm@chromium.org Bug: v8:11164 Change-Id: I5660ecf5db7e8915a27255bae0215d5368c7d10e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644937 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#72291}
-
Santiago Aboy Solanes authored
Also access the DescriptorArray through GetPropertyDetails concurrently if the FLAG_turbo_direct_heap_access is on. Bug: v8:7790 Change-Id: I13d12786399443ca1590dd87da7f371720acaa18 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2640421 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Dan Elphick authored
This reverts commit df5854c9. Reason for revert: The v8-gn.h header file seems to be inconsistently rebuilt sometimes causing build failures: https://bugs.chromium.org/p/v8/issues/detail?id=11341 Original change's description: > Reland "[build] Enable external flag header by default" > > This is a reland of d1da9694 > > Relanding now that fixes for perfetto and cppgc are in: > https://chromium-review.googlesource.com/c/v8/v8/+/2640458 > https://chromium-review.googlesource.com/c/v8/v8/+/2640480 > > Original change's description: > > [build] Enable external flag header by default > > > > Turns on v8_generate_external_defines_header. > > > > Bug: v8:11292 > > Change-Id: I4b1d9b47390b560b7cbf677948310694d8b03367 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2610966 > > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > > Commit-Queue: Dan Elphick <delphick@chromium.org> > > Auto-Submit: Dan Elphick <delphick@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#72201} > > Bug: v8:11292 > Change-Id: Ia47eeb6c45f4cc3db72c10782d677b69506fa3d6 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642249 > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Commit-Queue: Dan Elphick <delphick@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72226} TBR=rmcilroy@chromium.org,delphick@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:11292, v8:11341 Change-Id: I00719689e7a184e74699d074a01c10b4f462e553 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2647259Reviewed-by:
-
Clemens Backes authored
We did spawn exactly one task for each of copy&reloc and publishing. Those tasks did block until work is available. This can block background threads which could otherwise execute other component's work. Switching to the Job API allows us to easily avoid that blocking, and just respawning a task when more work is available. Is always avoid code duplication for participating in the work in the main thread. Instead we just {Join()} the existing job, which makes the current thread participate in work. For now, both Jobs set a maximum concurrency of one, so the main thread will only do work if no background thread is currently running. This can be lifted in a follow-up CL to see the performance impact of both changes independently. R=thibaudm@chromium.org Bug: v8:11164 Change-Id: I032153eb933648a750b113f5d766feb85b87070a Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_isolates_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643393Reviewed-by: -
Manos Koukoutos authored
According to the latest wasm-gc spec, the type immediate for the argument's heap type is no longer required. This CL also adds a missing check that the rtt immediate is a subtype of the argument's type. Bug: v8:7742 Change-Id: I627002d1c4bdb4ca3f2181d2f4b659ce3e95cb2d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642246 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#72287}
-
Igor Sheludko authored
This is a reland of 0ce0d934 This is a clean reland. The test failure on GC stress bot seems to be related to GC timing and --stress-flush-bytecode. Original change's description: > [classes] Make sure parent classes are never turned to setup mode > > It doesn't make sense in general and moreover an attempt to do so might > cause hard stack overflow. > > Bug: v8:11317 > Change-Id: I2a6bbadba1ebc5c1496660c734df76a13600edac > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643389 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Igor Sheludko <ishell@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72275} Tbr: verwaest@chromium.org Bug: v8:11317 Change-Id: Ic73efff7d9690c0edf7fa07b8b90691e9775a748 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642461 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#72286}
-
Michael Lippautz authored
This allows embedders to specialize MakeGarbageCollectedTrait and still get the static_asserts applied automatically, which avoids bypassing the type constraints. Bug: chromium:1056170 Change-Id: Ib24f8c6f5d8fb5ef1af4ca1af798f955fa253ba0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2647257 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#72285}
-
Clemens Backes authored
Since snapshotting returns a vector of code pointers, we should add them so the surrounding {WasmCodeRefScope}, to make sure that they are not being garbage-collected while the serializer reads them. This is unlikely to happen, since serialization is only triggered once top-tier compilation is finished, and we usually do not garbage-collect top-tier code, but in rare circumstances (e.g. in debugging), it could theoretically happen. R=ahaas@chromium.org Change-Id: Ie1a9654a8a1467c12e42181776cec1dad7366036 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644944Reviewed-by: -
Michael Lippautz authored
Bug: chromium:1056170 Change-Id: If639b12e1cceec2d27355bb4cbf8c1fefa8b5038 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642462 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Camillo Bruni authored
- Use movl which clears the upper 32bits on x64 - Use xorl + movb for Smi.ptr values <= 0xFF, saving one byte over movl Change-Id: Iacdacfbe397670667e71d1d12ef427a01994481d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642250 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Mythri A authored
Functions that get hot quickly are more likely to stay hot and stable, so optimize these functions earlier than the function that become hot slower. To measure how "soon" the function gets hot this cl introduces a global tick that is incremented whenever a function registers a tick. We use the difference in the global tick between the current tick and the last tick on that function to measure how soon the function is becoming hot. We use the last tick to account for functions that aren't used so much at the start but become hot in a later phase. Currently we use this heuristic only for Turboprop tierups. It is possible to extend this to extend this to Turbofan in future. Bug: v8:9684 Change-Id: I8ef265c03520274c68d56a9d35429531a3ba3d1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2627850 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#72281}
-
Igor Sheludko authored
This reverts commit 0ce0d934. Reason for revert: Causes failures on GC stress bots. Original change's description: > [classes] Make sure parent classes are never turned to setup mode > > It doesn't make sense in general and moreover an attempt to do so might > cause hard stack overflow. > > Bug: v8:11317 > Change-Id: I2a6bbadba1ebc5c1496660c734df76a13600edac > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643389 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Igor Sheludko <ishell@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72275} TBR=ishell@chromium.org,verwaest@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. No-Tree-Checks: true Bug: v8:11317 Change-Id: I524ce6dfee219180f36302edc94b8935c91f21dd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642458 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Shu-yu Guo authored
This reverts commit 46628795. Reason for revert: Compat breakage Bug: chromium:1170196 Original change's description: > Ship the relative indexing method `.at` > > I2S with LGTMs: > https://groups.google.com/a/chromium.org/g/blink-dev/c/I8S78w7aFmE/m/qLHAcjhRCQAJ > > v8: 10961 > Change-Id: If0440c0595823c61352f144c1fc29c54a1175623 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2574716 > Reviewed-by: Marja Hölttä <marja@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#71619} TBR=marja@chromium.org,syg@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: I2384af84100dcf8cb27f10c5d055d7f864ebcbb9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2646139Reviewed-by:
Shu-yu Guo <syg@chromium.org> Reviewed-by:
-
Jakob Gruber authored
The final CL of this chain, this extracts translation opcodes into the TranslationOpcode class, and merges logic for TranslationArray creation into TranslationArrayBuilder. Drive-by: Pull TranslationArray printing logic into translation-state.cc. Bug: v8:11332 Change-Id: Ia4bbb6cdd15ea3318dfb9b7edb6eb881530dda54 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642254 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#72278}
-
Jakob Gruber authored
Looks like these may have been missed; all other related operators silence NaNs. Bug: v8:7519 Change-Id: If6ee8d6e02d304ccbb4821c21386f93eab225434 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2637853 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/c6a6de1..710b42c Rolling v8/third_party/aemu-linux-x64: 3BZ2tnIBSRNhCGGy-kjxHmfx7sU6OP0zvO9x3gtnnY8C..DUWCHyibCTWCe-ijlAKpinTlXaJQW2jg8hs7uRUfK0gC TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I0b8ab37f65b85d3c6df60e1da426774cca96222c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2646138Reviewed-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@{#72276}
-
- 23 Jan, 2021 2 commits
-
-
Igor Sheludko authored
It doesn't make sense in general and moreover an attempt to do so might cause hard stack overflow. Bug: v8:11317 Change-Id: I2a6bbadba1ebc5c1496660c734df76a13600edac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2643389Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#72275}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/61eac11..c6a6de1 Rolling v8/third_party/aemu-linux-x64: xAHa1IXmKteChkPvba9ezjSnKL7IyDePQRzWVUEAx9UC..3BZ2tnIBSRNhCGGy-kjxHmfx7sU6OP0zvO9x3gtnnY8C Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/beb8370..957dfea Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/361ccce..07bd252 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/786cae1..94a96af TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ie8f52da5e468fd92309253f2e1a5a335bcd9b3f1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2645703Reviewed-by:
-
- 22 Jan, 2021 11 commits
-
-
Maya Lekova authored
This CL introduces a new internal class PerIsolateAssertSwitch which gives a static Allow/Disallow interface to be used from within classes such as DisallowJavascriptExecutionScope without the need for slow heap allocations. Bug: chromium:1155348 Change-Id: I66cd8377b5d9c43510165cd7b9a7f5ccdaf45c18 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2617086 Auto-Submit: Maya Lekova <mslekova@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#72273}
-
Milad Fa authored
Without the added header the following compilation error might occur: error: ‘size_t’ does not name a type Change-Id: I021f6ce7b9691f76f0c439265850f1f4fc50685c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2645160Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#72272}
-
Jakob Kummerow authored
Change-Id: Ic1130d1bba3f70906cd39685bfa45b214424c2e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644952 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
This implements support for the following instructions: ref.func, call_ref, return_call_ref Bug: v8:7748,v8:9495 Change-Id: If5bdc2b9bc2347de056de2917430b8d9dc901c53 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2632591 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Michael Lippautz authored
Users of padded objects must know the actual object size for implementing custom finalizers. Bug: chromium:1056170 Change-Id: I0ddf9066cfece0a8d18a9e6fd985d09449eea92a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644941 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Michael Lippautz authored
- Adds IsGarbageCollectedWithMixin<T> to check for mixin applications. - Add documentation to all trait values. Bug: chromium:1056170 Change-Id: I22c255c36c791a5ff9b38d034f205f1e23c968ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644951Reviewed-by:
-
Ng Zhi An authored
Bug: v8:10972 Change-Id: I00651064c1c17ce4ddc8669f00f904257387d613 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2644068Reviewed-by:
-
Omer Katz authored
Bug: chromium:1056170 Change-Id: I3d6cbff3e37bb541481a014056e539bd4824c37c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642259 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
-
Omer Katz authored
CppHeap was missing a scope for incremental marking. This CL also introduces NestedEmbedderStepScope which is used for identifying nested samples to avoid double accounting in UMA. Bug: chromium:1056170 Change-Id: I8bba3fbfe6d098fe6861d1cfe5df8b88b4ac0fea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2642260 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
-
Victor Gomes authored
After removing the arguments adaptor frame, this should not be needed anymore. Removes ArgumentFrame from the following nodes: - ArgumentsLength - RestLength - NewArgumentsElements Also removes 'formal parameter count' as input of ArgumentsLength. Adapt the escape analysis to use the frame pointer directly instead of the ArgumentsFrame node. Change-Id: I0ead48a6ee05a10d05d6cfa2e46906ad69930986 Bug: v8:11306 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2639765 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#72264}
-
Victor Gomes authored
Removes unnecessary move after the removal of the arguments adaptor frame Change-Id: If92b9505ca23bb06a01bd25ba8e9664697d381f8 Bug: v8:11307 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2639759 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
-
