| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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] Change roots to be COMMON_OWNERS No-Try: true Change-Id: I2c12d7dd135363ad33a44fff71731d705ace730a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5797116 Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#95712} | 1 年前 | |
[wasm] Reduce includes in wasm-module.h and includes of it Change-Id: Icb44a603f83811ae3cba445d824850e6e3f46f59 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6519540 Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Daniel Lehmann <dlehmann@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#100128} | 1 年前 | |
[hole] Add strict hole subtypes ... and make Hole a trivial HeapObjectLayout type. This required renaming Uninitialized and Exception to UninitializedHole and ExceptionHole (respectively), to avoid name conflicts. Bug: 434179415, 42202654 Change-Id: I78e4f85bc31a7ff9b1cbfca820307c649df49552 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6842396 Reviewed-by: Igor Sheludko <ishell@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#101882} | 10 个月前 | |
[v8] Fix CVE-498095290 495751197 497404188 TicketNo: DTS2026041307131 Description: [v8] Fix CVE Team:gitcode Feature or Bugfix: Binary Source: sync from gitcode PrivateCode(Yes/No):No Change-Id: I0685a6966e3fe17da7b8bb20d56b9699d170e9ba Reviewed-by: z30069899,y00500721 Approved-by: y00500721 Merged-on: https://open.codehub.huawei.com/OpenSourceCenter_CR/openharmony-tpc/chromium_v8/-/change_requests/552 Merged-by: public pjenkins Signed-off-by: gaojunyu <gaojunyu2@h-partners.com> revert merge request: DTS2026041307131 [v8] CVE-498095290 495751197 497404188 8ac5be1238b0a137cdb8cbe2561e68832faedf46 This revert merge request !454 | 1 个月前 | |
[heap] Make hole maps readable even when unmapped Previously, all hole objects were placed inside a payload of the WasmNull object so that they would be fully unmapped, including their map pointer, making it a requirement to check them by value instead of by instance type. This is proving to be a difficult restriction to adhere to, particularly in optimized code (where reading the map is considered a somewhat operation and can be hoisted above hole checks). This patch refactors this by making each Hole object a large, page-minus-map-aligned object, with a readable map and its own unmappable payload. Since they are in their own area, we can revert the WasmNull to its previous single-payload layout, since it doesn't need to store the holes in its unmappable payload. We can also uncouple hole unmapping from Wasm being enabled. This unfortunately blows up the (virtual) size of the RO space, in particular requiring it to expand to multiple V8 pages. Bug: 434179415 Change-Id: Id64b1a3f1228e621590058661d33eca72604fe5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7156717 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@{#103929} | 7 个月前 | |
[heap] Make hole maps readable even when unmapped Previously, all hole objects were placed inside a payload of the WasmNull object so that they would be fully unmapped, including their map pointer, making it a requirement to check them by value instead of by instance type. This is proving to be a difficult restriction to adhere to, particularly in optimized code (where reading the map is considered a somewhat operation and can be hoisted above hole checks). This patch refactors this by making each Hole object a large, page-minus-map-aligned object, with a readable map and its own unmappable payload. Since they are in their own area, we can revert the WasmNull to its previous single-payload layout, since it doesn't need to store the holes in its unmappable payload. We can also uncouple hole unmapping from Wasm being enabled. This unfortunately blows up the (virtual) size of the RO space, in particular requiring it to expand to multiple V8 pages. Bug: 434179415 Change-Id: Id64b1a3f1228e621590058661d33eca72604fe5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7156717 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@{#103929} | 7 个月前 | |
[heap] Make hole maps readable even when unmapped Previously, all hole objects were placed inside a payload of the WasmNull object so that they would be fully unmapped, including their map pointer, making it a requirement to check them by value instead of by instance type. This is proving to be a difficult restriction to adhere to, particularly in optimized code (where reading the map is considered a somewhat operation and can be hoisted above hole checks). This patch refactors this by making each Hole object a large, page-minus-map-aligned object, with a readable map and its own unmappable payload. Since they are in their own area, we can revert the WasmNull to its previous single-payload layout, since it doesn't need to store the holes in its unmappable payload. We can also uncouple hole unmapping from Wasm being enabled. This unfortunately blows up the (virtual) size of the RO space, in particular requiring it to expand to multiple V8 pages. Bug: 434179415 Change-Id: Id64b1a3f1228e621590058661d33eca72604fe5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7156717 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@{#103929} | 7 个月前 | |
[heap] Make hole maps readable even when unmapped Previously, all hole objects were placed inside a payload of the WasmNull object so that they would be fully unmapped, including their map pointer, making it a requirement to check them by value instead of by instance type. This is proving to be a difficult restriction to adhere to, particularly in optimized code (where reading the map is considered a somewhat operation and can be hoisted above hole checks). This patch refactors this by making each Hole object a large, page-minus-map-aligned object, with a readable map and its own unmappable payload. Since they are in their own area, we can revert the WasmNull to its previous single-payload layout, since it doesn't need to store the holes in its unmappable payload. We can also uncouple hole unmapping from Wasm being enabled. This unfortunately blows up the (virtual) size of the RO space, in particular requiring it to expand to multiple V8 pages. Bug: 434179415 Change-Id: Id64b1a3f1228e621590058661d33eca72604fe5f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7156717 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@{#103929} | 7 个月前 | |
[hole] Move all holes together for range-checked IsAnyHole Bug: 434179415, 42202654 Change-Id: Iae52a520ecfa69542b3451eaa2ab41e21e44a56f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6845797 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#102017} | 10 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 10 个月前 | ||
| 1 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 10 个月前 |