- 28 Jun, 2021 5 commits
-
-
Patrick Thier authored
With batch compilation, tracing messages for OSR were wrong and misleading. Since we can trace when and where we enter baseline code with other flags (--trace-unoptimized) we can remove tracing for baseline OSR. Bug: v8:11420 Change-Id: I72483c9262b7009652664739b692fd32bd936e20 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988403 Auto-Submit: Patrick Thier <pthier@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#75405}
-
Victor Gomes authored
- Creates v8root to reconcile support with blaze - Adds -m32 flag for 32 bit architectures No-Try: true Bug: v8:11234 Change-Id: I1c0b68b92922ee00cbfb960625c7be62445f636a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987834Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/master@{#75404}
-
Victor Gomes authored
No-Try: true Bug: v8:11234 Change-Id: I82a066bfc395718f1b295f52785600aaa34604e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985402 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
-
Lu Yahan authored
Change-Id: Id9820ec6f21a08a5437bc847d7199e12f1daedf0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2992391 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: Ji Qiu <qiuji@iscas.ac.cn> Reviewed-by:
Ji Qiu <qiuji@iscas.ac.cn> Cr-Commit-Position: refs/heads/master@{#75402}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/f8a6922..aeb5c9d Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/a73eec2..2a6dffa Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/49e7cd9..6274a55 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I41c53f201fa84ea686de969ab5bcffd0402d18a4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2992318Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#75401}
-
- 27 Jun, 2021 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/d3674b9..f8a6922 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: If692309f6319c56bba94e58f4c55ba08a7c88a3e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2991853Reviewed-by:
-
- 26 Jun, 2021 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/9dc1297..d3674b9 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/46bcd59..82a4d60 Rolling v8/buildtools/linux64: git_revision:d924640c25f9d90386716116a53957f24d709042..git_revision:4d207c94eab41f09c9a8505eb47f3d2919e47943 Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx/+log/8fa8794..79a2e92 Rolling v8/third_party/aemu-linux-x64: JZYvEBpGNCDNOK3uLHlpKn_AN6roNsL0YVup96egRSEC..A1XxYDWVeZi3lNSg1lZdcmGtIB2fA0XTIPYdevon60YC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/a2a4ced..11a2ddf Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/cf60c0a..a73eec2 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/098695c..49e7cd9 Rolling v8/tools/luci-go: git_revision:2adc53281f4a72ecb71e84a8af5acc0fced04cc9..git_revision:8ed83b4afa51020c8900d121bb57624b35882dec Rolling v8/tools/luci-go: git_revision:2adc53281f4a72ecb71e84a8af5acc0fced04cc9..git_revision:8ed83b4afa51020c8900d121bb57624b35882dec Rolling v8/tools/luci-go: git_revision:2adc53281f4a72ecb71e84a8af5acc0fced04cc9..git_revision:8ed83b4afa51020c8900d121bb57624b35882dec TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I9b820d261ef642c5bbd53b331c24e0757389a585 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2989108Reviewed-by:
-
- 25 Jun, 2021 24 commits
-
-
Milad Fa authored
Change-Id: I57c6989ff0ca872b66567c701c2b9bf8ee6e83d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983069 Commit-Queue: Milad Fa <mfarazma@redhat.com> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#75398}
-
Junliang Yan authored
Change-Id: I36000eaafd18b9eca8d302d977ad8e2f1205af35 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2989137 Auto-Submit: Junliang Yan <junyan@redhat.com> Reviewed-by:
Milad Fa <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#75397}
-
Igor Sheludko authored
... implications of not having Code pointers in the non-code spaces anywhere except CodeDataContainer objects. Tbr: jgruber@chromium.org Bug: v8:11880 Change-Id: Ide7482bd5a95776de50f8d94adaefb078b611d6e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987837Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#75396}
-
Igor Sheludko authored
StoreICs use slow handler for now. Bug: v8:11804 Change-Id: I008fc9a3639f649b63881f759078e664b16e25e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985403Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#75395}
-
Andreas Haas authored
R=jkummerow@chromium.org Bug: v8:11879 Change-Id: Ie0f748d78dd62d881dd4e97f9e2be19ef5a7bca9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987830 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
-
Clemens Backes authored
This reverts commit 3161106e. Reason for revert: Breaks layout tests (missing handle scope): https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Blink%20Linux/12278/overview Original change's description: > [wasm] Initialize compilation progress before compilation units > > Initializing the compilation progress first, and making it an explicit > step, allows us to share the wrapper compilation code between async > compilation and streaming compilation. In the future it will also allow > us to initialize compilation units based on the compilation progress, > which will allow us to share more code between async compilation and > deserialization. > > R=clemensb@chromium.org > > Bug: v8:11862 > Change-Id: If8394f3068840f759b8325ba806549dbd208f195 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2978258 > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75380} Bug: v8:11862 Change-Id: I05fa906a86ba8d3226356bcda99786a4a82e6374 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988416 Auto-Submit: Clemens Backes <clemensb@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#75393}
-
Leszek Swirski authored
In case we find that Sparkplug benefits require short builtin calls, add a --sparkplug-needs-short-builtins flag to make the former depend on the latter. Change-Id: I5b23abbd9ad6e0d11d7033497d5755f08c2ab876 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988753 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
This just moves the existing algorithm, and translates it from Handle<BigInt> to Digits as underlying data format. Bug: v8:11515 Change-Id: Ieefee4e953e14f4c574aebab94d825ddb7c31f8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2975304 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#75391}
-
Milad Fa authored
Newly added test under https://crrev.com/c/2987824 needs to be skipped on unsupported platforms. Change-Id: Ib5d222c09726cd63328ea894c3e6ea7e1e1bd3e5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988361Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#75390}
-
Junliang Yan authored
Change-Id: Iffe01cd3b49aa8b590b4930b3ea94fb52419b83c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985502 Auto-Submit: Junliang Yan <junyan@redhat.com> Reviewed-by:
-
Clemens Backes authored
The cached memory start was not preserved across stack checks in debug code. This only manifests if the stack check is actually executed, hence it's tricky to reproduce. R=ahaas@chromium.org Bug: chromium:1222648 Change-Id: I8d678305022e3521bd457ad49ebed30d81b05231 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987824 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#75388}
-
Mythri A authored
The code and prototype_or_initial_map fields are marked as weak in the torque definition of JSFunction. Given we don't have any annotations that generate BodyDescriptors or the C++ class specifying weak there didn't reflect in the actual C++ implementation. In the C++ implementation we were treating those as strong pointers and the rest of the code also expects them as strong pointers and doesn't actually deal with cleared weak references. Since JSFunction's header doesn't have any weak references we can just fallback to JSObject::BodyDescriptor that iterates through all header fields and the other JSObject fields as strong pointers. This is what was happening because JSFunction didn't have a body descriptor and we were falling back to JSObject::BodyDescriptor So this is a clean up CL to avoid confusion. There shouldn't be any change in behaviour. So this CL basically: 1. Drops weak from the torque definition to match with implementation 2. Changes JSFunction::BodyDescriptor to JSObject::BodyDescriptor when iterating over objects to be consistent with other JSObjects with strong pointers. Change-Id: I7c3e49f1759164a0f2517b3d5b8d0e5169b025ff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987827Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#75387}
-
Victor Gomes authored
No-Try: true Change-Id: I1aee4944bf4b33cb4b1be745bedb88ac63c6d9e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987832Reviewed-by:
Patrick Thier <pthier@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/master@{#75386}
-
Clemens Backes authored
Some flag comments and descriptions contained "Turbofan" instead of "TurboFan". R=ahaas@chromium.org Bug: v8:11879 Change-Id: I7e4c6a8820b6ab31eb2f868641a20004faf7104a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985401Reviewed-by:
-
Patrick Thier authored
- Remove possibility to pass frame to %BaselineOsr (was unused and adds overhead to the normal path) - Arm back edges for OSR of all functions compiled in a batch - Refactoring Bug: v8:11790 Change-Id: Ifb1016935296a172914f99e8b2a1742f618a2be0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2982609Reviewed-by:
-
Clemens Backes authored
Add a code comment for checking the maximum number of steps, and disambiguate the different types of breakpoints. R=thibaudm@chromium.org Change-Id: I9be40461554948a61e81b3f9953cfc4475e52e54 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985400 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#75383}
-
Clemens Backes authored
Most Liftoff code comments are generated by the {NextInstruction} function. That code was inside an "#ifdef DEBUG" block so far, because previously code comments were only enabled in debug builds anyway. Now that we have the separate v8_code_comments gn arg, they can also be enabled in release builds. Hence remove the "#if DEBUG" such that code comments are also output in release mode. This should not introduce any compile time regressions since both macros are no-ops in official builds. R=ahaas@chromium.org Change-Id: I0bdd11534620072ccf0ff959c7f7d658aa75717b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985243 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: -
Victor Gomes authored
Change-Id: I116a25fe586491f1a3aff6a486e69724d82115ac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983207 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by:
-
Andreas Haas authored
Initializing the compilation progress first, and making it an explicit step, allows us to share the wrapper compilation code between async compilation and streaming compilation. In the future it will also allow us to initialize compilation units based on the compilation progress, which will allow us to share more code between async compilation and deserialization. R=clemensb@chromium.org Bug: v8:11862 Change-Id: If8394f3068840f759b8325ba806549dbd208f195 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2978258 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
We would be allowing or disallowing using the local heap rather than that scope. There's one case that remains in common-operator-reducer.cc. Bug: v8:7790 Change-Id: Ice0b407aa37b3aa349fc68f4a7c2644156097e3e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983206Reviewed-by:
-
Clemens Backes authored
The code used to be only enabled in debug mode. Now that we have a separate v8_code_comments gn arg, this is not the case any more. Hence remove the "DEBUG_" prefix from the macro. R=ahaas@chromium.org Change-Id: I60215e3b07d6cb0cee5076136834e4bb5a13355b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2982345Reviewed-by:
-
Clemens Backes authored
We were just printing "Liftoff" in the compiler field, whichout a way to tell if it's Liftoff's debugging code flavour or default Liftoff code. This CL encodes that in the "compiler" field by selecting between "TurboFan", "Liftoff", and "Liftoff (debug)". R=ahaas@chromium.org Change-Id: Ia0c004eab96c0e10e52e81c4e2863dab423124fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985399Reviewed-by:
-
John Xu authored
These changes are found after Cobalt rebased to V8 v8.8. Most changes are grouped into their own CLs and here are the rest. - Replace raw printf with PrintF - Include Starboard as a platform for some implementations - Add some missing headers. This is probably because Cobalt does not compile all of V8 sources so some missing headers are only exposed when compiling Cobalt. Change-Id: Idf1512f57c37c8a63f79b1cf4ffc1da5d08421e2 Bug: v8:10927 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2966197 Auto-Submit: John Xu <johnx@google.com> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: John Xu <johnx@google.com> Cr-Commit-Position: refs/heads/master@{#75376}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/62937f9..1799e1b prefix VLOG (#1187) (Dominic Hamon) https://chromium.googlesource.com/external/github.com/google/benchmark/+/1799e1b prefix macros to avoid clashes (#1186) (Dominic Hamon) https://chromium.googlesource.com/external/github.com/google/benchmark/+/6a5bf08 Move flags inside the `benchmark` namespace (#1185) (Dominic Hamon) https://chromium.googlesource.com/external/github.com/google/benchmark/+/5da5660 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I4e2e782f3ac6d80c2aaacecb3b9825db2d44cef9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2987700Reviewed-by:
-
- 24 Jun, 2021 9 commits
-
-
Victor Gomes authored
No-Try: true Bug: v8:11234 Change-Id: I4099a231ecc5cfb87d74170b04753a8bec2b5cbf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985501Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/master@{#75374}
-
Peter Kasting authored
These indicate when a range-based for loop is using an index whose type (value, pointer, or reference) doesn't match what the loop actually extracts from the range. Fix by matching the actual type better. This shouldn't cause any behavior/performance change, just be slightly clearer about what's actually happening when reading the code. Bug: chromium:1223264 Change-Id: Ib8773fbbeb038609c54a52c7cd6ce5bd11fd99ba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983710Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Victor Gomes authored
- Disables FRIEND_TEST - Removes gtest_prod.h dependency Change-Id: I614f633749f3197989ac4a0d9d5faa6ec03ed59d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2982481Reviewed-by:
-
Victor Gomes authored
No-Try: true Bug: v8:11234 Change-Id: I4339a3a3f3fcffa7c65a569ea36a56be16b1ae45 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985340 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
-
Victor Gomes authored
Bug: v8:11234 No-Try: true Change-Id: Idc8a0d6a513fd38fafb10ff33121e37a79e3a1f3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2985242Reviewed-by:
-
Maya Lekova authored
This CL modifies the underlying storage of PerIsolateAssertScope from a bitfield to separate booleans. This slightly increases the space taken by the isolate, but allows for easier access to the individual fields, which is a prerequisite for implementing assertion scopes in TurboFan. It also refactors the template PerIsolateAssertScope class to separate simple C++ scope classes, defined through macros. Bug: chromium:1218898 Change-Id: Ia5e43352ebba28be6f013376b75f13ec8d5dc972 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2975303 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
-
Dan Elphick authored
This is a reland of 9701d4a4 with a small fix for some code landed in between the dry-run and submission. Original change's description: > [base] Move most of src/numbers into base > > Moves all but conversions.*, hash-seed-inl.h and math-random.* into > base, in preparation for moving the parts of conversions that don't > access HeapObjects. > > Also moves uc16 and uc32 out of commons/globals.h into base/strings.h. > > Bug: v8:11917 > Change-Id: Ife359148bb0961a63833aff40d26331454b6afb6 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2979595 > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> > Auto-Submit: Dan Elphick <delphick@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75354} Bug: v8:11917 Change-Id: Ie1ec9032fe56646a7c7303185cecc70fce5694ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2982607Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#75368}
-
Jakob Kummerow authored
Instead, make the array-allocating builtin initialize the object. This speeds up later stages of Turbofan graph processing, in particular live range computation. Bug: v8:7748 Change-Id: Iba0d682922b444b1d6151eeaee8d939821ebc980 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983457 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#75367}
-
Clemens Backes authored
There is only one global wasm engine, so we do not need to store the pointer in the NativeModule. We just use {GetWasmEngine()} instead, which reads the global pointer. R=jkummerow@chromium.org Bug: v8:11879 Change-Id: I66dedd571755774d96621b8d20ff23bdfef8134f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2983208Reviewed-by:
-
