- 21 Jun, 2022 3 commits
-
-
Jakob Kummerow authored
This is a reland of commit 15f372af Change since revert: TSan fix for tier-up budget reset. Original change's description: > [wasm] Fix tier-up budget tracking for recursive calls > > In the previous implementation, functions overwrote any budget > decrements caused by recursive invocations of themselves, which > could cause tier-up decisions for certain unlucky functions to > get delayed unreasonably long. > This patch avoids this by working with the on-instance value > directly instead of caching it in a stack slot. That generates > the same amount of Liftoff code as the status quo, but handles > recursive functions properly. > The "barista3" benchmark's peak performance improves by almost 20%. > > Bug: v8:12281 > Change-Id: I8b487a88da99c2d22e132f2cc72bdf36aa5f6e63 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3693710 > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/main@{#81249} Bug: v8:12281,v8:12984 Change-Id: Ia6ce776848dc86617546ec514660c9a840484cb1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3716479Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#81281}
-
Liu Yu authored
Port commit b84c7dbd Bug: chromium:1337221 Change-Id: I5f64995df3e0660740ef3915625373e1f147bc70 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3715957 Auto-Submit: Liu Yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#81269}
-
Michael Achenbach authored
This reverts commit 15f372af. Reason for revert: https://crbug.com/v8/12984 Original change's description: > [wasm] Fix tier-up budget tracking for recursive calls > > In the previous implementation, functions overwrote any budget > decrements caused by recursive invocations of themselves, which > could cause tier-up decisions for certain unlucky functions to > get delayed unreasonably long. > This patch avoids this by working with the on-instance value > directly instead of caching it in a stack slot. That generates > the same amount of Liftoff code as the status quo, but handles > recursive functions properly. > The "barista3" benchmark's peak performance improves by almost 20%. > > Bug: v8:12281 > Change-Id: I8b487a88da99c2d22e132f2cc72bdf36aa5f6e63 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3693710 > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/main@{#81249} Bug: v8:12281, v8:12984 Change-Id: Ie254236785628c07ac569de16ea82a67ed5bd221 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3714247 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Owners-Override: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#81267}
-
- 20 Jun, 2022 1 commit
-
-
Jakob Kummerow authored
In the previous implementation, functions overwrote any budget decrements caused by recursive invocations of themselves, which could cause tier-up decisions for certain unlucky functions to get delayed unreasonably long. This patch avoids this by working with the on-instance value directly instead of caching it in a stack slot. That generates the same amount of Liftoff code as the status quo, but handles recursive functions properly. The "barista3" benchmark's peak performance improves by almost 20%. Bug: v8:12281 Change-Id: I8b487a88da99c2d22e132f2cc72bdf36aa5f6e63 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3693710 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#81249}
-
- 07 Jun, 2022 1 commit
-
-
Liu Yu authored
Port commit e50d19cb Bug: v8:11708 Change-Id: Ia9a8cb9d8cd9e768fc056bc5555959e0aaeb3694 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3692435Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu Yu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80974}
-
- 06 Jun, 2022 1 commit
-
-
Liu Yu authored
Port commit a52b44f0 Bug: v8:12908 Change-Id: Ifcafab2f29d416f39fa48082e86c3c3b72508bad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3690453 Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu Yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80952}
-
- 02 Jun, 2022 2 commits
-
-
Clemens Backes authored
We should not use kSimd, which has already shipped. Instead, use a new kRelaxedSimd bailout reason. R=thibaudm@chromium.org Bug: chromium:1324081 Change-Id: I394e288014245ed9ae69e20f811f8cf7555e6149 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3686413Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80913}
-
Liu Yu authored
Port commit 3ac47847 Bug: v8:12284 Change-Id: I231e189514b5ed143b9299155938026f94ab3840 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3685484 Auto-Submit: Liu Yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80907}
-
- 20 May, 2022 1 commit
-
-
Liu Yu authored
LLd and Scd should be used for StoreType::kI64Store* types. Change-Id: Ic645c9149c7ade95e0a36acadb48d246ee817469 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3655179 Auto-Submit: Yu Liu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80657}
-
- 19 May, 2022 1 commit
-
-
Liu Yu authored
Port commit 0236d7b5 Bug: v8:12284 Change-Id: I8ce66d3e4d61e8cc446364fbc1b1ba7d6036fca7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3653715 Auto-Submit: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80628}
-
- 17 May, 2022 1 commit
-
-
Liu Yu authored
Port commit d2a8bdec Bug: v8:12284 Change-Id: Ia011008d1e7695601fce78d60018e473079e9d0f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3650332 Auto-Submit: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80574}
-
- 13 May, 2022 1 commit
-
-
Clemens Backes authored
Now that we require C++17 support, we can just use the standard static_assert without message, instead of our STATIC_ASSERT macro. R=leszeks@chromium.org Bug: v8:12425 Change-Id: I1d4e39c310b533bcd3a4af33d027827e6c083afe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3647353Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80524}
-
- 12 May, 2022 1 commit
-
-
Liu Yu authored
Port commit fe443a4e Bug: v8:12284 Change-Id: I242c4161ecff09fd7bcfeda27560a6c881c87d09 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3641034 Auto-Submit: Yu Liu <liuyu@loongson.cn> Commit-Queue: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80483}
-
- 06 May, 2022 1 commit
-
-
Thibaud Michaud authored
R=clemensb@chromium.org CC=gdeepti@chromium.org Bug: v8:12284 Change-Id: Ied63b2c7b57210f2cf2e1580520405ce1be5dc33 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3625979Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#80400}
-
- 20 Apr, 2022 2 commits
-
-
Thibaud Michaud authored
R=clemensb@chromium.org CC=gdeepti@chromium.org Bug: v8:12284 Change-Id: Idddb0b7648b29612fa0308520ca2fc2a3e5647f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3593218Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#80055}
-
Thibaud Michaud authored
R=clemensb@chromium.org CC=gdeepti@chromium.org Bug: v8:12284 Change-Id: If78b5a86364b015483131ef321ca9e928e8ddfc1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3585338Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#80047}
-
- 09 Apr, 2022 1 commit
-
-
Liu Yu authored
Port commit 9ca0bfef Bug: v8:12166 Change-Id: I39708d61f823b4ef12ab5aac6b030eff89517b16 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3579870 Auto-Submit: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#79901}
-
- 08 Apr, 2022 1 commit
-
-
Thibaud Michaud authored
Rename element_size_bytes() to value_kind_size(), and add the uncompressed version: value_kind_full_size(). R=clemensb@chromium.org Change-Id: I956142937fd1134ecbdaaa617c402ed8fff2cf17 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3568477Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#79884}
-
- 06 Apr, 2022 1 commit
-
-
Clemens Backes authored
The 'ForRegs' method is not needed for clarity of the code, it's pretty clear what to construct a register list from. Hence turn the static {LiftoffRegList::ForRegs} method into a constructor. This makes the code more concise. Also, turn the for loop into a C++17 folding expression, which might generate better code because the loop will automatically be unrolled. R=thibaudm@chromium.org Bug: v8:12425 Change-Id: Ic4446f23022db5f17420303d45b9c15fa5daff60 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3572041Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79815}
-
- 16 Mar, 2022 1 commit
-
-
Clemens Backes authored
In text, we should use the properly capitalized "Wasm" instead of "WASM". In particular for frame output, other frames typically use CamelCase (like "JsToWasmFrame", "ExitFrame", "InternalFrame"), so Wasm should do the same. The "0xa" comment in some assemblers is also outdated, the current tag we emit for StackFrame::WASM is 0x8 (0x4 shifted by one). R=jkummerow@chromium.org Bug: v8:12425 Change-Id: Ic3e00c401b219c28b5424c82efb0f1a9df51690f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3525195Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79498}
-
- 11 Mar, 2022 1 commit
-
-
Liu Yu authored
Change-Id: I4378e4f99c6b034f7b29782218896d5485178109 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3514656 Auto-Submit: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#79452}
-
- 24 Feb, 2022 1 commit
-
-
Liu Yu authored
Port commit c7e47c30 Bug: v8:7700 Change-Id: I59d5e483867118fa8efc50cc52e00bd3321fa01a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3487428 Auto-Submit: Yu Liu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#79245}
-
- 03 Feb, 2022 1 commit
-
-
Clemens Backes authored
On all platform, the method is implemented identical to {LoadInstanceFromFrame}. So remove {FillInstanceInto} and keep {LoadInstanceFromFrame} which is a better name. R=thibaudm@chromium.org Bug: v8:12425 Change-Id: Ia9e6a3e2478628f8d31ff4faaab8d5250fda7796 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3429203Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#78924}
-
- 01 Feb, 2022 1 commit
-
-
Clemens Backes authored
The 32-bit value is zero-extended to pointer size, which is a no-op on 32-bit systems. The operation changes nothing about the signedness of the value, so the old name was a bit misleading. We also provide one unified no-op implementation for all 32-bit systems. R=thibaudm@chromium.org Bug: v8:10949, chromium:1281995 Change-Id: Id04641fe793155ea98bf878b6789e4afce3da7df Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3424493Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#78881}
-
- 31 Jan, 2022 1 commit
-
-
Manos Koukoutos authored
Since inheritance depth of every type is known in the isorecursive hybrid type system, rtts with depth are removed. This enables simplification of type checks in Liftoff and Turbofan, as well as decoding of object allocation instructions. Bug: v8:7748 Change-Id: I6b52579b584191d92644de1c6e805d9f054641d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3422626Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78860}
-
- 02 Nov, 2021 1 commit
-
-
Zhao Jiazhong authored
Port commit 7a93bd64 Change-Id: I3d1793154b1d69fcc0dcde7b7d731cbbb326f05d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3255208 Auto-Submit: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
Liu yu <liuyu@loongson.cn> Commit-Queue: Liu yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#77635}
-
- 08 Oct, 2021 1 commit
-
-
Liu Yu authored
Port: 9d3c9d47 Bug: v8:7748 Change-Id: Id2fbd5c8dd5be1ea1932f48c03657f636bfb28bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3213351Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu yu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#77293}
-
- 02 Sep, 2021 1 commit
-
-
Liu Yu authored
Besides, fix an error in set_if_nan, because if src is a NaN, we should set the i32 instead of i64 at address dst to a non-zero value. Port e6961df2 Bug: v8:11856 Change-Id: Icc9afda35d4cca4fd5ae82356ecaec77bf92d009 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3139055Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#76636}
-
- 12 Aug, 2021 1 commit
-
-
Thibaud Michaud authored
Make "emit_s128_set_if_nan" take LiftoffRegisters rather than Registers. The decoding of the FP register code is architecture dependent, and in particular we expect an FP pair on arm. R=clemensb@chromium.org Bug: v8:11856 Change-Id: I44a364c3ef3a0c41000ea1f6cead4916ee04145d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3089165Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#76246}
-
- 05 Aug, 2021 1 commit
-
-
Liu Yu authored
Port 9e0e2c15 Bug: v8:12017 Change-Id: Ie722834291a3e23a391da741b17f84f3179bcdaf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3070386 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#76107}
-
- 28 Jul, 2021 2 commits
-
-
Liu Yu authored
Port 593fbb69 Bug: v8:12017 Change-Id: I0776820d0ab51950028da347d9d7d08acfb30386 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058652 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75955}
-
Liu Yu authored
Port edc349db Bug: v8:11235 Change-Id: Ie3cfadf97afcea4048c20bc1a5646f4e3c2a82ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3058061Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75950}
-
- 23 Jul, 2021 1 commit
-
-
Clemens Backes authored
Handle large frames by doing an explicit check to see if there is enough remaining stack space before the stack limit. The bailout which can be removed then is being triggered on more than 1 percent of all functions, so this is expected to improve compile time by several percent, because we avoid the costly TurboFan compilation for those >1%. R=ahaas@chromium.org Bug: v8:11235 Change-Id: I935998f7676647572598b52c989f7d41cc5239a8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3046180 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#75897}
-
- 06 Jul, 2021 1 commit
-
-
Liu Yu authored
Port: 6f48b7b3 Bug: v8:11856 Change-Id: I1828e307caa55a31090e09b6e24b3d6317fdf6fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3007176 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75579}
-
- 24 Jun, 2021 1 commit
-
-
Liu Yu authored
Port: e699762e Bug: v8:11856 Change-Id: Ib832dfcee864b21b4e56498fca54e9ae01c44ae7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983711 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75350}
-
- 10 Jun, 2021 1 commit
-
-
John Xu authored
For Cobalt's purpose in the past, we introduced base::Memcpy to intercept memcpy calls and replace it with SbMemoryCopy on Starboard/Cobalt. Recently Cobalt removed SbMemoryCopy because we found out that memcpy implementation is universal. To reduce the cost to maintain base::Memcpy, let us remove it and revert back to raw memcpy. Bug: v8:10927 Change-Id: I060f191f8f1aed8b78ffe4558a3743f3a2da008b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951462Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: John Xu <johnx@google.com> Cr-Commit-Position: refs/heads/master@{#75070}
-
- 03 Jun, 2021 1 commit
-
-
Liu Yu authored
Port 2b77ca20 Bug: v8:11809 Change-Id: Idbbbc10d1339d6c8463686b6e701fb601a217cab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2931557Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/master@{#74934}
-
- 01 Jun, 2021 1 commit
-
-
Camillo Bruni authored
Various behaviour preserving changes that make it easier to switch on callee-saved registers without having to land refactoring code at the same time. - Use MaybeStoreRegisters / MaybeRestoreRegisters - Use CallRecordWriteStubSaveRegisters everywhere for now. Eventually this will be replaced by CallRecordWriteStub in places with fixed registers. - Use WriteBarrierDescriptor::ComputeSavedRegisters, which for now returns the same as allocatable_registers Full x64 implementation: https://crrev.com/c/2922604 Bug: v8:11420 Change-Id: I04e6ac2f6333edc91cb1030a0217f59ad441a1d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2922250Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#74876}
-
- 19 May, 2021 1 commit
-
-
Camillo Bruni authored
Inline the RememberedSetAction and SaveFPMode flags directly into the RecordWrite stubs: - Save two register for input arguments - Avoid branches in the RecordWrite stubs We end up with 2 stubs for the EphemeronKeyBarrier and 4 stubs for RecordWrite. Due to more inlined calls we have roughly 1KiB more builtins code for RecordWrite currently. We will address this in the future by splitting out common code into a separate stub. There is no additional code size overhead for EphemeronKeyBarrier. This saves 4 to 8 bytes on x64 per RecordWrite call and 2.5% sparkplug code size reduction on d3.min.js. Bug: v8:11420 Change-Id: Ib7170265dd6dd4b3aaf8275083f096e76fae8251 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2902731Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#74661}
-
- 13 May, 2021 1 commit
-
-
Wenyu Zhao authored
Change-Id: I16872f90a10702c3dcc8e556a8bc17fd63a0f858 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2881511Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Wenyu Zhao <wenyu.zhao@anu.edu.au> Cr-Commit-Position: refs/heads/master@{#74553}
-