| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Add DIR_METADATA files to v8. Generate DIR_METADATA files and remove metadata from OWNERS files for v8. R=jkummerow@chromium.org, ochang@chromium.org, yangguo@chromium.org Bug: chromium:1113033 Change-Id: I82cbb62e438d82dbbc408e87120af39fa9da0afa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2476680 Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Auto-Submit: Edward Lesmes <ehmaldonado@chromium.org> Cr-Commit-Position: refs/heads/master@{#70669} | 5 年前 | |
Add DIR_METADATA files to v8. Generate DIR_METADATA files and remove metadata from OWNERS files for v8. R=jkummerow@chromium.org, ochang@chromium.org, yangguo@chromium.org Bug: chromium:1113033 Change-Id: I82cbb62e438d82dbbc408e87120af39fa9da0afa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2476680 Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Auto-Submit: Edward Lesmes <ehmaldonado@chromium.org> Cr-Commit-Position: refs/heads/master@{#70669} | 5 年前 | |
Use current isolate implicitly in assert scopes The per-isolate assert scopes always need to operate on the current isolate anyway, so instead of passing it as a parameter add a second constructor which just uses the current isolate implicitly. R=leszeks@chromium.org Bug: 396607238 Change-Id: I9dfde11e7ed1d0594c4912ed19c894ac43c63429 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6578641 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#100485} | 1 年前 | |
Use current isolate implicitly in assert scopes The per-isolate assert scopes always need to operate on the current isolate anyway, so instead of passing it as a parameter add a second constructor which just uses the current isolate implicitly. R=leszeks@chromium.org Bug: 396607238 Change-Id: I9dfde11e7ed1d0594c4912ed19c894ac43c63429 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6578641 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#100485} | 1 年前 | |
Use FlagValue::value() in SLOW_DCHECK Previously SLOW_DCHECK used the non-constexpr bool() operator of FlagValue, which cannot be used in constexpr. Switch to FlagValue::value() instead for make it compile in constexpr. Change-Id: I3e4f70d82c0027cf56999b6c4639479606151696 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4341495 Reviewed-by: Jakob Linke <jgruber@chromium.org> Commit-Queue: Joyee Cheung <joyee@igalia.com> Cr-Commit-Position: refs/heads/main@{#86611} | 3 年前 | |
TicketNo: AR20260205242358 Description: enable jitfort for memory w^x protection Team: OTHERS Feature or Bugfix: Feature Binary Source: No PrivateCode(Yes/No):No Change-Id: I8d4400f57dfa19993aa1fd8fa2ac4376f6abda71 Reviewed-by: z30069899 Approved-by: y00500721 Merged-on: https://open.codehub.huawei.com/OpenSourceCenter_CR/openharmony-tpc/chromium_v8/-/change_requests/531 Merged-by: public pjenkins Signed-off-by: s00502827 <shulin3@huawei.com> revert merge request: AR20260205242358 enable jitfort for memory w^x protection cdaa8cb6bdc83221f0b8d98f7f9da30c11ad5036 This revert merge request !458 | 1 个月前 | |
[base] Switch MemoryProtectionKey API to use PagePermissions enum ... instead of the PageAllocator equivalent. The PagePermissions enum class is newer and we'd like to eventually replace the PageAllocator with the VirtualAddressSpace API. This change also prepares for a follow-up change that allows setting a PKEY on a VirtualAddressSubspace, in which case the space will ensure that all pages in it use its pkey. Bug: 40643847, 350324877 Change-Id: I5b75ccd0aa27bfa7ac8be4aa88bae11283df2197 Cq-Include-Trybots: luci.v8.try:v8_linux64_pku_dbg,v8_linux64_pku_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6657960 Reviewed-by: Stephen Röttger <sroettger@google.com> Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#100952} | 1 年前 | |
Sparkplug+: support patchable baseline code A bytecode handler for an operation is often a generic handler that deal with different types of inputs. This make the baseline compiler to generate a call to a generic builtin for that operation. The generic builtin can deal with all types of inputs, but this makes the builtin very large and introduces a lot of branches to distinguish inputs' types, which hurts the performance. Sparkplug+ introduces some small and specific handlers to deal with one single type of input. For example, this CL introduces some small monomorphic handlers for builtin LoadIC to deal with one specific kind of IC. We will patch the baseline code to use these specific handlers on IC misses dynamically. Bug: chromium:429351411 Change-Id: I85f842ae4050eebbdd8d25d5e113deae743c95d0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6627216 Commit-Queue: Xu, Hao A <hao.a.xu@intel.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103495} | 7 个月前 | |
TicketNo: AR20260205242358 Description: enable jitfort for memory w^x protection Team: OTHERS Feature or Bugfix: Feature Binary Source: No PrivateCode(Yes/No):No Change-Id: I8d4400f57dfa19993aa1fd8fa2ac4376f6abda71 Reviewed-by: z30069899 Approved-by: y00500721 Merged-on: https://open.codehub.huawei.com/OpenSourceCenter_CR/openharmony-tpc/chromium_v8/-/change_requests/531 Merged-by: public pjenkins Signed-off-by: s00502827 <shulin3@huawei.com> revert merge request: AR20260205242358 enable jitfort for memory w^x protection cdaa8cb6bdc83221f0b8d98f7f9da30c11ad5036 This revert merge request !458 | 1 个月前 | |
platform: Provide hooks for disabling allocation quarantining Some performance sensitive paths in V8 (compilation/json parsing) or paths with high allocation/freeing throughput can suffer from not being able to reuse recently freed allocations. These paths can also significantly increase the working set and cause large number of page faults. For such paths (at least as an initial measure) we are planning to disable allocation quarantining. The CL provides a way for the embedder to hook in *Scan functions that disable/enable quarantining. It also disables *Scan for json parsing and compilation jobs. Bug: chromium:1249550 Change-Id: I0274f66010435f3d4d091fe70fabcd20f46dc0d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3306389 Auto-Submit: Anton Bikineev <bikineev@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/main@{#78178} | 4 年前 | |
[runtime][api] Relax requirements for setter/definer/deleter callbacks Previously V8 expected these callbacks to throw TypeError exception on failure depending on v8::PropertyCallbackInfo<T>::ShouldThrowOnError(). The embedders wasn't always doing it right anyway. This CL removes the requirement to handle ShouldThrowOnError() - it's enough to set the result to false and V8 will do the rest (throw TypeError with some default error message depending on the operation). Drive-by: advance deprecation of v8::ReturnValue<void>::Set(Local<S>). Bug: 348688196 Change-Id: If0245e3b5c8bd2cd6a012d3d4cfb4d07e0622d12 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7168624 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#103833} | 7 个月前 | |
Reland "[maglev][optimizer] Constant fold int32 operations" Bug: 424157317 Change-Id: I6c3b3362357dde2171338c22b74f00ceda7e23fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6947931 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#102492} | 9 个月前 | |
[isolate-groups] Make TrustedRange per isolate group. Previously, all isolate groups in a process shared a single 4 GB TrustedRange. This both limited the number of isolate groups per process and allowed trusted objects to be visible across sandboxes, creating security concerns. This change allocates a dedicated TrustedRange for each isolate group and simplifies the single-cage mode code path. Bug: 42204573 Change-Id: I33be0f5a2aeb38c74fafc91b01792ae8f6e8f2ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6818342 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Dmitry Bezhetskov <dima00782@gmail.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102009} | 10 个月前 | |
[isolate-groups] Make TrustedRange per isolate group. Previously, all isolate groups in a process shared a single 4 GB TrustedRange. This both limited the number of isolate groups per process and allowed trusted objects to be visible across sandboxes, creating security concerns. This change allocates a dedicated TrustedRange for each isolate group and simplifies the single-cage mode code path. Bug: 42204573 Change-Id: I33be0f5a2aeb38c74fafc91b01792ae8f6e8f2ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6818342 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Dmitry Bezhetskov <dima00782@gmail.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102009} | 10 个月前 | |
[isolate-groups] Make TrustedRange per isolate group. Previously, all isolate groups in a process shared a single 4 GB TrustedRange. This both limited the number of isolate groups per process and allowed trusted objects to be visible across sandboxes, creating security concerns. This change allocates a dedicated TrustedRange for each isolate group and simplifies the single-cage mode code path. Bug: 42204573 Change-Id: I33be0f5a2aeb38c74fafc91b01792ae8f6e8f2ef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6818342 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Dmitry Bezhetskov <dima00782@gmail.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102009} | 10 个月前 | |
[cleanup] Move ScopedModification to a common place, remove duplicate logic Change-Id: I300a8357bf620b3c485f486e17cf70317a695199 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6734243 Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#101422} | 11 个月前 | |
[cfi] Use VirtualAddressSubspace with PKEY for cfi-related pointer tables In https://crrev.com/c/6657446 we introduced the ability to set a PKEY on a VirtualAddressSubspace, which then guarantees that all its pages are protected by that key. With this CL we now use this mechanism for our pkey-protected pointer tables. This probably fixes a bug where previously, the pkey protection was lost for segments that were decommitted/freed (and then reallocated) as that will replace the page with a fresh page (without a pkey) under the hood. Change-Id: I7321ff207a573a4c042a57dc5f8038404719c753 Cq-Include-Trybots: luci.v8.try:v8_linux64_pku_dbg,v8_linux64_pku_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6759891 Reviewed-by: Stephen Röttger <sroettger@google.com> Commit-Queue: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#101476} | 11 个月前 | |
[segmented-table] Disable segments pool if pages can be too large The segments pool can only be used if we have 16Kb allocation granularity. On OSs where the page size can be configured larger we have to disable it, since it is currently not runtime configurabe. Fixed: 425634685 Change-Id: If77e46b034fc2e324d7eabf19eff54958ea6f7cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6973467 Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Commit-Queue: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#102700} | 9 个月前 | |
[code health] Ban std::bit_cast, use base::bit_cast instead base::bit_cast has some additional checks, so use that exclusively. Replace a few pointer-casts by reinterpret_casts instead. R=leszeks@chromium.org, machenbach@chromium.org Bug: 445301908, 40947442 Change-Id: Ib9f711cf4e786cfbf01883a8e9e4883e57e1ea51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6959216 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#102601} | 9 个月前 | |
[common] Switch to local-exec for TLS variables on ChromeOS After eco_wlcs got removed in https://crbug.com/393184696, we can also force local-exec for TLS variables in V8 on ChromeOS. Bug: 336738728 Change-Id: I4bdf5be82a16631cf1a55fa00e87502f4fe47d16 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6252977 Reviewed-by: Anton Bikineev <bikineev@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#98633} | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 5 年前 | ||
| 5 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 个月前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 1 个月前 | ||
| 4 年前 | ||
| 7 个月前 | ||
| 9 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 1 年前 |