- 25 Feb, 2022 14 commits
-
-
jameslahm authored
The per-Isolate Symbol tables are implemented using NameDictionary before, which has additional property details overhead And NameDictionary is limited to 2^23, which limits the Symbol tables to be a maximum of 2^23. - replace NameDictionary with SymbolTable in isolate Bug: v8:12575 Change-Id: Ica4f05aac3494f7dfa3a074c240d4ba25df814e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3476897Reviewed-by:
Shu-yu Guo <syg@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#79285}
-
Toon Verwaest authored
The helper function removes a register from the list and returns it Bug: v8:7700 Change-Id: I3f9fe9d30113b9e6c7362dc8443e39ae3d1adf07 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488372Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#79284}
-
Clemens Backes authored
When checking whether to merge a region with its surrounding regions in {InsertIntoWritableRegions}, we did not check first whether the determined {insert_pos} is within the vector. We were thus accessing (reading) after the end of the vector. The bug only happened on MSVC builds, suggesting that clang deterministically read a value which is never equal to the end of the new region, whereas for MSVC it sometimes happened that we read exactly the {region.end()} value, and we tried to merge regions. R=jkummerow@chromium.org Bug: v8:12643 Change-Id: If30d910ed6e996f7b0e1d8c5b439c3d842a498f6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487988Reviewed-by:Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79283}
-
Clemens Backes authored
R=manoskouk@chromium.org Change-Id: I6db42a8d851ccccf262be05feb0a7d90369cb78c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487990Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79282}
-
Michael Lippautz authored
This is a reland of 4fde3328 Another Blink-related test fix landed, see chromium:1300492. Original change's description: > heap: Force incremental marking in C++ only workloads > > ... when above a certain minimum threshold. This is to guard against > memory running away in scenarios where the JS heap is empty and > there's only high throughput C++ allocations that don't allow for a > memory reducer GC to kick in. > > This logic should be revisited after Oilpan's young generation > collector is implemented which may allow switching to a more efficient > shrinking strategy for initial heap setup. > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79255} Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: Ida66e0c944094472b4856d5fecef2d199d29549b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487991 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Clemens Backes authored
The {index} argument to {Peek} is unused. Other {Peek} methods use it to generate the error message, but {Peek} without expected type does not type check anything so it stays unused. R=manoskouk@chromium.org Change-Id: I979063f707f7305987220d6c192db7e679d930ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3490930Reviewed-by: -
Camillo Bruni authored
- Avoid handle derefs where possible - Split off PostProcessNewJSReceiver to avoid additional instance-type checks - Precompute should_rehash_ to avoid additional branches in PostProcessNewObject Bug: v8:12195 Change-Id: Ib80e711ced48b9b43072ada4e7ed72eb11ab0b8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3270537Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#79279}
-
Toon Verwaest authored
Instead of scanning the array of registers, keep an explicit list of free registers. Stack slots are equally changed to use an std::vector of free slots instead of a linked list. Now we only need to scan - the list of free registers when we want to allocate a specific register, - and scan the list of allocated registers to see if the free value is already in a different register, - scan the list of allocated registers to free some register if we don't have enough registers (for input, output, or temp). Bug: v8:7700 Change-Id: Iff41b06aae656b59e4ed25e9066671a21660a73e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3489487Reviewed-by:
-
Michael Lippautz authored
This reverts commit fe822dc9. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Blink%20Linux%20Debug/13306/overview Original change's description: > Reland "heap: Force incremental marking in C++ only workloads" > > This is a reland of 4fde3328 > > Two issues in Blink tests have been fixed before this reland. > > Original change's description: > > heap: Force incremental marking in C++ only workloads > > > > ... when above a certain minimum threshold. This is to guard against > > memory running away in scenarios where the JS heap is empty and > > there's only high throughput C++ allocations that don't allow for a > > memory reducer GC to kick in. > > > > This logic should be revisited after Oilpan's young generation > > collector is implemented which may allow switching to a more efficient > > shrinking strategy for initial heap setup. > > > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > > Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319 > > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#79255} > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > Change-Id: I6cd4a4d358bc1a78f2f001ed50dd9bb3f376f49e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488370 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79274} Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: If325d40455f433b7910b68b24bb1cf84337f177a No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488373 Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#79277}
-
Clemens Backes authored
Instead of returning false and failing in the caller, do fail inside the PageAllocator directly. Failure to free pages should never happen, and handling this case in the PageAllocator directly gives us better options to surface more detailed information in follow-up patches. R=mlippautz@chromium.org Bug: v8:12656, chromium:1299735 Change-Id: I6d2aa3a5613c0f1102210fccbccc6ad0e522a6ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484323Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79276}
-
Patrick Thier authored
mjsunit/compiler/deopt-pretenure.js is flaky due to --gc-interval in some variants. The flag can cause a variable to be promoted to old space before the test can force allocation site pretenuring for that variable, which is essential for the test case. Bug: v8:12652 Change-Id: If7239deaa3026bb781d3ee96df28a1bbf3a5b6f1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488371 Auto-Submit: Patrick Thier <pthier@chromium.org> Reviewed-by:
-
Michael Lippautz authored
This is a reland of 4fde3328 Two issues in Blink tests have been fixed before this reland. Original change's description: > heap: Force incremental marking in C++ only workloads > > ... when above a certain minimum threshold. This is to guard against > memory running away in scenarios where the JS heap is empty and > there's only high throughput C++ allocations that don't allow for a > memory reducer GC to kick in. > > This logic should be revisited after Oilpan's young generation > collector is implemented which may allow switching to a more efficient > shrinking strategy for initial heap setup. > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79255} Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: I6cd4a4d358bc1a78f2f001ed50dd9bb3f376f49e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488370Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/icu: https://chromium.googlesource.com/chromium/deps/icu/+log/901474b..1fa4e39 Build a CPP file with ICU data for WASM. (Harry Terkelsen) https://chromium.googlesource.com/chromium/deps/icu/+/1fa4e39 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,ftang@chromium.org Change-Id: I2f7b33496c3c6011d4b9b9909f54225116f0d262 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488700 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#79273}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/9a383ac..9e7c4ed Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/08a8050..57a228b Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/36d41ce..6b28c1d Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/4823a85..27dbe48 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ifafecb9a393a62a4e66c97d92a135619a2280525 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3488697 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#79272}
-
- 24 Feb, 2022 26 commits
-
-
Milad Fa authored
During `WasmDebugBreak` we push the full 128-bit vector register instead of only the 64-bit FP value. As a result offset calculation must use kSimd128Size instead of kDoubleSize. Change-Id: Icaa44d9663024b9740acbbf054f6c334ae349cf8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487958Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#79271}
-
Jakob Kummerow authored
For creating and unpacking the wrapper objects we currently use for WasmGC <-> JavaScript interop, we must read the Context from the "WasmApiFunctionRef" rather than from the "instance_node_". As a bonus, this patch also slightly improves generated code for wasm-to-js wrappers by moving conditionally needed code to labels (previously it was always executed but the results only conditionally used). Fixed: v8:12640 Change-Id: I55485cdb6a402f32ddc42ec6316dcbe23f1fcccb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3489486 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Junliang Yan authored
Change-Id: Iebe587955aad8445cd22598a3e2930ca9444e792 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484702Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#79269}
-
Toon Verwaest authored
- First inputs are walked to update next_use and collect dead inputs - If any dead values were collected, clear them from the registers - Finally free the LiveNodeInfo from values_. Bug: v8:7700 Change-Id: I4ae78820d4405470e73d3ec89948e46442286eeb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487786Reviewed-by:
-
Dominik Inführ authored
This is a reland of a1838956 Now that https://crrev.com/c/3485678 landed and fixed the deadlock in the linked bug, we can reland this CL without changes. Original change's description: > [heap] Allow shared references in WeakMap > > Shared references can also be stored in WeakMaps and during marking we > need to be able to deal with such references. In a client GC shared > objects are treated as live, so we don't need to update or check mark > bits for such objects. > > Bug: v8:11708 > Change-Id: I0dbf797472c4779f462750dab63cc9b012aad091 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3447365 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79153} Bug: v8:11708, v8:12642 Change-Id: I5945a16255647c897a1df834267137bf73b6207f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3485679 Auto-Submit: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Shu-yu Guo authored
Bug: v8:12499 Change-Id: I41961dc689ff634fa141c8b15909ca57bdb401cd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3482479 Auto-Submit: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#79266}
-
Clemens Backes authored
{AtomicSub} on x64 first negates the {value} register, then does an atomic addition. For that reason, {value} should be a unique register. So far, we only checked that it's not used in the value stack, but we should also check for overlap with the destination address or the offset register. Drive-by: Remove unneeded handling of non-unique register index on arm, as that cannot happen (LiftoffCompiler ensures that the result register is unique). R=thibaudm@chromium.org Bug: chromium:1296876 Change-Id: Ie6b97eec8e8dea07b0bcc644d261f47467cc5b8e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487987Reviewed-by:Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79265}
-
Nico Hartmann authored
This CL introduces an additional verification pass at the end of SimplifiedLowering. The verification checks consistency of the lowered graph with respect to node types under the effect of used truncations. Typing of additional, lower level nodes is required and added in this CL. The verification pass can be enabled using --verify-simplified-lowering. Bug: v8:12619, v8:11682 Change-Id: I21e7ebcf40153e53108ddfad2a871c7cbd61a085 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3452029Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#79264}
-
Tobias Tebbi authored
This reverts commit 4fde3328. Reason for revert: causes crashes Original change's description: > heap: Force incremental marking in C++ only workloads > > ... when above a certain minimum threshold. This is to guard against > memory running away in scenarios where the JS heap is empty and > there's only high throughput C++ allocations that don't allow for a > memory reducer GC to kick in. > > This logic should be revisited after Oilpan's young generation > collector is implemented which may allow switching to a more efficient > shrinking strategy for initial heap setup. > > Bug: chromium:1029379, chromium:1300028, chromium:1300492 > Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#79255} Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: I15e8d7b37b9f9b6ef4f72968c262a614618f1863 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487970 Auto-Submit: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Owners-Override: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#79263}
-
Michael Lippautz authored
Previously, the interval was max(6, <interval_value>) which was changed to actually consider the value of the flag. Change-Id: Iec3cef19b6ec8528f03c36db6239b044ee90cde1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487969Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#79262}
-
Dominik Inführ authored
We need to park the isolate's main thread before blocking in the semaphore to allow a shared GC to happen in the meantime. Bug: v8:11708, v8:12647 Change-Id: Ide215d2c811caee84663d8749b7d94a414c44bd8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3485678 Auto-Submit: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#79261}
-
Michael Lippautz authored
Avoid going through Heap but rather call it directly on the allocator. Bug: v8:12615 Change-Id: I395b96d08b685c63c4125245a76c3610acf1643b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3485677Reviewed-by:
-
Jakob Gruber authored
Bug: v8:7700 Change-Id: I38251c42a06af554281879613b6424cf65fbbbd1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487967 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Clemens Backes authored
Instead of returning a boolean value, and then failing in the caller via a CHECK, do fail directly inside OS::Free, OS::Release and similar functions. The PageAllocator methods still return a bool (which is always true) to avoid changing the public API. R=mlippautz@chromium.org Bug: v8:12656, chromium:1299735 Cq-Include-Trybots: luci.v8.try:v8_fuchsia_compile_rel Change-Id: Ide02e7d893e1603326c629797a7defac8bf258ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3483671Reviewed-by:
-
Nikolaos Papaspyrou authored
This CL refactors Heap::GCTypeTimer and Heap::GCTypePriorityTimer and moves them to a GCTracer::RecordGCPhasesInfo class. This is a necessary change for deprecating counters that are used for old style GC metrics, like gc_scavenger. When all such counters are deprecated, GCTracer::RecordGCPhasesInfo will no longer be necessary and will be removed. Bug: chromium:1154636 Change-Id: I04504a0f6c7a0955f4300a1c94c969aaeb23b77f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3486556Reviewed-by:
-
Michael Lippautz authored
Keep --gc-interval precise wrt to the # of allocations needed for a GC. Bug: v8:12615 Change-Id: I1ff45ef709013427b5f27643e3a6135dd0f4025d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3485676Reviewed-by:
-
Michael Lippautz authored
... when above a certain minimum threshold. This is to guard against memory running away in scenarios where the JS heap is empty and there's only high throughput C++ allocations that don't allow for a memory reducer GC to kick in. This logic should be revisited after Oilpan's young generation collector is implemented which may allow switching to a more efficient shrinking strategy for initial heap setup. Bug: chromium:1029379, chromium:1300028, chromium:1300492 Change-Id: I93924fc2fe77d6226c29358d3afb1cc9d6fbf3b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484319Reviewed-by:
-
Leszek Swirski authored
Bug: v8:7700 Change-Id: I801b482039b6f8ba19332747a8fee0fcdbcb8764 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487553Reviewed-by:
-
Jakob Gruber authored
- Add a maglev watchlist and add jgruber,leszeks,verwaest. - Remove unused lists csa/interpreter/torque. Bug: v8:7700 Change-Id: Ib2d361fe0af298a39b2dc1d9bd96ff39e7b7c0fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487552 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Camillo Bruni authored
With this change we can easily track and filter unsupported objects for full-page snapshots. Bug: v8:11525 Change-Id: Id75b6f4edf68b47d6dfbe79aed2b686aeec61068 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484320Reviewed-by:
-
Leszek Swirski authored
Bug: v8:7700 Change-Id: I221d77ddc43b5956e0b873900d1e92ec7c037103 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487550 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Maya Lekova authored
Bug: v8:12142 Change-Id: I700bae611cecb8bc26b476e35a1df407efd30331 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487549 Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
R=machenbach@chromium.org Change-Id: I9866742528d47210d39fcdeda522dcf29bdba38e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3486679Reviewed-by:
-
Clemens Backes authored
{FreePages} is never expected to fail, and each caller wraps the call in a CHECK macro. In order to learn more about failures, this CL moves the CHECK inside of {::FreePages}, to fail whenever the {PageAllocator} fails to free pages. As a next step, I'll audit our {PageAllocator} implementations to ensure that none of them return {false} for {FreePages}. Note that this is already the case for the gin platform (chromium). R=mlippautz@chromium.org Bug: v8:12656, chromium:1299735 Change-Id: Ib61be6cc8da0110ead2db1ad005728bd061e0243 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3484321Reviewed-by: -
Leszek Swirski authored
Maglev is mid-tier optimising compiler designed mainly for compilation speed that can still generate good code for straightforward JS. This initial commit is an MVP for Maglev which can compile and run some very simple code, and sets up a framework that we can build upon. Design: https://docs.google.com/document/d/13CwgSL4yawxuYg3iNlM-4ZPCB8RgJya6b8H_E2F-Aek/edit# Bug: v8:7700 Change-Id: I5ae074ae099126c2c0d50864ac9b3d6fa5c9e85a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3483664Reviewed-by:
-
Tobias Tebbi authored
Bug: v8:12655 Change-Id: I1ae4d546b7232fe30f716c5a9913f895637761f0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487546 Auto-Submit: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
