| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[cleanup] Fix inl header includes We have many inl headers which either do not include their non-inl header, or are including other headers first. Both can lead to compile errors because definitions of inline functions might not be visible in inl headers. This CL adds a script to fix those includes, and runs it over the whole code base. R=leszeks@chromium.org Change-Id: I1b7b04c59e5a5b89308512bfc40729f7ec4afc38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6387805 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#99453} | 1 年前 | |
Add mfloat_abi flag - Add mfloat_abi flag. - Move use_eabi_hardfloat from macro-assember-arm to assembler-arm. Change-Id: I8d66209d8e40d2467754c4218921109f8bac99e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6934205 Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#102408} | 9 个月前 | |
[codegen] Split constant pool code for arm64, ppc, and riscv This is purely a refactoring, shuffling code around. No functional changes have been made to the code. The biggest downside to this change is that the code shared between arm64 and riscv have been copied to their respective header files. This is entirely intentional as the riscv parts are about to change to make use of the fact that we're not using 32 bit entries. Change-Id: Ia73e06f5d647428a307540aa19bb1bf252f05e1b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6974673 Commit-Queue: Kasper Lund <kasperl@rivosinc.com> Reviewed-by: Milad Farazmand <mfarazma@ibm.com> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102693} | 9 个月前 | |
Reland "[CFI] Use WritableJitAllocation for relocation writes" This is a reland of commit 26bd78bfdf901b35940ec5088955a6d58d0d1e91 Fix: add V8_EXPORT_PRIVATE to the functions that moved to .cc. Unfortunately, I couldn't test it, since the bot returns an infra failure. Original change's description: > [CFI] Use WritableJitAllocation for relocation writes > > Perform all writes happening as part of relocations in RWX memory > through the WritableJitAllocation object as this is the bottleneck > where we'll apply JIT validation in the future. > > Bug: 42203297 > Change-Id: I0774c5255bfa95692cd6632c6556bd46eacc9d1b > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5952847 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Stephen Röttger <sroettger@google.com> > Cr-Commit-Position: refs/heads/main@{#96764} Bug: 42203297 Change-Id: I3a897f6e632840e5dea4a25ebd323c89c3bd11e0 Cq-Include-Trybots: luci.v8.try:v8_win_arm64_compile_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5952936 Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Stephen Röttger <sroettger@google.com> Cr-Commit-Position: refs/heads/main@{#96773} | 1 年前 | |
Reland "[compiler] Handle deopt in the fast API" 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 Change-Id: I8fd8fe49db98c48e325c1084d2b08fc093f8f88d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6578320 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#100439} | 1 年前 | |
Upstream Cobalt changes in cpu These are the changes Cobalt currently has in V8's cpu related code. - Add missing Starboard CPU code - Replace some V8_OS_WIN with V8_TARGET_OS_WIN, they are found when cross-compiling for Linux platforms on Windows Bug: v8:10927 Change-Id: Id63ae8614cbe6fe0eb53df89060c8ca2c9969ef4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2963803 Commit-Queue: John Xu <johnx@google.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#75318} | 4 年前 | |
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 个月前 | |
Reland "[compiler] Handle deopt in the fast API" 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 Change-Id: I8fd8fe49db98c48e325c1084d2b08fc093f8f88d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6578320 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#100439} | 1 年前 | |
[cleanup][arm] Remove kR9Available This has been in the codebase for at least 15 years: https://github.com/v8/v8/commit/43d26ecc3563a46f62a0224030667c8f8f3f6ceb If there was a platform using it as described in the comment, we would probably have found by now. If such platform appears in the future, there is no guarantee that the code would work with hR9Available=0, since this has never been tested. Change-Id: I9c8cd1dbcf70400495848b2a97fdd14c2f049deb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4618109 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#88283} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 1 年前 | ||
| 3 年前 |