| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[heap] Pass Isolate to metadata accessors Removes the implicit Isolate::Current() when looking up page metadata from a HeapObject or address, and either uses an available Isolate* or makes the Isolate::Current() explicit. There is still a MemoryChunk::Metadata() accessor which implicitly calls Isolate: :Current() -- this can be fixed in followup work. Change-Id: Ia64f1a38750f4c9c7279c631480b3ee9aadd8917 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6906859 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102184} | 9 个月前 | |
[simulator][arm64] Add missing ProbeMemory calls Memory accesses in LoadStoreMultiStructHelper and LoadStorePairHelper were not tested with ProbeMemory. Added the missing calls, and converted the ProbeMemoryWithLandingPad test into a macro. Change-Id: I4aebc3dd15a3f43dfc4e55d9f8dff83068826cf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6700119 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#101293} | 11 个月前 | |
Revert "[builtin] Don't push the context on the entry frame" This reverts commit f531ce808300b51fae09c67f9f095b26ca24122c. Reason for revert: https://b.corp.google.com/issues/416128289. This CL causes a performance regression, probably because stack alignment. Original change's description: > [builtin] Don't push the context on the entry frame > > On x64 and ia32, the context was pushed on the entry frame, but it was > never accessed there afterwards. Also the GC did not iterate it. This CL > removes the slot for the context on the entry frame. > > R=leszeks@chromium.org > > Change-Id: I9128ebcf3b8c3502ef5d23c5af0026e0c645a5ef > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6500834 > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/main@{#100091} Change-Id: Iffa6821383294a5da6f03ed2815d90b21fb79d9d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6523821 Auto-Submit: Andreas Haas <ahaas@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#100220} | 1 年前 | |
[loong64][simulator] Only use read/write mutexes if we're multithreaded Port commit 5d337a0322939b2edf23608ae2e05d70142ae104 Port commit 84762a55c707ee3e195c8861801422f6ede8e6c0 Change-Id: Icf711a13e7c9ce0cb86ae2e35bb4b9438f91420b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7108579 Reviewed-by: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Liu Yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#103451} | 7 个月前 | |
[cleanup] Modernize std::*::value and ::type Mechanically replacing std::foo<X>::value with std::foo_v<X>, and the same for ::type -> _t. Change-Id: I543dda07ba4c95534cdcd51f1f438f2626be8273 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6491388 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#99940} | 1 年前 | |
[heap] Pass Isolate to metadata accessors Removes the implicit Isolate::Current() when looking up page metadata from a HeapObject or address, and either uses an available Isolate* or makes the Isolate::Current() explicit. There is still a MemoryChunk::Metadata() accessor which implicitly calls Isolate: :Current() -- this can be fixed in followup work. Change-Id: Ia64f1a38750f4c9c7279c631480b3ee9aadd8917 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6906859 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102184} | 9 个月前 | |
[riscv] Use amo* instr in codegen Change-Id: I9a84eb93e7c877f3f549c15cf36f5ea35cb75358 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7138845 Auto-Submit: Yahan Lu (LuYahan) <yahan@iscas.ac.cn> Reviewed-by: Kasper Lund <kasperl@rivosinc.com> Commit-Queue: Yahan Lu (LuYahan) <yahan@iscas.ac.cn> Reviewed-by: Florian Loitsch <floitsch@rivosinc.com> Cr-Commit-Position: refs/heads/main@{#103669} | 7 个月前 | |
[heap] Pass Isolate to metadata accessors Removes the implicit Isolate::Current() when looking up page metadata from a HeapObject or address, and either uses an available Isolate* or makes the Isolate::Current() explicit. There is still a MemoryChunk::Metadata() accessor which implicitly calls Isolate: :Current() -- this can be fixed in followup work. Change-Id: Ia64f1a38750f4c9c7279c631480b3ee9aadd8917 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6906859 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102184} | 9 个月前 | |
Revert "[builtin] Don't push the context on the entry frame" This reverts commit f531ce808300b51fae09c67f9f095b26ca24122c. Reason for revert: https://b.corp.google.com/issues/416128289. This CL causes a performance regression, probably because stack alignment. Original change's description: > [builtin] Don't push the context on the entry frame > > On x64 and ia32, the context was pushed on the entry frame, but it was > never accessed there afterwards. Also the GC did not iterate it. This CL > removes the slot for the context on the entry frame. > > R=leszeks@chromium.org > > Change-Id: I9128ebcf3b8c3502ef5d23c5af0026e0c645a5ef > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6500834 > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/main@{#100091} Change-Id: Iffa6821383294a5da6f03ed2815d90b21fb79d9d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6523821 Auto-Submit: Andreas Haas <ahaas@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#100220} | 1 年前 | |
heap: Place LABs in IsolateData Until now, LABs were accessed from generated code via external references, e.g., see NewSpaceAllocationTopAddress() and NewSpaceAllocationLimitAddress(). This patch places them in the IsolateData, so they can be accessed using Isolate-constant offsets. It affects the hot path of all TF generated code. Bug: v8:12428 Change-Id: I7bfd54bea4febead404829d8e0b058b6cf53a374 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3303800 Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#78176} | 4 年前 | |
buganizer: fix component IDs in DIR_METADATA This only matches the old monorail components. Bug: 341800538 Change-Id: Id74fbdb3b9be0c858b77af84966c6c37adf78c5c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6025833 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Paul Semel <paulsemel@chromium.org> Commit-Queue: Paul Semel <paulsemel@chromium.org> Cr-Commit-Position: refs/heads/main@{#97252} | 1 年前 | |
[owners] Add olivf@ to execution No-Try: true Change-Id: I0d2fe0b993bdeeabf76dae3f2a1e58cd0dfb6461 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5797190 Reviewed-by: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#95715} | 1 年前 | |
[cleanup] Fix inl header includes We have many inl headers which either do not include their non-inl header, or are including other headers first. Both can lead to compile errors because definitions of inline functions might not be visible in inl headers. This CL adds a script to fix those includes, and runs it over the whole code base. R=leszeks@chromium.org Change-Id: I1b7b04c59e5a5b89308512bfc40729f7ec4afc38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6387805 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99453} | 1 年前 | |
[runtime] ClobberDoubleRegisters rewritten in platform-specific assembly Currently ClobberDoubleRegisters is implemented in C++ and is not guaranteed to clobber all registers. Rewritten in assembly to clobber all double registers Bug: v8:11798 Change-Id: I11c09bd247c929d251e6e509ea5cc76b9981ea98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3490715 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#79380} | 4 年前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
[mips32] Delete mips32 from v8 Bug: v8:13206 Change-Id: Ifb5daeff2a1e91fd098bc5abe9f81339575636bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837160 Reviewed-by: Hannes Payer <hpayer@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Auto-Submit: Liu Yu <liuyu@loongson.cn> Commit-Queue: Liu Yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#83148} | 3 年前 | |
Include guards should be at the top of files. For the include guard optimization to kick in the include guards should be the first thing in the file, not counting comments. In some cases the guard has been moved above a comment for consistency even though this does not matter. A couple of include guards have been renamed for uniqueness. git cl upload complained about some lint nits which have been fixed. Change-Id: Iaa208ea6557c36c84bc7bb77c787ba9feb7cf037 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6275067 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Erik Corry <erikcorry@chromium.org> Cr-Commit-Position: refs/heads/main@{#98907} | 1 年前 | |
[handles] Prefer OpenDirectHandle to OpenHandle when possible This CL replaces expressions of the form: *Utils::OpenHandle(value) Utils::OpenHandle(value)->something to use Utils::OpenDirectHandle instead of Utils::OpenHandle. Both forms of expressions create a temporary handle and immediately dereference it, to get to the referenced object. Using a temporary direct handle instead, which is simply a pointer in builds with v8_enable_direct_handle=true (requiring conservative stack scanning), eliminates the allocation of a handle slot and the double indirection. Bug: v8:13270 Change-Id: Ibc242317b3fdfdecead861020677b9ea7b59a7d6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5234191 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#91997} | 2 年前 | |
Reland "[profiler] Surface VM & Embedder State" This is a reland of 2d087f237eadd78f5545548675642f013fdfe675 The changes are : * Fix redundant reinterpret_cast in test file for MSVC failure https://crbug.com/v8/12476 * Fix flaky test https://crbug.com/v8/12475 If a sample is captured during a GC, no embedder context is obtained defaulting to EMPTY. This is the expected behavior, made it in clear in implementation and in test. * Synchronized the embedder context filter behavior with existing native context filter. Original change's description: > Add APIs to surface VMState and new EmbedderState to CpuProfile samples. > > EmbedderState: > * An EmbedderState is defined as a value uint8_t and a v8::context used > for filtering. > * EmbedderStates are stack allocated by the embedder, construction and > destruction set/unset the state to the isolate thread local top. > * A v8::context is used to filter states that are added to a CpuProfile, > if the CpuProfile do not have a ContextFilter set or if contexts do not > match, state defaults to Empty. > > * v8:StateTag is already propagated all the way to a Sample, simply add > an API to surface it. > > VMState: > Change-Id: I7eed08907360b99b0ad20ddcff59c95c7076c85e > Bug: chromium:1263871 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3188072 > Auto-Submit: Corentin Pescheloche <cpescheloche@fb.com> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78250} Bug: chromium:1263871 Change-Id: Ief891b05da99c695e9fb70f94ed7ebdecc6c3b7b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3320037 Auto-Submit: Corentin Pescheloche <cpescheloche@fb.com> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#78281} | 4 年前 | |
[api] Promote deprecation in v8-fast-api.h Change-Id: Id1335f7c923d4b6e1d54721ede23cdb9ee2260d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6836379 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#101898} | 10 个月前 | |
[riscv][fastcall] Enable float support on riscv64 simulator Add IsReturnFloat64 in EncodedCSignature to support NaN Boxing float32. In RISC-V float32 need be NaN-Boxed, More details are under riscv spec: https://github.com/riscv/riscv-isa-manual/blob/aaf37804a85f7f1ed147e99e6efb2ffd29916d2a/src/d-st-ext.adoc#nan-boxing-of-narrower-values Port commit 098f31f49593fce4148717ccaf5f2b05b4ea9ad0 Port commit a6da8161197577a2221f5880cde4195f4ff92626 Change-Id: I1b4a86e597c29ae9a115aa00fb4f46421a2a55a8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5545261 Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#94046} | 2 年前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
[handles] Migration to direct handles, part 16 This CL migrates a large number of handles to direct handles. The changes are only relevant for builds with v8_enable_direct_handle=true. Affected source directories: api, asmjs, baseline, builtins, codegen, compiler, debug, deoptimizer, execution, heap, ic, init, objects, regexp, runtime, snapshot, wasm, and tests. Bug: 42203211 Change-Id: I3adbfb4aa55ebabec86ef94e312d92c8514446a0 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6240033 Reviewed-by: Omer Katz <omerkatz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#98600} | 1 年前 | |
[wasm][jspi] Rename STACK_SWITCH frame type to WASM_JSPI And StackSwitchFrame to WasmJspiFrame, to avoid future confusions with wasmfx frame types. R=clemensb@chromium.org Bug: 388533754,42202153 Change-Id: I133dea42f37278df11257d896f4b99a68393f0af Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6889552 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#102104} | 10 个月前 | |
[wasmfx] Implement the resume instruction Switch to the target stack in the resume instruction, and switch back to the current parent stack on return from the stack entry wrapper. Introduce the WasmFXResume and WasmFXReturn builtins to handle the platform specific logic of saving/restoring the stack state. The builtins reuse JSPI's {Isolate::SwitchStacks} via external C calls for the shared platform-independent logic. Add a new frame type for the WasmFXResume builtin to represent the stack exit, and update the stack frame iterator to support iterating chains of WasmFX stacks. With this change, it is already possible for JSPI to attempt to suspend multiple WasmFX stacks at once. However, properly supporting this requires non-trivial changes and will be done in a separate change. R=clemensb@chromium.org Bug: 388533754 Change-Id: I5c96b0014ab3db3a6eb8472ec6bc346ee93a2e9f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6904557 Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#102193} | 9 个月前 | |
[sandbox] Remove kDefaultCodeEntrypointTag, pt.1 This is a step towards making code entrypoint tag verification strict. This CL - introduces kCodeEntrypointTagForTesting, - introduces CodeKind::FOR_TESTING_JS in addition to existing CodeKind::FOR_TESTING in order to assign them different code entrypoint tags (kJSEntrypointTag for the former and kCodeEntrypointTagForTesting for the latter), - add SBXCHECK for Code object's entrypoint tags when generating calls and tail calls to compile-time known Code objects, - introduce Linkage::GetCPPBuiltinCallDescriptor() - a CEntry call descriptor customized for CPP builtins, - replaces some of the kDefaultCodeEntrypointTag usages with correct tags, - fixes usages of entrypoint tags in various code generation unit tests. Drive-by: - assign proper descriptor for GenericJSToWasmInterpreterWrapper builtin, - make Builtins::CallInterfaceDescriptorFor() work for bytecode handlers, - make switches over CodeKind values case-complete. Bug: 435630464 Change-Id: I2e34666df5314b0cd4e604a4deaf74e2f0de6f1a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6976541 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102733} | 9 个月前 | |
[wasmfx] Implement the resume instruction Switch to the target stack in the resume instruction, and switch back to the current parent stack on return from the stack entry wrapper. Introduce the WasmFXResume and WasmFXReturn builtins to handle the platform specific logic of saving/restoring the stack state. The builtins reuse JSPI's {Isolate::SwitchStacks} via external C calls for the shared platform-independent logic. Add a new frame type for the WasmFXResume builtin to represent the stack exit, and update the stack frame iterator to support iterating chains of WasmFX stacks. With this change, it is already possible for JSPI to attempt to suspend multiple WasmFX stacks at once. However, properly supporting this requires non-trivial changes and will be done in a separate change. R=clemensb@chromium.org Bug: 388533754 Change-Id: I5c96b0014ab3db3a6eb8472ec6bc346ee93a2e9f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6904557 Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#102193} | 9 个月前 | |
[api] Avoid species lookup in v8::Promise::{Then,Catch} This aligns the C++ Promise API with the WebIDL specification by using the PerformPromiseThen abstract operation. This avoids species lookups, making the API more robust against monkey-patched Promise constructors and guaranteeing that the API result type can actually be v8::Promise. Drive-by clean up PromiseToLocal into ToLocal with the guaranteed type. Bug: 40050555 Change-Id: I0e1b1415cab4f35d63a0a30cf41d22e915fbe401 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7079568 Reviewed-by: Andreas Haas <ahaas@google.com> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103373} | 8 个月前 | |
[api] Avoid species lookup in v8::Promise::{Then,Catch} This aligns the C++ Promise API with the WebIDL specification by using the PerformPromiseThen abstract operation. This avoids species lookups, making the API more robust against monkey-patched Promise constructors and guaranteeing that the API result type can actually be v8::Promise. Drive-by clean up PromiseToLocal into ToLocal with the guaranteed type. Bug: 40050555 Change-Id: I0e1b1415cab4f35d63a0a30cf41d22e915fbe401 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7079568 Reviewed-by: Andreas Haas <ahaas@google.com> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103373} | 8 个月前 | |
Small improvements of various scopes - InterruptScope - use uint32_t for interrupt masks - Make constructor/destructors inlinable - Remove virtual subclasses since the custom interrupt handling is already implemented via the mode_ member - SaveContext scope: remove unused c_entry_fp_ - Avoid context handle in CallDepthScope Change-Id: I077f05165782b4bb6298a3dc5bec23b96266b904 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4247437 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#85818} | 3 年前 | |
[execution] Use uint8_t instead of byte Byte is an alias for the standard uint8_t type (defined in src/common/globals.h). For readability, avoid the alias and use the uint8_t directly. R=jkummerow@chromium.org Change-Id: Icf875df86a538ef1ed911b1f1b375b889d8131cd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4523173 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#87621} | 3 年前 | |
Revert "[wasmfx] Implement tag parameters and returns" This reverts commit b086976de652588c6620662b7f73af498ffe3450. Reason for revert: Failure on PKU bot: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20-%20PKU/13615/overview Original change's description: > [wasmfx] Implement tag parameters and returns > > - Add a global buffer in the isolate and use it as a temporary storage > to pass arguments across stacks. > - Resize the buffer based on continuation and tag types found in newly > decoded modules. > - The buffer can be loaded as an offset from the Isolate root, so we > don't need to pass it explicitly as an argument. > - Use the buffer to pass tag parameters, and unpack them from the resume > handler. > - Similarly, store resume parameters in the buffer, and unpack them > after the suspend instruction. > > Passing the initial func ref arguments and returning the return values > is not supported yet. > > R=jkummerow@chromium.org > > Bug: 388533754 > Change-Id: I0c907f5134939a7d75179f12ffcf392a2ce159a3 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7146289 > Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Cr-Commit-Position: refs/heads/main@{#103771} Bug: 388533754 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I6e19de5927ace075f3767b6c6ac7771eff04d64d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7164999 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> Owners-Override: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#103773} | 7 个月前 | |
[hole] Remove unneeded hole value checks Undo a bunch of work which added by-value hole checks. Originally we wanted to make holes fully unmapped, including their map pointer, so that potential hole values would have to be checked by pointer value rather than map checks. This turned out to be tricky, partially because the optimizing compiler could hoist map reads above hole checks, and partially because the extra hole value checks ended up with performance regressions. In https://crrev.com/c/7156717 we switched to keeping the holes' maps mapped with an unmapped payload after the map (very similar approach to the WasmNull). This means that all those hole checks we added are now unnecessary, since they were already covered by the existing map-based checks. We can also remove the --assert-hole-checked-by-value flag and fuzzing, since this is no longer an invariant we want to preserve. Bug: 434179415 Change-Id: I9399498d89592127e4291b8acffee83a3ba70052 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7206087 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#103982} | 7 个月前 | |
[heap] Remove MemoryChunk::GetHeap() Always go through the metadata object to make clear that this pointer is trusted. Bug: 429538831 Change-Id: I52369359faa5f9e45658070e54fb5a14ba8469c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6765767 Reviewed-by: Anton Bikineev <bikineev@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101494} | 11 个月前 | |
Remove GetHeapFromWritableObject Same as https://crrev.com/c/6695012 but for the GetHeapFromWritableObject() method. R=mlippautz@chromium.org Bug: 396607238 Change-Id: I4986c52375d7848e2c300268a6b6118bc628883a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6695546 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101330} | 11 个月前 | |
heap_dump_1 for jsvm TicketNo: AR20260205251565 Description: heap_dump_1 for jsvm Team:gitee Feature or Bugfix: Binary Source: sync from gitee PrivateCode(Yes/No):No Change-Id: I2c4bf8190cab99d9278a68c3c7f94092f0507054 Reviewed-by: y00500721 Approved-by: w00518651 Merged-on: https://open.codehub.huawei.com/OpenSourceCenter_CR/openharmony-tpc/chromium_v8/-/change_requests/558 Merged-by: public pjenkins Signed-off-by: huanghan18 <huanghan18@huawei.com> revert merge request: AR20260205251565 heap_dump_1 for jsvm 5fae5665635fc7a1b52e325454044501fafec68e This revert merge request !453 | 1 个月前 | |
[v8]jsvm OOM use hisysevent TicketNo: DTS2026031703156 Description: [v8]jsvm OOM use hisysevent Team:gitcode Feature or Bugfix: Binary Source: sync from gitcode PrivateCode(Yes/No):No ------ DO NOT MODIFY, AUTO-GENERATED! ------ gitcode-Issue: 117 Time: "2026-03-31T03:03:10.268740Z" PR-Num: 421 gitcode-PR: https://gitcode.com/openharmony-tpc/chromium_v8/pull/421 UserId:30014474 Change-Id: I1774926181646c6e5ef7fedaa421fbb6d3f40079 Reviewed-by: w00518651,h00886390 Approved-by: w00518651 Merged-on: https://open.codehub.huawei.com/OpenSourceCenter_CR/openharmony-tpc/chromium_v8/-/change_requests/525 Merged-by: public pjenkins Signed-off-by: jiang-qunchao <jiangqunchao@huawei.com> | 1 个月前 | |
[cleanup] Fix inl header includes We have many inl headers which either do not include their non-inl header, or are including other headers first. Both can lead to compile errors because definitions of inline functions might not be visible in inl headers. This CL adds a script to fix those includes, and runs it over the whole code base. R=leszeks@chromium.org Change-Id: I1b7b04c59e5a5b89308512bfc40729f7ec4afc38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6387805 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99453} | 1 年前 | |
[isolate] Propagate FPU state to bytecode compile tasks Also add additional DCHECKs around LocalIsolate to make sure FPU state is consistent for all LocalIsolate-using threads, and reset FPU state on POSIX thread entry to make sure this DCHECK is able to fail. Fixed: 422598067 Change-Id: I691afb1b8292c580f49b75f48a8e4a402347c5bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6632794 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#100796} | 1 年前 | |
[cleanup] Remove leaptiering ifdefs from tiering Bug: 42204201 Change-Id: I10d7765fd38e58c48633d0cc659dcf0c1918787a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6994660 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#102830} | 9 个月前 | |
[serializer] Promote ObjectTemplateInfo to RO space when possible This CL adds v8::ObjectTemplate::SealAndPrepareForPromotionToReadOnly() which is supposed to be called by embedder when the object template is ready and is not going to be modified. Additionally, support 3-way promo decisions for promotion to read only space. The third mode "match host" is supposed to indicate that decision depends on the outer object. This is useful for types such as ArrayList or JSExternalObject (AKA v8::External), when it's impossible to make a promo decision by looking just at object without knowing how it's used. Bug: 399393891 Fixed: 413385733 Change-Id: Ic99783ea69d293c5659c3a5d74cd7151d93ba54a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6416966 Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#99991} | 1 年前 | |
Include guards should be at the top of files. For the include guard optimization to kick in the include guards should be the first thing in the file, not counting comments. In some cases the guard has been moved above a comment for consistency even though this does not matter. A couple of include guards have been renamed for uniqueness. git cl upload complained about some lint nits which have been fixed. Change-Id: Iaa208ea6557c36c84bc7bb77c787ba9feb7cf037 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6275067 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Erik Corry <erikcorry@chromium.org> Cr-Commit-Position: refs/heads/main@{#98907} | 1 年前 | |
[api] Fix micro task queue completion callbacks We used the non-empty state of the COW vector to indicate whether the COW vector was used in first place. This is not correct if the COW vector is used and all callbacks (i.e. the last one) was removed from within the callback itself. Fix this by indicating this bit via using optional. Bug: 350350588 Change-Id: I03c629ce72d25d854f28e79e7e5e435052585230 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6172299 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98090} | 1 年前 | |
[api] Fix micro task queue completion callbacks We used the non-empty state of the COW vector to indicate whether the COW vector was used in first place. This is not correct if the COW vector is used and all callbacks (i.e. the last one) was removed from within the callback itself. Fix this by indicating this bit via using optional. Bug: 350350588 Change-Id: I03c629ce72d25d854f28e79e7e5e435052585230 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6172299 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98090} | 1 年前 | |
[mutex] Replace SharedMutex with SpinningMutex Rationale: https://g3doc.corp.google.com/devtools/library_club/g3doc/totw/197.md Change-Id: Ic488c895c4ea3e6d75e6c70d91b706a70d00a80f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6218211 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98446} | 1 年前 | |
[wasm][arm64] Growable stacks for Liftoff The CL introduces segmented stacks for JSPI secondary stacks for Arm64 Liftoff. When stack overflow happens a builtin allocates a new stack segment and evacuates overflowed frame there with incoming params. And then execution continues. A stack can grow until --stack-size is reached. More details in the design doc: https://docs.google.com/document/d/1yw0n3aA7QVzkovI8uvLupe5AiocyW8lmweFQbDy3pFM/ Bug: 42202153 Change-Id: I74e0f3a0a5dd2cef0a58fbe490f6809e1634a449 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5790492 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Ilya Rezvov <irezvov@chromium.org> Cr-Commit-Position: refs/heads/main@{#95842} | 1 年前 | |
[deoptimizer][wasm][arm64] Re-sign caller pc for pointer authentication In case of tail calls in the deoptimized frames the caller pc of the bottom most (outer most) function can end up in a different stack slot than in the optimized function as the number of parameter stack slots may differ. This means, the caller_pc_ needs to be stripped from the PAC and re-signed again prior to writing it to the output frame. Fixed: 353582136 Bug: 42204618 Change-Id: I1670c416d3af44af0507b82717ac1df4d3cc11ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5716734 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Stephen Röttger <sroettger@google.com> Cr-Commit-Position: refs/heads/main@{#95148} | 1 年前 | |
[cleanup] Fix inl header includes We have many inl headers which either do not include their non-inl header, or are including other headers first. Both can lead to compile errors because definitions of inline functions might not be visible in inl headers. This CL adds a script to fix those includes, and runs it over the whole code base. R=leszeks@chromium.org Change-Id: I1b7b04c59e5a5b89308512bfc40729f7ec4afc38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6387805 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99453} | 1 年前 | |
[compiler] Optimize Date.prototype.getXXX() accessors ... in Maglev and TurboFan. This CL: - adds NoDateTimeConfigurationChangeProtector, - makes sure that JSDate's cached fields are always initialized, which make it possible to read cached fields directly without additional run-time checks. Drive-by: - move DateCache::stamp_ field to IsolateData (this removes one indirection on access and avoids potential issues with reallocated DateCache object), - make deserializer recompute cached fields after deserialization to match current date/time configuration which could have been different during snapshot creation, - simplify definition of alignment padding fields in ISOLATE_DATA_FIELDS by introducing PADDING_FIELD macro. Bug: 411352101 Change-Id: I69e25b1ce7e2c79f9aeee69e97192be62a08c2c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6535917 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#100248} | 1 年前 | |
[array] Remove ArrayConstructorProtector Remove the ArrayConstructorProtector, which guarded against Array constructor calls with too-large arguments, exceeding the max initial array size, where the optimizing compilers would deopt out of inlined Array construction when the elements didn't fit inside a new space page. The original idea here was that we can usually guard against deopts and deopt loops here by marking the allocation site, and we'd only set the protector when there is no allocation site available, which should be rare. However, this original idea predates lazy feedback allocation, which makes missing allocation sites common in the initial state rather than rare. Fortunately, we have another mechanism for preventing deopt loops, which is the call speculation bit on CallICs (which is also predated by the original ArrayConstructorProtector idea). So, with appropriate wiring, we can use this call speculation bit for call-sites which will never have an allocation site, and allow lazy feedback (and thus lazy allocation sites) to still be used for the common case without invalidating any global protectors. Only in a few very rare cases will we have neither an allocation site nor a CallIC on array construction (e.g. accessors an polymorphic construction sites), and for these cases we can disable the speculative array constructor inlining at compile time. Bug: 420613330 Change-Id: I0386cce96412baf1e0598d0d95167b3e01466fe1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6590918 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#100548} | 1 年前 | |
[runtime] Merge redirected and non-redirected callback fields Namely: - AccessorInfo::getter and AccessorInfo::js_getter, - CallHandlerInfo::callback and CallHandlerInfo::js_callback. The redirected/non-redirected callback distinction is required only for simulated builds but we wasted memory also for all native builds. Now we store these fields in "redirected" form which allows us to call them directly from builtins or generated code. In case it's necessary to call a callback from C++ code the C function address is read from the redirection. This additional indirection makes the callback calls from C++ code in simulated builds slower but saves memory for native builds. This CL should recover a part of memory regression caused by inlining Foreign fields into AccessorInfo and CallHandlerInfo. Bug: v8:12949, chromium:1336105, chromium:1335930 Change-Id: I38470ed21ee23b281247c11a9531542c7e4acca1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835686 Reviewed-by: Jakob Linke <jgruber@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#82631} | 3 年前 | |
[cleanup] Modernize std::*::value and ::type Mechanically replacing std::foo<X>::value with std::foo_v<X>, and the same for ::type -> _t. Change-Id: I543dda07ba4c95534cdcd51f1f438f2626be8273 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6491388 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#99940} | 1 年前 | |
[wasm][growable-stacks] Fix IsOnCentralStack check When computing the central stack bounds in Isolate::IsOnCentralStack() check, we incorrectly use the secondary stack limit margin instead of the central stack margin. This is the margin that we allow C++ to overflow the JS stack limit by, and it is stricter for secondary stacks than for the central stack. So this can lead to false positives when C++ code runs near the stack limit. R=clemensb@chromium.org Fixed: 425827679 Change-Id: I65614346d82848bce4f3abd95e3e3b730fdce5c2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6678674 Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#101059} | 1 年前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
Reland "[wasm] Differentiate the stack guard on loop back edges" This is a reland of commit 5868db33ba95544a8945bfc6f478cb79de0cf641 Changed in reland: when we only handle no-heap-write interrupt requests, we should only check for such requests. Original review: crrev.com/c/7036471 Change-Id: I745216818096640672d3b75c230e6235b166d4c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7062937 Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#103226} | 8 个月前 | |
Use thread_local for storing ThreadId Change-Id: Ifc754fb81089aed4cb79b1f6c4aab0cb73a2a5d7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2537690 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#71176} | 5 年前 | |
Move relevant files to src/execution Bug: v8:9247 Change-Id: I79e0553e8a0d6dac2aa16b94a6c0e05b6ccde4a1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1621934 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#61725} | 6 年前 | |
[runtime] Add IDLE_EXTERNAL VM state Otherwise we can't properly filter samples where V8 isn't on the stack at all. This also updates the tick processors to include ATOMICS_WAIT support that has been missing for years. Change-Id: I511f1d706d9d5bbee317f7f12608c7618266fe7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6714365 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101305} | 11 个月前 | |
Reland "Remove g_thread_in_wasm_code flag" This is a reland of commit 73288e18ba967b06e73cacd8f1659529915e3097 For ASan on Windows, we need more function to run without ASan instrumentation now. Original change's description: > Remove g_thread_in_wasm_code flag > > Keeping track of whether a thread is currently executing Wasm code or > not has become quite complex (see size of this change) and therefore a > maintenance burden. Furthermore, this feature now conflicts with future > V8 sandbox advancements as we want to forbid writes from sandboxed code > (which includes all Wasm code) to out-of-sandbox memory. As such, we can > no longer write to thread-local storage (where the flag was stored). > > This CL replaces the flag with a simpler guarding mechanism that ensures > that the trap handler is robust against nested faults and deadlocks. In > essence, we now set a thread-local flag (only) when entering the trap > handler or taking one of the locks used by it. If the flag is already > set when entering the trap handler, then we bail out immediately as it > means that we're either handling a nested fault (which we shouldn't) or > risk running into a deadlock because the current thread holds one of the > locks required by the trap handler. > > Bug: 350324877, 40192807 > Change-Id: Idb9fce83ac9b46ab04fd93d5bdbd8cb8c0722488 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6650680 > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Reviewed-by: Mark Seaborn <mseaborn@chromium.org> > Commit-Queue: Samuel Groß <saelo@chromium.org> > Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#101213} Bug: 350324877, 40192807 Change-Id: I9c5a6b3820181129fa7ed4240831cfc1dbef1697 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6700520 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101275} | 11 个月前 | |
2026.03.30 arkweb_144代码蓝黄同步 Signed-off-by: jiujiaoxiaogula <sujiahao10@huawei.com> Change-Id: I00194d339064f999dedfc211cd5af5501cbed0fb | 3 个月前 | |
Reland "[handles] Migration to direct handles, part 5" This is a reland of commit aba439cfe3964922735607a5e44c6cd158c75268 Original change's description: > [handles] Migration to direct handles, part 5 > > This CL migrates a large number of handles to direct handles. The > changes are only relevant for builds with v8_enable_direct_handle=true. > > Bug: 42203211 > Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg > Change-Id: I57d35b99ec3bd83bc2ba5590ad18021bc4e34592 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5771452 > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/main@{#95576} Bug: 42203211 Change-Id: I201b85456fd359d261c08a533c42a522626daf39 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5785213 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#95598} | 1 年前 | |
[isolate-groups] Update usage of PtrComprCageAccessScope. Remove unnecessary PtrComprCageAccessScopes since access to RO roots has changed recently. Bug: 42204573 Change-Id: I455261602768ecde93bad267ef1325477dcb86f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6120294 Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Dmitry Bezhetskov <dima00782@gmail.com> Cr-Commit-Position: refs/heads/main@{#98153} | 1 年前 | |
[base] Merge SpinningMutex back into Mutex They are now the same; beyond that we can't do ave THREAD_SAFETY_ANALYSIS on a bunch of previous SpinningMutex cases, so we'll need to propagate this into Mutex. Bug: 384940357 Change-Id: Ifbd4ffc4090738455036f32d9a5cf813b9f15781 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6244422 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#98597} | 1 年前 | |
[runtime] Add IDLE_EXTERNAL VM state Otherwise we can't properly filter samples where V8 isn't on the stack at all. This also updates the tick processors to include ATOMICS_WAIT support that has been missing for years. Change-Id: I511f1d706d9d5bbee317f7f12608c7618266fe7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6714365 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101305} | 11 个月前 | |
Fix random presubmit warnings Those were flushed out in https://crrev.com/c/6582961. R=leszeks@chromium.org Change-Id: I97024c19a4211c3057ae36ee5c6585996b14e42a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6579374 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#100471} | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 9 个月前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 7 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 3 个月前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 10 个月前 | ||
| 2 年前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 8 个月前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 |