| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[ptr-compr] Remove OnHeapAddress from Decompress Since we're using a global cage, we never need an OnHeapAddress for decompressing pointers. Remove this unused parameter. Change-Id: Ie14a7284c1e793c0b9e146a4e57f981a2985de27 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6481261 Commit-Queue: Leszek Swirski <leszeks@chromium.org> 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@{#99866} | 1 年前 | |
Fix array out of bound trap in supportsSTFLE http://crrev.com/c/7065731 has enabled -fsanitize=array-bounds which is now causing a 100% failure on s390x native test runs. This loop doesn't seem to be checking the bounds correctly and causes OOB traps. Change-Id: Ibdca8002d336165db92b117c869a6ff07b084246 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7076802 Reviewed-by: Junliang Yan <junyan1@ibm.com> Commit-Queue: Milad Farazmand <mfarazma@ibm.com> Cr-Commit-Position: refs/heads/main@{#103315} | 8 个月前 | |
[maglev] Properly clear state on failures Fixed: 439769607 Change-Id: Ia540ce656311aba7f7e4e28f2adec8dd0773fe7a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6875820 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#102012} | 10 个月前 | |
[CFI] Use WriteUnalignedValue when Memory<> isn't used Drive-by: - use jit_allocation under set_uint32_constant_at - use FlushInstructionCache with jit_allocations Change-Id: Ie0a9eee6e5c912b755ded501352ff63c72e79bff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5966555 Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#96840} | 1 年前 | |
PPC/s390: [compiler] Handle deopt in the fast API Port 6ec26945cdb9064a6c6835a7c638092f344e6a89 Original Commit Message: This is a reland of commit 3da1691dd7f64aa5514b1765f12f3900d030fa0c The original CL opened a WritableJitAllocation scope in the deoptimizer before calling PatchToJump to allow modifying generated code on M1. However, this scope caused problems with pkeys on x64. This CL now opens an RwxMemoryWriteScope inside the arm64 implementation of PatchToJump to avoid the problem. The original CL opened a WritableJitAllocation scope in the deoptimizer before calling PatchToJump to allow modifying generated code on M1. However, this scope caused problems with pkeys on x64. This CL now opens an RwxMemoryWriteScope inside the arm64 implementation of PatchToJump to avoid the problem. Original change's description: > [compiler] Handle deopt in the fast API > > Deopt with fast API is different than normal deopts in the following ways: > 1) Normal deopts (without CFI) patch the return address on the stack to return to the deopt trampoline; with fast API calls, the generated code is patched to jump to the deopt trampoline after returning from the fast call; > > 2) With CFI, the generated code also gets patched, but for fast calls the jump is not patched right after the return address, but after the code that restores the stack pointer. > > 3) The DeoptimizationEntry_LazyAfterFastCall builtin has to check and handle pending exceptions before tail-calling to DeoptimizationEntry_Lazy. > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6532354 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/main@{#100421} BYPASS_LARGE_CHANGE_WARNING R=ahaas@chromium.org, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: Ie64d358542297ebd77c578ee00a5138f416b4f93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6580220 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#100460} | 1 年前 | |
S390x: remove support for s390 32-bit, part 1 s390 has been out of support for a long time now. This CL removes the following from v8 codebase: - V8_TARGET_ARCH_S390 - V8_HOST_ARCH_S390 - V8_TARGET_ARCH_S390_LE_SIM - v8_current_cpu == "s390" - arch == s390 Change-Id: I97d4cafe0be65c91c872466b94dd835f695aaeab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5857023 Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by: Junliang Yan <junyan@redhat.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#96110} | 1 年前 | |
Reland^2 "Embedding feedback in BytecodeArray for StrictEqual" This is a reland of commit e295f1f18da01c386eda73f535fb67a56c004d88 Original change's description: > Reland "Embedding feedback in BytecodeArray for StrictEqual" > > This is a reland of commit f0fed41e48b1966e3e565ae278d018da538ef123 > > Original change's description: > > Embedding feedback in BytecodeArray for StrictEqual > > > > This CL removes the feedback vector slot for StrictEqual and stores its feedback values directly in the BytecodeArray. Optimized compilers will now access the type feedback from the BytecodeArray. > > > > Before: > > 75 04 00 TestEqualStrict a1, [0] > > > > After: > > 75 04 00 00 TestEqualStrict a1, #0 > > > > This change saves moemory by reducing FeedbackVector size, and is part of the Sparkplug+ optimization effort. > > > > Bug: chromium:429351411 > > Change-Id: I24390811c12755b0a19beaefe2b0319d75ceaf6c > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6986847 > > Reviewed-by: Xu, Hao A <hao.a.xu@intel.com> > > Commit-Queue: Wei, Yuheng <yuheng.wei@intel.com> > > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#103656} > > Bug: chromium:429351411 > Change-Id: I77286b0e9c65f8a9e257a2125adab7f68fe09aec > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7148333 > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Commit-Queue: Wei, Yuheng <yuheng.wei@intel.com> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/main@{#103800} Bug: chromium:429351411 Change-Id: I5020c9dffbed90ff207520728b13cf0dbcfb5903 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7197099 Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Wei, Yuheng <yuheng.wei@intel.com> Cr-Commit-Position: refs/heads/main@{#103962} | 7 个月前 | |
[cleanup] remove remnants of V8_ENABLE_LEAPTIERING Change-Id: I3c8c4bceced1cd09ee13fe9c91a3de7d80132e58 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7130698 Commit-Queue: Dan Carney <dcarney@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#103626} | 7 个月前 | |
[cleanup] remove remnants of V8_ENABLE_LEAPTIERING Change-Id: I3c8c4bceced1cd09ee13fe9c91a3de7d80132e58 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7130698 Commit-Queue: Dan Carney <dcarney@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Olivier Flückiger <olivf@chromium.org> Cr-Commit-Position: refs/heads/main@{#103626} | 7 个月前 | |
PPC/s390: [compiler] Handle deopt in the fast API Port 6ec26945cdb9064a6c6835a7c638092f344e6a89 Original Commit Message: This is a reland of commit 3da1691dd7f64aa5514b1765f12f3900d030fa0c The original CL opened a WritableJitAllocation scope in the deoptimizer before calling PatchToJump to allow modifying generated code on M1. However, this scope caused problems with pkeys on x64. This CL now opens an RwxMemoryWriteScope inside the arm64 implementation of PatchToJump to avoid the problem. The original CL opened a WritableJitAllocation scope in the deoptimizer before calling PatchToJump to allow modifying generated code on M1. However, this scope caused problems with pkeys on x64. This CL now opens an RwxMemoryWriteScope inside the arm64 implementation of PatchToJump to avoid the problem. Original change's description: > [compiler] Handle deopt in the fast API > > Deopt with fast API is different than normal deopts in the following ways: > 1) Normal deopts (without CFI) patch the return address on the stack to return to the deopt trampoline; with fast API calls, the generated code is patched to jump to the deopt trampoline after returning from the fast call; > > 2) With CFI, the generated code also gets patched, but for fast calls the jump is not patched right after the return address, but after the code that restores the stack pointer. > > 3) The DeoptimizationEntry_LazyAfterFastCall builtin has to check and handle pending exceptions before tail-calling to DeoptimizationEntry_Lazy. > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6532354 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/main@{#100421} BYPASS_LARGE_CHANGE_WARNING R=ahaas@chromium.org, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: Ie64d358542297ebd77c578ee00a5138f416b4f93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6580220 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#100460} | 1 年前 | |
PPC/s390: [codegen] Change RegList into a class Port 8a0d1b6fe5874d6645da3719d1ccce9b15df18b9 Original Commit Message: Modernise the RegList interface to be a proper class, rather than a typedef to an integer, and add proper methods onto it rather than ad-hoc bit manipulation. In particular, this makes RegList typesafe, adding a DoubleRegList for DoubleRegisters. The Arm64 CPURegList isn't updated to use (or extend) the new RegList interface, because of its weird type-erasing semantics (it can store Registers and VRegisters). Maybe in the future we'll want to get rid of CPURegList entirely and use RegList/DoubleRegList directly. R=leszeks@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I997156fe4f4f2ccc40b2631d5cb752efdc8a5ad2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3525084 Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#79484} | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 8 个月前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 4 年前 |