| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[wasm][ESM] Add API for source-phase imports The API is similar to the existing WasmStreaming API, but can be instantiated fully from the background. Only the final Finish step needs to be called from a foreground task. After all the refactorings that already landed for https://crbug.com/446885278 this is a pretty straight-forward addition now which reuses most of the existing logic for WasmStreaming. R=jkummerow@chromium.org CC=lpardosixtos@microsoft.com Bug: 446885278 Change-Id: I4749e27a722b1e50e107a808a3e02f8d70adbbce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7156414 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#103915} | 7 个月前 | |
[test] Remove some unused includes (2) Mostly test/fuzzer, test/inspector, test/unittests. Bug: v8:13006 Change-Id: I825efa5d72a224bb3cb9f86a9fac8763e9dbd1cf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3769696 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#81799} | 3 年前 | |
[arm64] Fix the PRFM disassembly Change-Id: I82f8ea3e6096fd67cd54fe55a879800441d5b19a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7096243 Auto-Submit: Anton Kirilov <anton.kirilov@arm.com> Commit-Queue: Sam Parker-Haynes <sam.parker@arm.com> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#103783} | 7 个月前 | |
[platform] Remove default values for parameters of virtual overrides These implementations should not be called directly, so the default values are just noise. NFC. Change-Id: I7a6958c0170313dfd2e0dddd3097e9a271ac4514 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7203288 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Andy Wingo <wingo@igalia.com> Cr-Commit-Position: refs/heads/main@{#103983} | 7 个月前 | |
[sandbox] Activate sandbox hardware support in unittests With this CL, if enabled at compile time we now activate sandbox hardware support at runtime for all unittests. This requires opting out a few unittests that are currently incompatible with hardware sandboxing support, mostly due to the use of signal handlers. Bug: 350324877 Change-Id: Ib6414003abe34f41da5f1d2a3e44544644e812d6 Cq-Include-Trybots: luci.v8.try:v8_linux64_pku_dbg,v8_linux64_pku_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6718196 Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101392} | 11 个月前 | |
[cfi] add a force-memory-protection-keys flag This change also adds the ThreadIsolatedAllocator support for the other non-default platforms. Fixed: 418724441 Change-Id: If6a4f84ff4a9c8a1a10a3afe88efed67611bcc63 Cq-Include-Trybots: luci.v8.try:v8_linux64_pku_rel,v8_linux64_pku_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6586437 Commit-Queue: Stephen Röttger <sroettger@google.com> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#100563} | 1 年前 | |
[init] Finalize compilation Job when last isolate tears down The job_handle_ in OptimizingCompileTaskExecutor was supposed to get destroyed as part of V8::DisposePlatform(). However, some Blink unittests do not invoke this method and therefore the job can leak. This CL fixes this leak by resetting the job once the last isolate leaves the IsolateGroup. Bug: 40274702 Change-Id: I3fca938135d2915ce32cd11f439314a6ce9ec63f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6491347 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#99944} | 1 年前 | |
[v8] Fix CVE Signed-off-by: gaojunyu <gaojunyu2@h-partners.com> | 25 天前 | |
[timezones] Remove DST cache, add local offset cache This puts the interval-based caching approach back to the critical path (ToLocal / ToUTC) after it was removed by https://chromium-review.googlesource.com/c/v8/v8/+/572148 . For more information, see https://docs.google.com/document/d/1fZ3TXSzeHKaK-L-OAAxSUrF2L_157-psVzKauW4DQWk/edit?usp=sharing . Additional changes in the CL: - Harden the cache by adding a SLOW_DCHECK that the cached result we return always matches the result we'd get without the cache. - Make invalid cache item handling explicit, not based on them having certain start / end times. - Remove the restriction around kMaxEpochTimeInSec since the restriction doesn't seem to hold for the function called by the new caching code. Change-Id: I4cd7d48e1719e7a4d51101b7f3e7a0fda85dd7db Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5899395 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#96424} | 1 年前 | |
[sandbox][api] Use new String::Write* APIs In https://crrev.com/c/5975682 we introduced new version of the String::Write* APIs. In this CL, all users of the old API in V8 are converted to the new API. Bug: 373485796, 376071292 Change-Id: Ia2ec193c266322bb627ebfa9acdd642f87bb6286 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5979449 Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#97172} | 1 年前 | |
[tests] Remove --always-turbofan from deoptization unittests Use the %PrepareForOptimization/%OptimizationFunctionOnNextCall pattern instead. Drive-by: remove useless flag "--prepare-always-turbofan" Bug: 431974094 Change-Id: Ibb10d379082c4a0cabe8f6773b38b54e2bf5efa0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6769642 Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#101528} | 11 个月前 | |
[gtest] Clean up single-arg testing::Invoke()s Not needed and deprecated [0]. This CL should be a no-op. [0]: https://chromium.googlesource.com/external/github.com/google/googletest.git/+/a05c0915074bcd1b82f232e081da9bb6c205c28d/googlemock/include/gmock/gmock-actions.h#2046 Bug: chromium:439838457 Change-Id: I95fcdefb5e6a529f43312403319c1aa10b5ec5fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6941574 Auto-Submit: Jonathan Lee <jonathanjlee@google.com> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#102454} | 9 个月前 | |
Ensure JSPromise::Resolve() obtains "then" method from the correct context As an optimization, Resolve() will use isolate->promise_then() to get the "then" method whenever resolution is a native promise object in *any* context. The Torque builtin ResolvePromise() mirrors this Resolve() method in nearly every way. However, Node issue https://github.com/nodejs/node/issues/59541 revealed a discrepancy. In Torque, ResolvePromise() only does the equivalent optimization if resolution is a native promise object in the *current* context. While all then native methods in all native contexts share the same behavior, of course, the distinction actually matters. The thenable job task is enqueued on the microtask queue of the native context associated with the then method, and the C++ version can in effect pick a different native context, and thus a different queue, than the Torque version. For instance, in current native context A, if the native Promise resolution comes from native context B, Resolve(promise, resolution) will enqueue the task on native context A, while ResolvePromise(promise, resolution) will enqueue the task on native context B. Indeed, for Resolve(), resolution is a native promise object in any native context, and by using isolate->promise_then() it fetches a then method from native context A (the current native context). While for ResolvePromise(), resolution is not a native promise object in the current native context A, therefore it skips the optimization, and will simply look up resolution["then"], fetching the native then method from context B. This change ensures Resolve(), when applying this optimization, obtains a "then" method from the creation context of resolution. Before this change, the test DetachGlobal_ResolveThenableNativeThen succeeds with builtin (ResolvePromise) but fails with runtime (JSPromise::Resolve), illustrating bug v8:441679231. Bug: v8:441679231 Change-Id: I43643c36420228a416c08d6f06c37273efd93082 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6920776 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#102517} | 9 个月前 | |
[maglev] Enable always_osr_from_maglev Drive-By: * Fix the logic when to do osr checks. * Don't call into the OSR runtime function if we are already in the process of compiling osr code. Bug: 328115456 Change-Id: I6d80b57a8824bd775aaf69ca8235ed85ba317835 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6458426 Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#99822} | 1 年前 | |
【CVE-2026-4450】【487746373】【490642836】【CVE-2026-4457】【488803413】[CVE-2026-4461][490558172][489159859][481749436][491191100][492077213][496629079][472181383][480442279][481295170][485784597][474402856][483220222] Signed-off-by: Marja Hölttä <marja@chromium.org> | 25 天前 | |
Enable Clang -Wshadow warning A recent correctness bug was caused by variable shadowing (https://crrev.com/c/6097639). And re-enabling the -Wshadow warning found a bug in MaglevGraphBuilder::TryReduceFunctionPrototypeApply (fixed in https://crrev.com/c/6113594). So, sounds like a good idea to enable this warning to avoid similar issues in the future. Bug: chromium:40643816 Change-Id: I4bab2c25e908b80328e75385ad20e12a9867aa8f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6163544 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#98041} | 1 年前 | |
[interpreter] Improve bytecode disassembler output Pass the constant pool to the bytecode decoder, so that constants can be printed as part of the bytecode itself. Also improve printing of the new split index types. Change-Id: Ia65149765b03a8d2665810b1d377e5b497600d15 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7209311 Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Patrick Thier <pthier@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#104020} | 7 个月前 | |
Support sharing ReadOnly heap for multi-cage mode. RO heap will be shared only for isolates inside one isolate group and so, the RO heap and its artifacts will be per isolate group. This patch unifies code for obtaining RO artifacts for all configuration and removes dead code like PointerCompressedReadOnlyArtifacts since we use isolate groups in all configurations. Also, current tests that test sharing heap are skipped for multi-cage mode because in the current execution model each isolate creates its isolate group so the heap isn't shared. Bug: 357931034 Change-Id: I3095144156465137a6dd591471890e0ff34ece72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5857294 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Dmitry Bezhetskov <dima00782@gmail.com> Cr-Commit-Position: refs/heads/main@{#96114} | 1 年前 | |
[fuzztest] Add json fuzzer This adds an exemplary fuzz test for json, inspired by the existing libfuzzer json fuzzer. The inputs are structurally aware and focus on valid json inputs, generated with the help of jsoncpp (while the existing libfuzzer implementation would work on arbitrary strings mostly leading to parse errors). In the future, we could also add another fuzz test with arbitrary inputs. Domains for FuzzTest are constructed with utilities from: https://github.com/google/fuzztest/blob/main/doc/domains-reference.md Bug: 40941204 Change-Id: I76c7337ffb1a5a530dedcfba092e0d9260cdec66 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5367021 Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#92818} | 2 年前 | |
[platform] Rename Call[Blocking/LowPriority]OnWorkerThread() to PostTaskOnWorkerThread PostTaskOnWorkerThread takes a priority argument, instead of exposing multiple methods. CallOnWorkerThread is kept around because Chrome codebase has a call to it that needs to be switched. It will be removed in a follow-up. This should address https://chromium-review.googlesource.com/c/v8/v8/+/5952524 Change-Id: Ie45941b6996737a7ef04994c32dfa775717f4aa3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5350692 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/main@{#97426} | 1 年前 | |
[ept] Delete tag kExternalObjectValueTag The tag was a generic tag used for v8::External. After a recent refactoring, the generic tag should not be used anymore. Instead, type-specific tags should be used. Additionally the number of tags reserved for v8::External gets reduced from 100 to 40, as this is enough in currently for Chrome, where 34 tags are used so far. The reduction is needed to make sure that the ExternalPointerTags stay within 7 bit range. Another change is that the tags that were used so far for tests are out of range now. Therefore, the tags get shifted to a new value range. Bug: 436799229 Change-Id: I0bbef6391bd4340d8d113ba01a565d9f1a24a0a4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7003791 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#102975} | 8 个月前 | |
[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 个月前 | |
[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 个月前 | |
Reland "[handles] Migration to direct handles, part 12" This is a reland of commit 5fa54d85a10049a55ba2fa02bc05145ddee7d19a Original change's description: > [handles] Migration to direct handles, part 12 > > 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, ast, builtins, codegen, > compiler, d8, debug, deoptimizer, diagnostics, execution, extensions, > heap, ic, init, interpreter, json, maglev, objects, parsing, profiler, > regexp, runtime, snapshot, strings, wasm, and tests. > > Bug: 42203211 > Change-Id: I2334b3295e5780e8f52d0b13d1545dce29fcf81e > Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6181904 > Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#98240} Bug: 42203211 Change-Id: Ie21acd681c12e7212185d61a19bd858365650204 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6187462 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#98249} | 1 年前 | |
[heap] Use task with kUserVisible priority instead of idle task This CL switches from idle tasks to kUserVisible tasks for "context disposal" GCs. @etiennep thankfully notices that this can improve JS score quite a bit. As we have no guarantee when this task will be run after being scheduled, we use gc_count() to only trigger a GC if no GC has been performed in-between. For idle tasks we limit this based on time, the task had to run within two frames (=16ms*2). Unlike idle tasks the regular tasks don't get a deadline, instead we use a hard coded limit of 5ms. In addition to the previous condition, we only perform the GC if the estimated time for it is less than 5ms. This CL improves JS2 by about +0.7%, JS3 by about +0.2%. Bug: 460477160 Change-Id: I9d084d59dca53a57d5cb6e81f26c122f037f15f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6734023 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#104016} | 7 个月前 | |
[ArkWeb][安全][自动提交] 修复 Chromium issue 511228272: Reland "[scanner] Fix integer overflow in LiteralBuffer and guard stream limi… Signed-off-by: ringking <renkang2@huawei.com> | 10 天前 | |
[profiler] Add unittest for heap snapshots This CL adds a C++ unittest for heap snapshot generation. This allows us to check that in resulting snapshot both node_fields/node_types and edge_fields/edge_types have the same length. Bug: 416245387 Change-Id: I1bad0d788dbf9ed75faa1644bdb58d5dd207e9a1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6565347 Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#100386} | 1 年前 | |
[regexp] Move mode to RegExpMacroAssembler ... instead of having it in each sub-class individually. Previously it was only used in sub-classes of NativeRegExpMacroAssembler, but we also want to use it in the Bytecode-Generator. Drive-by: Also move char_size() from individual sub-classes to RegExpMacroAssembler. Bug: 437003349 Change-Id: I89b20419d718892b477f8a9643cc105aef401b29 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7164997 Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#103785} | 7 个月前 | |
[handles] Migration to direct handles, part 8 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, builtins, codegen, compiler, date, debug, diagnostics, execution, heap, ic, init, interpreter, json, logging, objects, parsing, regexp, runtime, snapshot, strings, wasm. Bug: 42203211 Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Change-Id: Ib35bb03997bb4a646c56674f834b952dffdeaf02 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6074945 Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#97624} | 1 年前 | |
[wasm][cleanup] Drop kCanonicalI32 etc aliases They are the same as kWasmI32 etc now anyway. This CL does not change behavior or performance. Change-Id: I5528ae4b8e9f029e2710db3d358cc3284472f4bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6333549 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#99100} | 1 年前 | |
[sandbox] Test detection of invalid bytecode In crrev.com/c/7203123 we added abort_with_sandbox_violation and use it when executing an invalid bytecode. This CL now adds a unit test to ensure that execution of invalid bytecode is correctly detected as a sandbox violation crash. Bug: 461681036 Change-Id: Iaa52a2f3664dfbab8efeac84918311eebc25f0b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7204201 Commit-Queue: Samuel Groß <saelo@chromium.org> Auto-Submit: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#103960} | 7 个月前 | |
[base] Clean up Vector construction and conversion Allow converting Vector<T> and Vector<const T> to Vector<const U> if T* converts to const U* and T and U have the same size. As long as we do not write to the U pointer, this is safe. And we cannot write because we only allow this for const U*. Also audit Vector construction and remove unneeded casts and redundant template arguments, sometimes by switching to VectorOf`. R=jkummerow@chromium.org Change-Id: I76cfa7328ac5adc210fbe1c662716968ca58ecf8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5913528 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Samuel Groß <saelo@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#96566} | 1 年前 | |
[platform] Rename Call[Blocking/LowPriority]OnWorkerThread() to PostTaskOnWorkerThread PostTaskOnWorkerThread takes a priority argument, instead of exposing multiple methods. CallOnWorkerThread is kept around because Chrome codebase has a call to it that needs to be switched. It will be removed in a follow-up. This should address https://chromium-review.googlesource.com/c/v8/v8/+/5952524 Change-Id: Ie45941b6996737a7ef04994c32dfa775717f4aa3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5350692 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/main@{#97426} | 1 年前 | |
[tagged] Make FreeSpace a HeapObjectLayout Bug: 42202654 Change-Id: I2c5d1a69d9bf0272b631e3fa7964026f3ccded11 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6596552 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#100564} | 1 年前 | |
[test] Move cctest/test-traced-value to unittests/tracing/ ... traced-value-unittest. Bug: v8:12781 Change-Id: I0da3b38c12a1c1f39e47ddde9b266ff0249715bb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3675897 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: 王澳 <wangao.james@bytedance.com> Cr-Commit-Position: refs/heads/main@{#80795} | 4 年前 | |
[heap] Use task with kUserVisible priority instead of idle task This CL switches from idle tasks to kUserVisible tasks for "context disposal" GCs. @etiennep thankfully notices that this can improve JS score quite a bit. As we have no guarantee when this task will be run after being scheduled, we use gc_count() to only trigger a GC if no GC has been performed in-between. For idle tasks we limit this based on time, the task had to run within two frames (=16ms*2). Unlike idle tasks the regular tasks don't get a deadline, instead we use a hard coded limit of 5ms. In addition to the previous condition, we only perform the GC if the estimated time for it is less than 5ms. This CL improves JS2 by about +0.7%, JS3 by about +0.2%. Bug: 460477160 Change-Id: I9d084d59dca53a57d5cb6e81f26c122f037f15f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6734023 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#104016} | 7 个月前 | |
enable jitfort for memory w^x protection Signed-off-by: zzhengxiang <zhengxiang27@h-partners.com> | 25 天前 | |
[zone] Clean up ZoneAllocator This CL cleans up the implementations of ZoneAllocator and RecyclingZoneAllocator, removing redundant or deprecated things and aligning with C++ >= 11. It also adds tests to verify that both these allocators can be used with standard C++ containers. Change-Id: I245b39d2bd39f7fbbf7b5a589a973701314d9861 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4866420 Reviewed-by: Anton Bikineev <bikineev@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#90007} | 2 年前 | |
[sandbox] Test detection of invalid bytecode In crrev.com/c/7203123 we added abort_with_sandbox_violation and use it when executing an invalid bytecode. This CL now adds a unit test to ensure that execution of invalid bytecode is correctly detected as a sandbox violation crash. Bug: 461681036 Change-Id: Iaa52a2f3664dfbab8efeac84918311eebc25f0b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7204201 Commit-Queue: Samuel Groß <saelo@chromium.org> Auto-Submit: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#103960} | 7 个月前 | |
third_party: Move siphash - Move src/third_party/siphash to third_party/siphash Bug: 383356859 Change-Id: Ic910a07d9790a71283ed2ed3c14c95276a85f79c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6091599 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#97770} | 1 年前 | |
[fuzztest] Enable the FuzzTest framework in V8's unit tests This enables FuzzTest (https://github.com/google/fuzztest) in V8 to write parameterized tests or simple fuzzers for running later on ClusterFuzz. For more details, see the internal design doc (go/v8-fuzztest). This enables three modes of compilation and running tests: - FuzzTest has no effect, v8_enable_fuzztest=false - FuzzTest runs as GTest, v8_enable_fuzztest=true - Centipede build, like before with use_centipede=true On unsupported configurations, FuzzTest is off, while on supported ones, FuzzTest runs like GTest, enabling smoke-testing the fuzzers. The Centipede mode is used to upload to Clusterfuzz, where fuzz tests will run with coverage feedback enabled. The centipede build uses the v8_fuzztests group target and dynamically creates executable wrappers for all fuzz tests during compilation. All wrappers will be stored in the fuzztests/ directory in the build output. FuzzTest is off when V8 is embedded and won't have any effect on the shipped build. However, since it's on on most stand-alone configurations, we unconditionally include the fuzz-test dependencies. We only conditionally include boringssl, since this is only required for the Centipede build. This CL also adds one demo example of a parameterized test using an existing V8 unit test with a test fixture class. We also provide two probe-testing fuzz-test puzzles, which will be used to demonstrated error discovery on Clusterfuzz. Bug: chromium:1500944 Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_dbg Change-Id: I27fca07abf523c532cbce3e4dfa1cffbf8f11526 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5003626 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#92105} | 2 年前 | |
Test that heap-inl.h doesn't include windows.h In order to avoid namespace pollution and compilation overhead it is desirable to avoid include windows.h, and this enforces that. Bug: chromium:796644 Change-Id: I7fdcd3c182a77cee03672bc4324b9e21566896d6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3223960 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/main@{#77404} | 4 年前 | |
[fuzztest] Enable the FuzzTest framework in V8's unit tests This enables FuzzTest (https://github.com/google/fuzztest) in V8 to write parameterized tests or simple fuzzers for running later on ClusterFuzz. For more details, see the internal design doc (go/v8-fuzztest). This enables three modes of compilation and running tests: - FuzzTest has no effect, v8_enable_fuzztest=false - FuzzTest runs as GTest, v8_enable_fuzztest=true - Centipede build, like before with use_centipede=true On unsupported configurations, FuzzTest is off, while on supported ones, FuzzTest runs like GTest, enabling smoke-testing the fuzzers. The Centipede mode is used to upload to Clusterfuzz, where fuzz tests will run with coverage feedback enabled. The centipede build uses the v8_fuzztests group target and dynamically creates executable wrappers for all fuzz tests during compilation. All wrappers will be stored in the fuzztests/ directory in the build output. FuzzTest is off when V8 is embedded and won't have any effect on the shipped build. However, since it's on on most stand-alone configurations, we unconditionally include the fuzz-test dependencies. We only conditionally include boringssl, since this is only required for the Centipede build. This CL also adds one demo example of a parameterized test using an existing V8 unit test with a test fixture class. We also provide two probe-testing fuzz-test puzzles, which will be used to demonstrated error discovery on Clusterfuzz. Bug: chromium:1500944 Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_dbg Change-Id: I27fca07abf523c532cbce3e4dfa1cffbf8f11526 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5003626 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#92105} | 2 年前 | |
[fuzztest] Enable the FuzzTest framework in V8's unit tests This enables FuzzTest (https://github.com/google/fuzztest) in V8 to write parameterized tests or simple fuzzers for running later on ClusterFuzz. For more details, see the internal design doc (go/v8-fuzztest). This enables three modes of compilation and running tests: - FuzzTest has no effect, v8_enable_fuzztest=false - FuzzTest runs as GTest, v8_enable_fuzztest=true - Centipede build, like before with use_centipede=true On unsupported configurations, FuzzTest is off, while on supported ones, FuzzTest runs like GTest, enabling smoke-testing the fuzzers. The Centipede mode is used to upload to Clusterfuzz, where fuzz tests will run with coverage feedback enabled. The centipede build uses the v8_fuzztests group target and dynamically creates executable wrappers for all fuzz tests during compilation. All wrappers will be stored in the fuzztests/ directory in the build output. FuzzTest is off when V8 is embedded and won't have any effect on the shipped build. However, since it's on on most stand-alone configurations, we unconditionally include the fuzz-test dependencies. We only conditionally include boringssl, since this is only required for the Centipede build. This CL also adds one demo example of a parameterized test using an existing V8 unit test with a test fixture class. We also provide two probe-testing fuzz-test puzzles, which will be used to demonstrated error discovery on Clusterfuzz. Bug: chromium:1500944 Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_dbg Change-Id: I27fca07abf523c532cbce3e4dfa1cffbf8f11526 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5003626 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#92105} | 2 年前 | |
[fuzztest] Make error messages distinct on probing bugs The Clusterfuzz crash analysis groups cases that are too similar. To avoid this from happening to our internal fake probing bugs, this makes their error message more distinct. Bug: 346939884 Change-Id: I3cd2a20ece001e24719c4f9dc28177ff3f3921dd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5625700 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Alexander Schulze <alexschulze@chromium.org> Commit-Queue: Alexander Schulze <alexschulze@chromium.org> Cr-Commit-Position: refs/heads/main@{#94461} | 2 年前 | |
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 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[test] Move cctest/{test-bignum-dtoa, test-dtoa ... ,test-fast-dtoa, test-fixed-dtoa} to unittests/base/ {bignum-dtoa-unittest, dtoa-unittest, fast-dtoa-unittest, fixed-dtoa-unittest}. This CL also moves cctest/{gay-fixed, gay-precision, gay-shortest} to unittest/{gay-fixed, gay-precision, gay-shortest}. Bug: v8:12781 Change-Id: Id6072f92908ad3abfe683c69dac041227de2553f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3607114 Commit-Queue: 王澳 <wangao.james@bytedance.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80572} | 4 年前 | |
[fuzztests] Run list_fuzz_tests relative to V8 src dir ... to allow the v8_unittests binary to find the bytecode golden files relative to the source directory. Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_centipede_compile_rel Change-Id: I611db52b148458de6548bb1e63ee87201efd89e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6917678 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#102267} | 9 个月前 | |
[fuzztest] Fix corpus_data requirement Ports https://crrev.com/c/5587876 to V8. No-Try: true Bug: 40941204 Change-Id: I1df208e8fab82f063a421c810e4a1914767bc2db Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5611287 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Alexander Schulze <alexschulze@chromium.org> Commit-Queue: Alexander Schulze <alexschulze@chromium.org> Cr-Commit-Position: refs/heads/main@{#94329} | 2 年前 | |
[sandbox] Activate sandbox hardware support in unittests With this CL, if enabled at compile time we now activate sandbox hardware support at runtime for all unittests. This requires opting out a few unittests that are currently incompatible with hardware sandboxing support, mostly due to the use of signal handlers. Bug: 350324877 Change-Id: Ib6414003abe34f41da5f1d2a3e44544644e812d6 Cq-Include-Trybots: luci.v8.try:v8_linux64_pku_dbg,v8_linux64_pku_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6718196 Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#101392} | 11 个月前 | |
[runtime] Reuse JSFunctions in eval Previously we'd store a native-context specific feedback cell in the eval cache as a way to share info across eval calls (+ sfi of course). This CL changes that to storing the entire JSFunction. When we run the code we'll load the context from the function, and all accesses to the context go through that. This means that the JSFunction[[context]] only needs to be correct on the initial call. So we can reuse the JSFunction and swap the context right before we run eval. Functions that are called are tracked in Call feedback though, so we need to make sure to break consuming that feedback. Otherwise the optimizing compiler might inline whatever context it sees on the function it tracked as the canonical context for that function. This CL updates the heap broker to ignore providing feedback for script-top-level functions (function literal id 0). Change-Id: I0d7aeb654fe9b4e03b6a9922b29078261cce99c3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6556163 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#100334} | 1 年前 | |
[handles] Migration to direct handles, part 4 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 directories: test. Bug: 42203211 Change-Id: Ie9fb3d5b3c66ea9ffa0092d928256aa3891c9a9a Cq-Include-Trybots: luci.v8.try:v8_linux64_css_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5622011 Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#94378} | 2 年前 | |
[testing] Generalize bytecode expectation tests for flags The bytecode expectation generator is changed from having a hardcoded elide redundant tdz checks boolean to a generic extra flags string. This allows any flag to be set for a bytecode expectation test. The SaveFlags RAII helper is moved from test/unittests to src/flags to be used by the generator. Change-Id: Ib88abfbc1be91121c87a17d926adf85b1d61ac50 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6909215 Reviewed-by: Patrick Thier <pthier@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102221} | 9 个月前 | |
[sandbox] Don't allow to use disabled builtins, pt.1 ... i.e. the ones that belong to features that are not currently enabled. This CL adds machinery that ensures that a newly added builtin is either mandatory JS language builtin (always enabled and available) or forces developer to update Builtins::GetJSBuiltinState() accordingly. This machinery is not yet used for disabling builtins for real. Drive-by: fix AccessorTest.WrapFunctionTemplateSetNativeDataProperty test. Bug: 435630464 Change-Id: I04629f9584c5f8be3c4ecbd2eb939da4fa1bc503 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7003082 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#102905} | 9 个月前 | |
[heap] Enable Scavenger chaos mode on bots and fuzzers Bug: 450045070 Change-Id: Iad52fcf2e40cdb7d0ce4f22159b0551268a82cbb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7046422 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#103239} | 8 个月前 | |
un-skip GenerationSizesFromHeapSize on ppc Test was fixed by http://crrev.com/c/7079327 . Change-Id: Id24acd73970227a97016da045df08a9a62929ca1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7158875 Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@ibm.com> Cr-Commit-Position: refs/heads/main@{#103752} | 7 个月前 | |
[fuchsia][v8_unittests] migrate v8_unittests.cmx to .cml Replace v8_unittests.cmx with v8_unittests.cml, thus migrating the tests to CFv2. Bug: chromium:1256503 Change-Id: Iab90b406973585a513bce5a1a0884860c7c88e90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3826050 Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Wez <wez@chromium.org> Commit-Queue: Derek Gonyeo <dgonyeo@google.com> Cr-Commit-Position: refs/heads/main@{#82692} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 7 个月前 | ||
| 3 年前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 25 天前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 25 天前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 9 个月前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 10 天前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 7 个月前 | ||
| 25 天前 | ||
| 2 年前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 8 个月前 | ||
| 7 个月前 | ||
| 3 年前 |