AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
8fce4f1e0c
v8/tools/v8heapconst.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

646 lines
29 KiB
Python
Raw Normal View History

[py3] Bump v8heapconstants.py and related files Bug: v8:12581 Change-Id: I4d98e48801ffcfbe507c61ba296da67359e3f5cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3568464 Auto-Submit: Alexander Schulze <alexschulze@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Alexander Schulze <alexschulze@chromium.org> Cr-Commit-Position: refs/heads/main@{#79743}
2022-04-04 10:53:50 +00:00
#!/usr/bin/env python3
Remove always-true --harmony-symbol-description runtime flag It shipped in Chrome 70. Bug: v8:7807, v8:8562 Change-Id: I5c5a9fc23656018ee6e9115af7a0c779230e681b Reviewed-on: https://chromium-review.googlesource.com/c/1450787 Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#59589}
2019-02-14 10:00:15 +00:00
# Copyright 2019 the V8 project authors. All rights reserved.
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
# Use of this source code is governed by a BSD-style license that can
# be found in the LICENSE file.
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
Introduce mkgrokdump to update tools/v8heapconst.py. - Migrate make grokdump to GYP and GN - Move code from d8 into stand-alone execution - Add test case to ensure it's up-to-date Review-Url: https://codereview.chromium.org/2809653003 Cr-Original-Original-Commit-Position: refs/heads/master@{#44687} Committed: https://chromium.googlesource.com/v8/v8/+/0cc0c130fa56f129c90c2a74cb01bda85df5e42a Review-Url: https://codereview.chromium.org/2809653003 Cr-Original-Commit-Position: refs/heads/master@{#44710} Committed: https://chromium.googlesource.com/v8/v8/+/477f00557458d383bd9ebef281890ba485ee882a Review-Url: https://codereview.chromium.org/2809653003 Cr-Commit-Position: refs/heads/master@{#44738}
2017-04-20 06:14:53 +00:00
# This file is automatically generated by mkgrokdump and should not
# be modified manually.
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
# List of known V8 instance types.
[runtime] Add ReadOnlyRoots.empty_array_list() - Simplify HeapObject::IsArrayList check - Dehandlify ArrayList initialization - Prevent auto-formatting of v8heapconst.py Change-Id: I9849ad82dae1a2dc671433e8d5eb8ec63ed830c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3447906 Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Auto-Submit: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#79114}
2022-02-15 22:18:48 +00:00
# yapf: disable
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
INSTANCE_TYPES = {
Update heap constants R=ishell@chromium.org BUG= Review-Url: https://codereview.chromium.org/2590923002 Cr-Commit-Position: refs/heads/master@{#41865}
2016-12-20 15:26:08 +00:00
0: "INTERNALIZED_STRING_TYPE",
2: "EXTERNAL_INTERNALIZED_STRING_TYPE",
[grokdump] Update grokdump to decode new map layouts, and dump-heap-constants to 512kb pages BUG= Change-Id: I5e60705764b8ea20b171981cdd44d57a928fa34d Reviewed-on: https://chromium-review.googlesource.com/461178 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#44188}
2017-03-28 08:44:17 +00:00
8: "ONE_BYTE_INTERNALIZED_STRING_TYPE",
10: "EXTERNAL_ONE_BYTE_INTERNALIZED_STRING_TYPE",
Revert "[objects] Remove uncached internal external string type" This reverts commit b3d09001eb012ebf75816f5be51a2b1db47e55f2. Reason for revert: https://chromium-review.googlesource.com/c/v8/v8/+/2565511 has to be reverted, and this was a follow-up to that Original change's description: > [objects] Remove uncached internal external string type > > We shouldn't be creating those anymore since they are not thread-safe. > > Bug: v8:7790 > Change-Id: I4546d995fa32eb076c8dfe9d95301fad719c9e07 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2615347 > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72006} TBR=rmcilroy@chromium.org,leszeks@chromium.org,solanes@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:7790 Change-Id: I4eb1a6b8446fa602eeb5bf29fbf1fe57182cdbf3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2627605 Reviewed-by: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#72122}
2021-01-14 15:12:09 +00:00
18: "UNCACHED_EXTERNAL_INTERNALIZED_STRING_TYPE",
26: "UNCACHED_EXTERNAL_ONE_BYTE_INTERNALIZED_STRING_TYPE",
[cleanup] Remove obsolete "one byte data hint" for strings. In the early days of Chrome when we used WebKit there was no support for ASCII strings on the C++ side, so we put a hint onto these two-byte strings that said "string only contains one byte data", such that internally in V8 when these were involved in string operations, we could instead create the *cheaper* one byte strings. Nowadays Blink properly supports one-byte string representations and this additional hint only comes with overhead, since we check it in quite a few places (i.e. on the hot path for string concatenation), plus we end up consuming more memory due to the additional string maps. Removing the hint also frees one bit in the InstanceType zoo for strings. This alone improves performance on the `bench-dom-serialize.js` test case by around **3%**. Tbr: mstarzinger@chromium.org Bug: v8:6622, v8:8834, v8:8939 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: I0753f2859cee7b5a37b6f0da64d8ec39fcb044ff Doc: https://bit.ly/fast-string-concatenation-in-javascript Reviewed-on: https://chromium-review.googlesource.com/c/1498478 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#60006}
2019-03-04 12:55:22 +00:00
32: "STRING_TYPE",
33: "CONS_STRING_TYPE",
34: "EXTERNAL_STRING_TYPE",
35: "SLICED_STRING_TYPE",
37: "THIN_STRING_TYPE",
40: "ONE_BYTE_STRING_TYPE",
41: "CONS_ONE_BYTE_STRING_TYPE",
42: "EXTERNAL_ONE_BYTE_STRING_TYPE",
43: "SLICED_ONE_BYTE_STRING_TYPE",
45: "THIN_ONE_BYTE_STRING_TYPE",
50: "UNCACHED_EXTERNAL_STRING_TYPE",
58: "UNCACHED_EXTERNAL_ONE_BYTE_STRING_TYPE",
[string] Add a is_shared bit to strings and String::Share The is_shared bit bumps the number of reserved bits for Strings' InstanceType from 6 to 7. This has the side effect of shuffling the InstanceType enum values. There are no users of this bit yet. This is steps 1-2 from the following design doc [1], in preparation for sharing internalized and in-place-internalizable strings. [1] https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit?usp=sharing Bug: v8:12007 Change-Id: Idf11a6035305f0375b4f824ffd32a64f6b5b043b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3266017 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#77831}
2021-11-10 22:42:10 +00:00
96: "SHARED_STRING_TYPE",
Reland "[strings] Support shared external strings" This is a reland of commit d00c040547f22858c1ab724e9db1933c00daccec Changes since revert: Use AsAtomicTagged instead of base::AsAtomicPointer to store a hash value in the forwarding table. Original change's description: > [strings] Support shared external strings> > > With this CL shared strings can be externalized and external strings can > be shared. > The StringForwardingTable is used to delay the real transition to the > next full GC. On the API side strings marked for externalization will > look like externalized strings. > > Bug: v8:12957 > Change-Id: I53b6509129bc5679c06bdf99421bdb41ea5d9082 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3849643 > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Commit-Queue: Patrick Thier <pthier@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82966} Bug: v8:12957 Change-Id: I17715e927e4339240a6aa12a3c4a3c2ea50eb567 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3871211 Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#83018}
2022-09-07 07:24:12 +00:00
98: "SHARED_EXTERNAL_STRING_TYPE",
[string] Make String::MakeThin threadsafe for shared strings For shared strings, String::MakeThin is protected by using the map word of the string being migrated as a spinlock. Note that this CL does not make it safe yet to access character data from multiple threads. The spinlock here only protects write-write races in String::MakeThin. For more information, see the following two design docs: https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit https://docs.google.com/document/d/1Drzigf17t4ofy0evDmaIL5p0MDZuAl95c9fSeX-QjVg/edit Bug: v8:12007 Change-Id: I9c47412c6ec7360a672b65a8576b4f6156ee5846 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3313429 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Patrick Thier <pthier@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78257}
2021-12-06 19:23:51 +00:00
101: "SHARED_THIN_STRING_TYPE",
[string] Add a is_shared bit to strings and String::Share The is_shared bit bumps the number of reserved bits for Strings' InstanceType from 6 to 7. This has the side effect of shuffling the InstanceType enum values. There are no users of this bit yet. This is steps 1-2 from the following design doc [1], in preparation for sharing internalized and in-place-internalizable strings. [1] https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit?usp=sharing Bug: v8:12007 Change-Id: Idf11a6035305f0375b4f824ffd32a64f6b5b043b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3266017 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#77831}
2021-11-10 22:42:10 +00:00
104: "SHARED_ONE_BYTE_STRING_TYPE",
Reland "[strings] Support shared external strings" This is a reland of commit d00c040547f22858c1ab724e9db1933c00daccec Changes since revert: Use AsAtomicTagged instead of base::AsAtomicPointer to store a hash value in the forwarding table. Original change's description: > [strings] Support shared external strings> > > With this CL shared strings can be externalized and external strings can > be shared. > The StringForwardingTable is used to delay the real transition to the > next full GC. On the API side strings marked for externalization will > look like externalized strings. > > Bug: v8:12957 > Change-Id: I53b6509129bc5679c06bdf99421bdb41ea5d9082 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3849643 > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Commit-Queue: Patrick Thier <pthier@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82966} Bug: v8:12957 Change-Id: I17715e927e4339240a6aa12a3c4a3c2ea50eb567 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3871211 Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#83018}
2022-09-07 07:24:12 +00:00
106: "SHARED_EXTERNAL_ONE_BYTE_STRING_TYPE",
[string] Make String::MakeThin threadsafe for shared strings For shared strings, String::MakeThin is protected by using the map word of the string being migrated as a spinlock. Note that this CL does not make it safe yet to access character data from multiple threads. The spinlock here only protects write-write races in String::MakeThin. For more information, see the following two design docs: https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit https://docs.google.com/document/d/1Drzigf17t4ofy0evDmaIL5p0MDZuAl95c9fSeX-QjVg/edit Bug: v8:12007 Change-Id: I9c47412c6ec7360a672b65a8576b4f6156ee5846 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3313429 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Patrick Thier <pthier@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78257}
2021-12-06 19:23:51 +00:00
109: "SHARED_THIN_ONE_BYTE_STRING_TYPE",
Reland "[strings] Support shared external strings" This is a reland of commit d00c040547f22858c1ab724e9db1933c00daccec Changes since revert: Use AsAtomicTagged instead of base::AsAtomicPointer to store a hash value in the forwarding table. Original change's description: > [strings] Support shared external strings> > > With this CL shared strings can be externalized and external strings can > be shared. > The StringForwardingTable is used to delay the real transition to the > next full GC. On the API side strings marked for externalization will > look like externalized strings. > > Bug: v8:12957 > Change-Id: I53b6509129bc5679c06bdf99421bdb41ea5d9082 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3849643 > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Commit-Queue: Patrick Thier <pthier@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82966} Bug: v8:12957 Change-Id: I17715e927e4339240a6aa12a3c4a3c2ea50eb567 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3871211 Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#83018}
2022-09-07 07:24:12 +00:00
114: "SHARED_UNCACHED_EXTERNAL_STRING_TYPE",
122: "SHARED_UNCACHED_EXTERNAL_ONE_BYTE_STRING_TYPE",
[string] Add a is_shared bit to strings and String::Share The is_shared bit bumps the number of reserved bits for Strings' InstanceType from 6 to 7. This has the side effect of shuffling the InstanceType enum values. There are no users of this bit yet. This is steps 1-2 from the following design doc [1], in preparation for sharing internalized and in-place-internalizable strings. [1] https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit?usp=sharing Bug: v8:12007 Change-Id: Idf11a6035305f0375b4f824ffd32a64f6b5b043b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3266017 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#77831}
2021-11-10 22:42:10 +00:00
128: "SYMBOL_TYPE",
129: "BIG_INT_BASE_TYPE",
130: "HEAP_NUMBER_TYPE",
131: "ODDBALL_TYPE",
132: "PROMISE_FULFILL_REACTION_JOB_TASK_TYPE",
133: "PROMISE_REJECT_REACTION_JOB_TASK_TYPE",
134: "CALLABLE_TASK_TYPE",
135: "CALLBACK_TASK_TYPE",
136: "PROMISE_RESOLVE_THENABLE_JOB_TASK_TYPE",
137: "LOAD_HANDLER_TYPE",
138: "STORE_HANDLER_TYPE",
139: "FUNCTION_TEMPLATE_INFO_TYPE",
140: "OBJECT_TEMPLATE_INFO_TYPE",
141: "ACCESS_CHECK_INFO_TYPE",
[runtime] Inline Foreign fields into AccessorInfo ... to avoid additional indirection on every access. Drive-by: given that AccessorInfo class now has a custom body visitor it's no longer necessary to encode flags field as Smi. Bug: v8:12949 Change-Id: I30eabee3cbc5ded2bf3f050dfe22208713a764bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3701590 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#81237}
2022-06-15 16:11:08 +00:00
142: "ACCESSOR_PAIR_TYPE",
143: "ALIASED_ARGUMENTS_ENTRY_TYPE",
144: "ALLOCATION_MEMENTO_TYPE",
145: "ALLOCATION_SITE_TYPE",
146: "ARRAY_BOILERPLATE_DESCRIPTION_TYPE",
147: "ASM_WASM_DATA_TYPE",
148: "ASYNC_GENERATOR_REQUEST_TYPE",
149: "BREAK_POINT_TYPE",
150: "BREAK_POINT_INFO_TYPE",
[runtime] Cache template objects as JSArray lists keyed on Script Make several changes to template object caching: * Key the cache on Script rather than SFI, so that entries stay alive even if the SFI dies (e.g. because its parent is code flushed) but can be resurrected (because other functions from the same script can recreate it) * With the above change, identify the required template object by comparing both function literal id and feedback slot id. * Change the cache from a linked list of CachedTemplateObjects into an ArrayList pointing directly to the template object JSArrays. * With CachedTemplateObjects being gone, store the function literal id and slot id directly on the JSArray behind private symbols. Fast path access to them in the case where the template object has the expected map, and look them up in a slow path if the map changed (e.g. because the template object was used as a prototype and transitioned to a dictionary map). Change-Id: Id715cb2fd38b9605b8e6ddf5e35336bb4f0300d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3900376 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#83693}
2022-10-12 08:59:09 +00:00
151: "CALL_SITE_INFO_TYPE",
152: "CLASS_POSITIONS_TYPE",
153: "DEBUG_INFO_TYPE",
154: "ENUM_CACHE_TYPE",
155: "ERROR_STACK_DATA_TYPE",
156: "FEEDBACK_CELL_TYPE",
157: "FUNCTION_TEMPLATE_RARE_DATA_TYPE",
158: "INTERCEPTOR_INFO_TYPE",
159: "INTERPRETER_DATA_TYPE",
160: "MODULE_REQUEST_TYPE",
161: "PROMISE_CAPABILITY_TYPE",
162: "PROMISE_ON_STACK_TYPE",
163: "PROMISE_REACTION_TYPE",
164: "PROPERTY_DESCRIPTOR_OBJECT_TYPE",
165: "PROTOTYPE_INFO_TYPE",
166: "REG_EXP_BOILERPLATE_DESCRIPTION_TYPE",
167: "SCRIPT_TYPE",
168: "SCRIPT_OR_MODULE_TYPE",
169: "SOURCE_TEXT_MODULE_INFO_ENTRY_TYPE",
170: "STACK_FRAME_INFO_TYPE",
171: "TEMPLATE_OBJECT_DESCRIPTION_TYPE",
172: "TUPLE2_TYPE",
173: "WASM_EXCEPTION_TAG_TYPE",
174: "WASM_INDIRECT_FUNCTION_TABLE_TYPE",
175: "FIXED_ARRAY_TYPE",
176: "HASH_TABLE_TYPE",
177: "EPHEMERON_HASH_TABLE_TYPE",
178: "GLOBAL_DICTIONARY_TYPE",
179: "NAME_DICTIONARY_TYPE",
180: "NAME_TO_INDEX_HASH_TABLE_TYPE",
181: "NUMBER_DICTIONARY_TYPE",
182: "ORDERED_HASH_MAP_TYPE",
183: "ORDERED_HASH_SET_TYPE",
184: "ORDERED_NAME_DICTIONARY_TYPE",
185: "REGISTERED_SYMBOL_TABLE_TYPE",
186: "SIMPLE_NUMBER_DICTIONARY_TYPE",
187: "CLOSURE_FEEDBACK_CELL_ARRAY_TYPE",
188: "OBJECT_BOILERPLATE_DESCRIPTION_TYPE",
189: "SCRIPT_CONTEXT_TABLE_TYPE",
190: "BYTE_ARRAY_TYPE",
191: "BYTECODE_ARRAY_TYPE",
192: "FIXED_DOUBLE_ARRAY_TYPE",
193: "INTERNAL_CLASS_WITH_SMI_ELEMENTS_TYPE",
194: "SLOPPY_ARGUMENTS_ELEMENTS_TYPE",
[turboshaft] Introduce new Turboshaft type system Bug: v8:12783 Change-Id: Id5d3ce17f0dc8cec1b2b257585290bed72dd9fd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4057111 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#84765}
2022-12-09 17:00:05 +00:00
195: "TURBOSHAFT_FLOAT64_TYPE_TYPE",
196: "TURBOSHAFT_FLOAT64_RANGE_TYPE_TYPE",
197: "TURBOSHAFT_FLOAT64_SET_TYPE_TYPE",
198: "TURBOSHAFT_WORD32_TYPE_TYPE",
199: "TURBOSHAFT_WORD32_RANGE_TYPE_TYPE",
200: "TURBOSHAFT_WORD32_SET_TYPE_TYPE",
201: "TURBOSHAFT_WORD64_TYPE_TYPE",
202: "TURBOSHAFT_WORD64_RANGE_TYPE_TYPE",
203: "TURBOSHAFT_WORD64_SET_TYPE_TYPE",
[string] Add a is_shared bit to strings and String::Share The is_shared bit bumps the number of reserved bits for Strings' InstanceType from 6 to 7. This has the side effect of shuffling the InstanceType enum values. There are no users of this bit yet. This is steps 1-2 from the following design doc [1], in preparation for sharing internalized and in-place-internalizable strings. [1] https://docs.google.com/document/d/1c5i8f2EfKIQygGZ23hNiGxouvRISjUMnJjNsOodj6z0/edit?usp=sharing Bug: v8:12007 Change-Id: Idf11a6035305f0375b4f824ffd32a64f6b5b043b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3266017 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#77831}
2021-11-10 22:42:10 +00:00
204: "FOREIGN_TYPE",
[sandbox] Sandboxify WasmTypeInfo This CL changes the WasmTypeInfo class to have a direct ExternalPointer to the native type structure instead of using a Foreign. This in turn makes it possible to use a unique pointer tag for that external pointer when the sandbox is enabled. Bug: v8:10391, v8:12949 Change-Id: Ifee4d2103cabfa6a7299d0d09e06d387034e5f8f Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829085 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#82504}
2022-08-16 10:06:49 +00:00
205: "AWAIT_CONTEXT_TYPE",
206: "BLOCK_CONTEXT_TYPE",
207: "CATCH_CONTEXT_TYPE",
208: "DEBUG_EVALUATE_CONTEXT_TYPE",
209: "EVAL_CONTEXT_TYPE",
210: "FUNCTION_CONTEXT_TYPE",
211: "MODULE_CONTEXT_TYPE",
212: "NATIVE_CONTEXT_TYPE",
213: "SCRIPT_CONTEXT_TYPE",
214: "WITH_CONTEXT_TYPE",
[turboshaft] Introduce new Turboshaft type system Bug: v8:12783 Change-Id: Id5d3ce17f0dc8cec1b2b257585290bed72dd9fd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4057111 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#84765}
2022-12-09 17:00:05 +00:00
215: "TURBOFAN_BITSET_TYPE_TYPE",
216: "TURBOFAN_HEAP_CONSTANT_TYPE_TYPE",
217: "TURBOFAN_OTHER_NUMBER_CONSTANT_TYPE_TYPE",
218: "TURBOFAN_RANGE_TYPE_TYPE",
219: "TURBOFAN_UNION_TYPE_TYPE",
220: "UNCOMPILED_DATA_WITH_PREPARSE_DATA_TYPE",
221: "UNCOMPILED_DATA_WITH_PREPARSE_DATA_AND_JOB_TYPE",
222: "UNCOMPILED_DATA_WITHOUT_PREPARSE_DATA_TYPE",
223: "UNCOMPILED_DATA_WITHOUT_PREPARSE_DATA_WITH_JOB_TYPE",
224: "WASM_FUNCTION_DATA_TYPE",
225: "WASM_CAPI_FUNCTION_DATA_TYPE",
226: "WASM_EXPORTED_FUNCTION_DATA_TYPE",
227: "WASM_JS_FUNCTION_DATA_TYPE",
228: "EXPORTED_SUB_CLASS_BASE_TYPE",
229: "EXPORTED_SUB_CLASS_TYPE",
230: "EXPORTED_SUB_CLASS2_TYPE",
231: "SMALL_ORDERED_HASH_MAP_TYPE",
232: "SMALL_ORDERED_HASH_SET_TYPE",
233: "SMALL_ORDERED_NAME_DICTIONARY_TYPE",
234: "ABSTRACT_INTERNAL_CLASS_SUBCLASS1_TYPE",
235: "ABSTRACT_INTERNAL_CLASS_SUBCLASS2_TYPE",
236: "DESCRIPTOR_ARRAY_TYPE",
237: "STRONG_DESCRIPTOR_ARRAY_TYPE",
238: "SOURCE_TEXT_MODULE_TYPE",
239: "SYNTHETIC_MODULE_TYPE",
240: "WEAK_FIXED_ARRAY_TYPE",
241: "TRANSITION_ARRAY_TYPE",
242: "ACCESSOR_INFO_TYPE",
243: "CALL_HANDLER_INFO_TYPE",
244: "CELL_TYPE",
Rename CodeDataContainer to Code This completes the big Code/CodeDataContainer name shuffle. Bug: v8:13654 Change-Id: If033e9153e751ab0d2a38572da2ce2f7029bc359 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4173569 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Jakob Linke <jgruber@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85354}
2023-01-17 13:39:32 +00:00
245: "CODE_TYPE",
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
246: "COVERAGE_INFO_TYPE",
247: "EMBEDDER_DATA_ARRAY_TYPE",
248: "FEEDBACK_METADATA_TYPE",
249: "FEEDBACK_VECTOR_TYPE",
250: "FILLER_TYPE",
251: "FREE_SPACE_TYPE",
252: "INSTRUCTION_STREAM_TYPE",
[turboshaft] Introduce new Turboshaft type system Bug: v8:12783 Change-Id: Id5d3ce17f0dc8cec1b2b257585290bed72dd9fd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4057111 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#84765}
2022-12-09 17:00:05 +00:00
253: "INTERNAL_CLASS_TYPE",
254: "INTERNAL_CLASS_WITH_STRUCT_ELEMENTS_TYPE",
255: "MAP_TYPE",
256: "MEGA_DOM_HANDLER_TYPE",
257: "ON_HEAP_BASIC_BLOCK_PROFILER_DATA_TYPE",
258: "PREPARSE_DATA_TYPE",
259: "PROPERTY_ARRAY_TYPE",
260: "PROPERTY_CELL_TYPE",
261: "SCOPE_INFO_TYPE",
262: "SHARED_FUNCTION_INFO_TYPE",
263: "SMI_BOX_TYPE",
264: "SMI_PAIR_TYPE",
265: "SORT_STATE_TYPE",
266: "SWISS_NAME_DICTIONARY_TYPE",
267: "WASM_API_FUNCTION_REF_TYPE",
268: "WASM_CONTINUATION_OBJECT_TYPE",
269: "WASM_INTERNAL_FUNCTION_TYPE",
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
270: "WASM_NULL_TYPE",
271: "WASM_RESUME_DATA_TYPE",
272: "WASM_STRING_VIEW_ITER_TYPE",
273: "WASM_TYPE_INFO_TYPE",
274: "WEAK_ARRAY_LIST_TYPE",
275: "WEAK_CELL_TYPE",
276: "WASM_ARRAY_TYPE",
277: "WASM_STRUCT_TYPE",
278: "JS_PROXY_TYPE",
[torque] Generate instance types Design doc: https://docs.google.com/document/d/1ZU6rCvF2YHBGMLujWqqaxlPsjFfjKDE9C3-EugfdlAE/edit Changes from the design doc: - Changed to use 'class' declarations rather than 'type' declarations for things that need instance types but whose layout is not known to Torque. These declarations end with a semicolon rather than having a full set of methods and fields surrounded by {}. If the class's name should not be treated as a class name in generated output (because it's actually a template, or doesn't exist at all), we use the standard 'generates' clause to declare the most appropriate C++ class. - Removed @instanceTypeName. - @highestInstanceType became @highestInstanceTypeWithinParentClassRange to indicate a semantic change: it no longer denotes the highest instance type globally, but only within the range of values for its immediate parent class. This lets us use it for Oddball, which is expected to be the highest primitive type. - Added new abstract classes JSCustomElementsObject and JSSpecialObject to help with some range checks. - Added @lowestInstanceTypeWithinParentClassRange so we can move the new classes JSCustomElementsObject and JSSpecialObject to the beginning of the JSObject range. This seems like the least-brittle way to establish ranges that also include JSProxy (and these ranges are verified with static assertions in instance-type.h). - Renamed @instanceTypeValue to @apiExposedInstanceTypeValue. - Renamed @instanceTypeFlags to @reserveBitsInInstanceType. This change introduces the new annotations and adds the ability for Torque to assign instance types that satisfy those annotations. Torque now emits two new macros: - TORQUE_ASSIGNED_INSTANCE_TYPES, which is used to define the InstanceType enumeration - TORQUE_ASSIGNED_INSTANCE_TYPE_LIST, which replaces the non-String parts of INSTANCE_TYPE_LIST The design document mentions a couple of other macro lists that could easily be replaced, but I'd like to defer those to a subsequent checkin because this one is already pretty large. Bug: v8:7793 Change-Id: Ie71d93a9d5b610e62be0ffa3bb36180c3357a6e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1757094 Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#64258}
2019-10-11 21:52:06 +00:00
1057: "JS_OBJECT_TYPE",
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
279: "JS_GLOBAL_OBJECT_TYPE",
280: "JS_GLOBAL_PROXY_TYPE",
281: "JS_MODULE_NAMESPACE_TYPE",
Reduce max instance type enum value. We collect instance type statistics in FatalProcessOutOfMemory into an array, which is allocated to the max instance type value. While we want to leave space to ensure new instance types do not affect constants in the API, we can be more frugal. We currently serialize 350 maps into the startup/context snapshot. Even if we assign a distinct instance type to each of these maps, we would still have more than enough to spare with this change. R=ulan@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I3e583c2c8da3342e9132d96046b5d80cd41afd72 Reviewed-on: https://chromium-review.googlesource.com/842542 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#50302}
2017-12-22 17:20:47 +00:00
1040: "JS_SPECIAL_API_OBJECT_TYPE",
[objects] Rename JSValue to JSPrimitiveWrapper We currently use the class name “JSValue” for JSObjects that wrap primitive values. This name is a common source of confusion. This patch switches to a name that’s more clear. In addition to manual tweaks, the patch applies the following mechanical global replacements: before | after --------------------------------|-------------------------------------- if_valueisnotvalue | if_valueisnotwrapper if_valueisvalue | if_valueiswrapper js_value | js_primitive_wrapper JS_VALUE_TYPE | JS_PRIMITIVE_WRAPPER_TYPE JSPrimitiveWrapperType | JSPrimitiveWrapper type jsvalue | js_primitive_wrapper JSValue | JSPrimitiveWrapper _GENERATED_JSVALUE_FIELDS | _GENERATED_JSPRIMITIVE_WRAPPER_FIELDS Change-Id: I9d9edea784eab6067b013e1f781e4db2070f807c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1672942 Reviewed-by: Tamer Tas <tmrts@chromium.org> Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#62337}
2019-06-24 13:13:34 +00:00
1041: "JS_PRIMITIVE_WRAPPER_TYPE",
[api] Implement signature checks using instance types Rather than depending on slow signature checks, receiver type checks are performed using fast numeric instance type checks. This CL adds a instance type range for embedders to assign values and uses these to perform type checks. Bug: v8:11476 Change-Id: Ie8236ae47ca0ba93ae76a7e690b81aa0a2b0f3e2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2883623 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#76162}
2021-08-09 07:44:18 +00:00
1058: "JS_API_OBJECT_TYPE",
2058: "JS_LAST_DUMMY_API_OBJECT_TYPE",
Check instance type before initializing embedder data slots JSObject::InitializeBody now checks whether the instance type of the object being initialized can have embedder data slots around the initialization logic for these slots. This fixes a performance regression on certain benchmarks. To perform this check efficiently, a new instance type, JSObjectWithEmbedderSlots, is introduced so that the check becomes a simple range check. Bug: chromium:1304139 Change-Id: I00c892bc2276e950b59602257ca1c2435c10e517 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3507712 Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#79497}
2022-03-14 17:35:42 +00:00
2059: "JS_DATA_VIEW_TYPE",
2060: "JS_TYPED_ARRAY_TYPE",
2061: "JS_ARRAY_BUFFER_TYPE",
2062: "JS_PROMISE_TYPE",
2063: "JS_BOUND_FUNCTION_TYPE",
2064: "JS_WRAPPED_FUNCTION_TYPE",
2065: "JS_FUNCTION_TYPE",
2066: "BIGINT64_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2067: "BIGUINT64_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2068: "FLOAT32_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2069: "FLOAT64_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2070: "INT16_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2071: "INT32_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2072: "INT8_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2073: "UINT16_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2074: "UINT32_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2075: "UINT8_CLAMPED_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2076: "UINT8_TYPED_ARRAY_CONSTRUCTOR_TYPE",
2077: "JS_ARRAY_CONSTRUCTOR_TYPE",
2078: "JS_PROMISE_CONSTRUCTOR_TYPE",
2079: "JS_REG_EXP_CONSTRUCTOR_TYPE",
2080: "JS_CLASS_CONSTRUCTOR_TYPE",
2081: "JS_ARRAY_ITERATOR_PROTOTYPE_TYPE",
2082: "JS_ITERATOR_PROTOTYPE_TYPE",
2083: "JS_MAP_ITERATOR_PROTOTYPE_TYPE",
2084: "JS_OBJECT_PROTOTYPE_TYPE",
2085: "JS_PROMISE_PROTOTYPE_TYPE",
2086: "JS_REG_EXP_PROTOTYPE_TYPE",
2087: "JS_SET_ITERATOR_PROTOTYPE_TYPE",
2088: "JS_SET_PROTOTYPE_TYPE",
2089: "JS_STRING_ITERATOR_PROTOTYPE_TYPE",
2090: "JS_TYPED_ARRAY_PROTOTYPE_TYPE",
2091: "JS_MAP_KEY_ITERATOR_TYPE",
2092: "JS_MAP_KEY_VALUE_ITERATOR_TYPE",
2093: "JS_MAP_VALUE_ITERATOR_TYPE",
2094: "JS_SET_KEY_VALUE_ITERATOR_TYPE",
2095: "JS_SET_VALUE_ITERATOR_TYPE",
[shared-struct] Disallow property redefinition Shared objects have fixed layout (i.e. immutable maps) and start off sealed. Ordinary JS objects allow writable properties to be redefined to be non-writable. This violates the fixed layout invariant and needs to be disallowed. Also contains a drive-by fix removing @highestInstanceTypeWithinParentClassRange, which is unneeded. Bug: chromium:1407595, v8:12547 Change-Id: I0257fa19f59ccfaaf0e07cb42aeedd71e132d21a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4190525 Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#85570}
2023-01-30 22:39:29 +00:00
2096: "JS_ATOMICS_CONDITION_TYPE",
2097: "JS_ATOMICS_MUTEX_TYPE",
2098: "JS_SHARED_ARRAY_TYPE",
2099: "JS_SHARED_STRUCT_TYPE",
2100: "JS_GENERATOR_OBJECT_TYPE",
2101: "JS_ASYNC_FUNCTION_OBJECT_TYPE",
2102: "JS_ASYNC_GENERATOR_OBJECT_TYPE",
2103: "JS_MAP_TYPE",
2104: "JS_SET_TYPE",
2105: "JS_WEAK_MAP_TYPE",
2106: "JS_WEAK_SET_TYPE",
2107: "JS_ARGUMENTS_OBJECT_TYPE",
2108: "JS_ARRAY_TYPE",
2109: "JS_ARRAY_ITERATOR_TYPE",
2110: "JS_ASYNC_FROM_SYNC_ITERATOR_TYPE",
2111: "JS_COLLATOR_TYPE",
2112: "JS_CONTEXT_EXTENSION_OBJECT_TYPE",
2113: "JS_DATE_TYPE",
2114: "JS_DATE_TIME_FORMAT_TYPE",
2115: "JS_DISPLAY_NAMES_TYPE",
2116: "JS_DURATION_FORMAT_TYPE",
2117: "JS_ERROR_TYPE",
2118: "JS_EXTERNAL_OBJECT_TYPE",
2119: "JS_FINALIZATION_REGISTRY_TYPE",
2120: "JS_LIST_FORMAT_TYPE",
2121: "JS_LOCALE_TYPE",
2122: "JS_MESSAGE_OBJECT_TYPE",
2123: "JS_NUMBER_FORMAT_TYPE",
2124: "JS_PLURAL_RULES_TYPE",
2125: "JS_RAW_JSON_TYPE",
2126: "JS_REG_EXP_TYPE",
2127: "JS_REG_EXP_STRING_ITERATOR_TYPE",
2128: "JS_RELATIVE_TIME_FORMAT_TYPE",
2129: "JS_SEGMENT_ITERATOR_TYPE",
2130: "JS_SEGMENTER_TYPE",
2131: "JS_SEGMENTS_TYPE",
2132: "JS_SHADOW_REALM_TYPE",
2133: "JS_STRING_ITERATOR_TYPE",
2134: "JS_TEMPORAL_CALENDAR_TYPE",
2135: "JS_TEMPORAL_DURATION_TYPE",
2136: "JS_TEMPORAL_INSTANT_TYPE",
2137: "JS_TEMPORAL_PLAIN_DATE_TYPE",
2138: "JS_TEMPORAL_PLAIN_DATE_TIME_TYPE",
2139: "JS_TEMPORAL_PLAIN_MONTH_DAY_TYPE",
2140: "JS_TEMPORAL_PLAIN_TIME_TYPE",
2141: "JS_TEMPORAL_PLAIN_YEAR_MONTH_TYPE",
2142: "JS_TEMPORAL_TIME_ZONE_TYPE",
2143: "JS_TEMPORAL_ZONED_DATE_TIME_TYPE",
2144: "JS_V8_BREAK_ITERATOR_TYPE",
2145: "JS_WEAK_REF_TYPE",
2146: "WASM_EXCEPTION_PACKAGE_TYPE",
2147: "WASM_GLOBAL_OBJECT_TYPE",
2148: "WASM_INSTANCE_OBJECT_TYPE",
2149: "WASM_MEMORY_OBJECT_TYPE",
2150: "WASM_MODULE_OBJECT_TYPE",
2151: "WASM_SUSPENDER_OBJECT_TYPE",
2152: "WASM_TABLE_OBJECT_TYPE",
2153: "WASM_TAG_OBJECT_TYPE",
2154: "WASM_VALUE_OBJECT_TYPE",
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
}
# List of known V8 maps.
KNOWN_MAPS = {
[turboshaft] Introduce new Turboshaft type system Bug: v8:12783 Change-Id: Id5d3ce17f0dc8cec1b2b257585290bed72dd9fd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4057111 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#84765}
2022-12-09 17:00:05 +00:00
("read_only_space", 0x02141): (255, "MetaMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x02169): (175, "FixedArrayMap"),
("read_only_space", 0x02191): (240, "WeakFixedArrayMap"),
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
("read_only_space", 0x021b9): (274, "WeakArrayListMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x021e1): (175, "FixedCOWArrayMap"),
("read_only_space", 0x02209): (236, "DescriptorArrayMap"),
("read_only_space", 0x02231): (131, "UndefinedMap"),
("read_only_space", 0x02259): (131, "NullMap"),
("read_only_space", 0x02281): (131, "TheHoleMap"),
("read_only_space", 0x02319): (132, "PromiseFulfillReactionJobTaskMap"),
("read_only_space", 0x02341): (133, "PromiseRejectReactionJobTaskMap"),
("read_only_space", 0x02369): (134, "CallableTaskMap"),
("read_only_space", 0x02391): (135, "CallbackTaskMap"),
("read_only_space", 0x023b9): (136, "PromiseResolveThenableJobTaskMap"),
("read_only_space", 0x023e1): (139, "FunctionTemplateInfoMap"),
("read_only_space", 0x02409): (140, "ObjectTemplateInfoMap"),
("read_only_space", 0x02431): (141, "AccessCheckInfoMap"),
("read_only_space", 0x02459): (142, "AccessorPairMap"),
("read_only_space", 0x02481): (143, "AliasedArgumentsEntryMap"),
("read_only_space", 0x024a9): (144, "AllocationMementoMap"),
("read_only_space", 0x024d1): (146, "ArrayBoilerplateDescriptionMap"),
("read_only_space", 0x024f9): (147, "AsmWasmDataMap"),
("read_only_space", 0x02521): (148, "AsyncGeneratorRequestMap"),
("read_only_space", 0x02549): (149, "BreakPointMap"),
("read_only_space", 0x02571): (150, "BreakPointInfoMap"),
("read_only_space", 0x02599): (151, "CallSiteInfoMap"),
("read_only_space", 0x025c1): (152, "ClassPositionsMap"),
("read_only_space", 0x025e9): (153, "DebugInfoMap"),
("read_only_space", 0x02611): (154, "EnumCacheMap"),
("read_only_space", 0x02639): (155, "ErrorStackDataMap"),
("read_only_space", 0x02661): (157, "FunctionTemplateRareDataMap"),
("read_only_space", 0x02689): (158, "InterceptorInfoMap"),
("read_only_space", 0x026b1): (159, "InterpreterDataMap"),
("read_only_space", 0x026d9): (160, "ModuleRequestMap"),
("read_only_space", 0x02701): (161, "PromiseCapabilityMap"),
("read_only_space", 0x02729): (162, "PromiseOnStackMap"),
("read_only_space", 0x02751): (163, "PromiseReactionMap"),
("read_only_space", 0x02779): (164, "PropertyDescriptorObjectMap"),
("read_only_space", 0x027a1): (165, "PrototypeInfoMap"),
("read_only_space", 0x027c9): (166, "RegExpBoilerplateDescriptionMap"),
("read_only_space", 0x027f1): (167, "ScriptMap"),
("read_only_space", 0x02819): (168, "ScriptOrModuleMap"),
("read_only_space", 0x02841): (169, "SourceTextModuleInfoEntryMap"),
("read_only_space", 0x02869): (170, "StackFrameInfoMap"),
("read_only_space", 0x02891): (171, "TemplateObjectDescriptionMap"),
("read_only_space", 0x028b9): (172, "Tuple2Map"),
("read_only_space", 0x028e1): (173, "WasmExceptionTagMap"),
("read_only_space", 0x02909): (174, "WasmIndirectFunctionTableMap"),
("read_only_space", 0x02931): (145, "AllocationSiteWithWeakNextMap"),
("read_only_space", 0x02959): (145, "AllocationSiteWithoutWeakNextMap"),
("read_only_space", 0x02981): (137, "LoadHandler1Map"),
("read_only_space", 0x029a9): (137, "LoadHandler2Map"),
("read_only_space", 0x029d1): (137, "LoadHandler3Map"),
("read_only_space", 0x029f9): (138, "StoreHandler0Map"),
("read_only_space", 0x02a21): (138, "StoreHandler1Map"),
("read_only_space", 0x02a49): (138, "StoreHandler2Map"),
("read_only_space", 0x02a71): (138, "StoreHandler3Map"),
("read_only_space", 0x02ab5): (261, "ScopeInfoMap"),
("read_only_space", 0x02add): (175, "ModuleInfoMap"),
("read_only_space", 0x02b05): (187, "ClosureFeedbackCellArrayMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x02b2d): (249, "FeedbackVectorMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x02b55): (130, "HeapNumberMap"),
Reland "[static-roots] Use static map range checks instead of instance types" This is a reland of commit 77d08fcde520a4d806c550b007d619dcd9d0ba4f Original change's description: > [static-roots] Use static map range checks instead of instance types > > Some instance types, or type ranges, corresponds to a range of pointers > in the static read only roots table. Instead of loading the instance > type of a map it can therefore be beneficial to compare the map itself > against this range. > > This CL adds: > > * Add infrastructure to compute and output a mapping of > `(instance_type_first, instance_type_last) -> > (map_ptr_first, map_ptr_last)` for interesting ranges. > * Extend InstanceTypeChecker to use these ranges. > > For single instance types that map onto a range of maps it is not > obvious which check is faster. Checking the map range saves a load, > whereas checking the instance type saves an additional jump. > > Bug: v8:13466 > Change-Id: I670fc10fad9920645c0ce0d976ae7e7a13a86e60 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4188379 > Reviewed-by: Jakob Linke <jgruber@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85599} Bug: v8:13466 Change-Id: I0317a7b88e391e0a7502cc056a2fe691d294fba1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4217131 Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#85614}
2023-02-02 07:19:26 +00:00
("read_only_space", 0x02b7d): (204, "ForeignMap"),
("read_only_space", 0x02ba5): (256, "MegaDomHandlerMap"),
("read_only_space", 0x02bcd): (131, "BooleanMap"),
("read_only_space", 0x02bf5): (131, "UninitializedMap"),
("read_only_space", 0x02c1d): (131, "ArgumentsMarkerMap"),
("read_only_space", 0x02c45): (131, "ExceptionMap"),
("read_only_space", 0x02c6d): (131, "TerminationExceptionMap"),
("read_only_space", 0x02c95): (131, "OptimizedOutMap"),
("read_only_space", 0x02cbd): (131, "StaleRegisterMap"),
("read_only_space", 0x02ce5): (131, "SelfReferenceMarkerMap"),
("read_only_space", 0x02d0d): (131, "BasicBlockCountersMarkerMap"),
("read_only_space", 0x02d35): (129, "BigIntMap"),
("read_only_space", 0x02d5d): (128, "SymbolMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x02d85): (32, "StringMap"),
("read_only_space", 0x02dad): (40, "OneByteStringMap"),
("read_only_space", 0x02dd5): (33, "ConsStringMap"),
("read_only_space", 0x02dfd): (41, "ConsOneByteStringMap"),
("read_only_space", 0x02e25): (35, "SlicedStringMap"),
("read_only_space", 0x02e4d): (43, "SlicedOneByteStringMap"),
("read_only_space", 0x02e75): (34, "ExternalStringMap"),
("read_only_space", 0x02e9d): (42, "ExternalOneByteStringMap"),
("read_only_space", 0x02ec5): (50, "UncachedExternalStringMap"),
("read_only_space", 0x02eed): (58, "UncachedExternalOneByteStringMap"),
("read_only_space", 0x02f15): (0, "InternalizedStringMap"),
("read_only_space", 0x02f3d): (8, "OneByteInternalizedStringMap"),
("read_only_space", 0x02f65): (2, "ExternalInternalizedStringMap"),
("read_only_space", 0x02f8d): (10, "ExternalOneByteInternalizedStringMap"),
("read_only_space", 0x02fb5): (18, "UncachedExternalInternalizedStringMap"),
("read_only_space", 0x02fdd): (26, "UncachedExternalOneByteInternalizedStringMap"),
("read_only_space", 0x03005): (37, "ThinStringMap"),
("read_only_space", 0x0302d): (45, "ThinOneByteStringMap"),
("read_only_space", 0x03055): (96, "SharedStringMap"),
("read_only_space", 0x0307d): (104, "SharedOneByteStringMap"),
("read_only_space", 0x030a5): (98, "SharedExternalStringMap"),
("read_only_space", 0x030cd): (106, "SharedExternalOneByteStringMap"),
("read_only_space", 0x030f5): (114, "SharedUncachedExternalStringMap"),
("read_only_space", 0x0311d): (122, "SharedUncachedExternalOneByteStringMap"),
("read_only_space", 0x03145): (101, "SharedThinStringMap"),
("read_only_space", 0x0316d): (109, "SharedThinOneByteStringMap"),
("read_only_space", 0x03195): (192, "FixedDoubleArrayMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x031bd): (248, "FeedbackMetadataArrayMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x031e5): (190, "ByteArrayMap"),
("read_only_space", 0x0320d): (191, "BytecodeArrayMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x03235): (251, "FreeSpaceMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x0325d): (259, "PropertyArrayMap"),
("read_only_space", 0x03285): (231, "SmallOrderedHashMapMap"),
("read_only_space", 0x032ad): (232, "SmallOrderedHashSetMap"),
("read_only_space", 0x032d5): (233, "SmallOrderedNameDictionaryMap"),
("read_only_space", 0x032fd): (222, "UncompiledDataWithoutPreparseDataMap"),
("read_only_space", 0x03325): (220, "UncompiledDataWithPreparseDataMap"),
("read_only_space", 0x0334d): (223, "UncompiledDataWithoutPreparseDataWithJobMap"),
("read_only_space", 0x03375): (221, "UncompiledDataWithPreparseDataAndJobMap"),
("read_only_space", 0x0339d): (257, "OnHeapBasicBlockProfilerDataMap"),
("read_only_space", 0x033c5): (215, "TurbofanBitsetTypeMap"),
("read_only_space", 0x033ed): (219, "TurbofanUnionTypeMap"),
("read_only_space", 0x03415): (218, "TurbofanRangeTypeMap"),
("read_only_space", 0x0343d): (216, "TurbofanHeapConstantTypeMap"),
("read_only_space", 0x03465): (217, "TurbofanOtherNumberConstantTypeMap"),
("read_only_space", 0x0348d): (198, "TurboshaftWord32TypeMap"),
("read_only_space", 0x034b5): (199, "TurboshaftWord32RangeTypeMap"),
("read_only_space", 0x034dd): (201, "TurboshaftWord64TypeMap"),
("read_only_space", 0x03505): (202, "TurboshaftWord64RangeTypeMap"),
("read_only_space", 0x0352d): (195, "TurboshaftFloat64TypeMap"),
("read_only_space", 0x03555): (196, "TurboshaftFloat64RangeTypeMap"),
("read_only_space", 0x0357d): (253, "InternalClassMap"),
("read_only_space", 0x035a5): (264, "SmiPairMap"),
("read_only_space", 0x035cd): (263, "SmiBoxMap"),
("read_only_space", 0x035f5): (228, "ExportedSubClassBaseMap"),
("read_only_space", 0x0361d): (229, "ExportedSubClassMap"),
("read_only_space", 0x03645): (234, "AbstractInternalClassSubclass1Map"),
("read_only_space", 0x0366d): (235, "AbstractInternalClassSubclass2Map"),
("read_only_space", 0x03695): (230, "ExportedSubClass2Map"),
("read_only_space", 0x036bd): (265, "SortStateMap"),
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
("read_only_space", 0x036e5): (272, "WasmStringViewIterMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x0370d): (194, "SloppyArgumentsElementsMap"),
("read_only_space", 0x03735): (237, "StrongDescriptorArrayMap"),
("read_only_space", 0x0375d): (200, "TurboshaftWord32SetTypeMap"),
("read_only_space", 0x03785): (203, "TurboshaftWord64SetTypeMap"),
("read_only_space", 0x037ad): (197, "TurboshaftFloat64SetTypeMap"),
("read_only_space", 0x037d5): (193, "InternalClassWithSmiElementsMap"),
("read_only_space", 0x037fd): (254, "InternalClassWithStructElementsMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x03825): (252, "InstructionStreamMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x0384d): (244, "CellMap"),
("read_only_space", 0x0387d): (260, "GlobalPropertyCellMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x038a5): (250, "OnePointerFillerMap"),
("read_only_space", 0x038cd): (250, "TwoPointerFillerMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x038f5): (156, "NoClosuresCellMap"),
("read_only_space", 0x0391d): (156, "OneClosureCellMap"),
("read_only_space", 0x03945): (156, "ManyClosuresCellMap"),
("read_only_space", 0x0396d): (241, "TransitionArrayMap"),
("read_only_space", 0x03995): (176, "HashTableMap"),
("read_only_space", 0x039bd): (182, "OrderedHashMapMap"),
("read_only_space", 0x039e5): (183, "OrderedHashSetMap"),
("read_only_space", 0x03a0d): (184, "OrderedNameDictionaryMap"),
("read_only_space", 0x03a35): (179, "NameDictionaryMap"),
("read_only_space", 0x03a5d): (266, "SwissNameDictionaryMap"),
("read_only_space", 0x03a85): (178, "GlobalDictionaryMap"),
("read_only_space", 0x03aad): (181, "NumberDictionaryMap"),
("read_only_space", 0x03ad5): (186, "SimpleNumberDictionaryMap"),
("read_only_space", 0x03afd): (180, "NameToIndexHashTableMap"),
("read_only_space", 0x03b25): (185, "RegisteredSymbolTableMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x03b4d): (247, "EmbedderDataArrayMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x03b75): (177, "EphemeronHashTableMap"),
("read_only_space", 0x03b9d): (175, "ArrayListMap"),
("read_only_space", 0x03bc5): (189, "ScriptContextTableMap"),
("read_only_space", 0x03bed): (188, "ObjectBoilerplateDescriptionMap"),
Rename Code to InstructionStream .. as part of the big Code/CodeDataContainer name shuffle. In the next step, CodeDataContainer will be renamed to Code. Bug: v8:13654 Change-Id: Ia80ac984d46dd6c2a108098055a5cd60e22a837c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171628 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85337}
2023-01-17 09:59:51 +00:00
("read_only_space", 0x03c15): (246, "CoverageInfoMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x03c3d): (242, "AccessorInfoMap"),
("read_only_space", 0x03c65): (243, "SideEffectCallHandlerInfoMap"),
("read_only_space", 0x03c8d): (243, "SideEffectFreeCallHandlerInfoMap"),
("read_only_space", 0x03cb5): (243, "NextCallSideEffectFreeCallHandlerInfoMap"),
("read_only_space", 0x03cdd): (258, "PreparseDataMap"),
("read_only_space", 0x03d05): (262, "SharedFunctionInfoMap"),
("read_only_space", 0x03d2d): (238, "SourceTextModuleMap"),
("read_only_space", 0x03d55): (239, "SyntheticModuleMap"),
Rename CodeDataContainer to Code This completes the big Code/CodeDataContainer name shuffle. Bug: v8:13654 Change-Id: If033e9153e751ab0d2a38572da2ce2f7029bc359 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4173569 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Jakob Linke <jgruber@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#85354}
2023-01-17 13:39:32 +00:00
("read_only_space", 0x03d7d): (245, "CodeMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x03da5): (267, "WasmApiFunctionRefMap"),
("read_only_space", 0x03dcd): (225, "WasmCapiFunctionDataMap"),
("read_only_space", 0x03df5): (226, "WasmExportedFunctionDataMap"),
("read_only_space", 0x03e1d): (269, "WasmInternalFunctionMap"),
("read_only_space", 0x03e45): (227, "WasmJSFunctionDataMap"),
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
("read_only_space", 0x03e6d): (271, "WasmResumeDataMap"),
("read_only_space", 0x03e95): (273, "WasmTypeInfoMap"),
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x03ebd): (268, "WasmContinuationObjectMap"),
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
("read_only_space", 0x03ee5): (270, "WasmNullMap"),
("read_only_space", 0x03f0d): (275, "WeakCellMap"),
[shared-struct] Disallow property redefinition Shared objects have fixed layout (i.e. immutable maps) and start off sealed. Ordinary JS objects allow writable properties to be redefined to be non-writable. This violates the fixed layout invariant and needs to be disallowed. Also contains a drive-by fix removing @highestInstanceTypeWithinParentClassRange, which is unneeded. Bug: chromium:1407595, v8:12547 Change-Id: I0257fa19f59ccfaaf0e07cb42aeedd71e132d21a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4190525 Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#85570}
2023-01-30 22:39:29 +00:00
("old_space", 0x043bd): (2118, "ExternalMap"),
("old_space", 0x043e5): (2122, "JSMessageObjectMap"),
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
}
# List of known V8 objects.
KNOWN_OBJECTS = {
Reland "Reland "Reland "[static-roots] Enable static roots on supported configurations""" This is a reland of commit 4bbbb521f4267d0f8ec6edd07be595eed82dac9c The issue was that the hash of the static roots table was not stable across cross-compilation. Original change's description: > Reland "Reland "[static-roots] Enable static roots on supported configurations"" > > This is a reland of commit b247270178dcfffe9af4389dbb84d1643bfccea4 > > But with static roots disabled on non-external code space builds. > > > Original change's description: > > Reland "[static-roots] Enable static roots on supported configurations" > > > > This is a reland of commit c04ca9cc63417d24455704cbee44eb60b79f7af2 > > > > Original change's description: > > > [static-roots] Enable static roots on supported configurations > > > > > > The static root values are not actually used yet. > > > > > > Bug: v8:13466 > > > Change-Id: I85fc99277c31e0dd4350a305040ab25456051046 > > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4101880 > > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > > > Cr-Commit-Position: refs/heads/main@{#84850} > > > > Bug: v8:13466 > > Change-Id: Id65bb5b19df999dfe930a78993e4bf3343d9f996 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4111641 > > Auto-Submit: Olivier Flückiger <olivf@chromium.org> > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Toon Verwaest <verwaest@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#84991} > > Bug: v8:13466 > Change-Id: Id1f55c1cf8d349338fd49f6cb0ed7dc2e1054a72 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4123534 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Olivier Flückiger <olivf@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85037} Bug: v8:13466 Change-Id: Ifbf26347da293bb465e837a0a914d3f0b393cfad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4139138 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Olivier Flückiger <olivf@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#85154}
2023-01-05 16:40:49 +00:00
("read_only_space", 0x022a9): "EmptyFixedArray",
("read_only_space", 0x022b1): "EmptyWeakFixedArray",
("read_only_space", 0x022b9): "EmptyWeakArrayList",
("read_only_space", 0x022c5): "NullValue",
("read_only_space", 0x022e1): "UndefinedValue",
("read_only_space", 0x022fd): "TheHoleValue",
("read_only_space", 0x02a99): "EmptyEnumCache",
("read_only_space", 0x02aa5): "EmptyDescriptorArray",
("read_only_space", 0x03875): "InvalidPrototypeValidityCell",
Reland "[wasm-gc] Introduce wasm null object" This is a reland of commit 2e357c4814954c6d83c336655209e14aa53911d4 Difference compared to original: Initialize wasm-null object's payload. Original change's description: > [wasm-gc] Introduce wasm null object > > We introduce a wasm null object, separate from JS null. Its purpose is > to support trapping null accesses for wasm objects. > This will be achieved by allocating a large payload for it (larger than > any wasm struct) and memory-protecting it (see linked CL). The two null > objects get mapped to each other at the wasm-JS boundary. > Since externref objects live on the JS side of the boundary, > null-related instructions in wasm now need an additional type argument > to handle the correct null object. > > Bug: v8:7748 > Change-Id: I06da00fcd279cc5376e69ab7858e3782f5b5081e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4200639 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Cr-Commit-Position: refs/heads/main@{#85648} Bug: v8:7748 Change-Id: I46413d05f0213229f1d19277ae98dbb8df5afdf9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4224011 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#85705}
2023-02-06 13:12:58 +00:00
("read_only_space", 0x03f35): "EmptyArrayList",
("read_only_space", 0x03f41): "EmptyScopeInfo",
("read_only_space", 0x03f51): "EmptyObjectBoilerplateDescription",
("read_only_space", 0x03f5d): "EmptyArrayBoilerplateDescription",
("read_only_space", 0x03f69): "TrueValue",
("read_only_space", 0x03f85): "FalseValue",
("read_only_space", 0x03fa1): "EmptyByteArray",
("read_only_space", 0x03fa9): "EmptyPropertyArray",
("read_only_space", 0x03fb1): "EmptyClosureFeedbackCellArray",
("read_only_space", 0x03fb9): "NoOpInterceptorInfo",
("read_only_space", 0x03fe1): "MinusZeroValue",
("read_only_space", 0x03fed): "NanValue",
("read_only_space", 0x03ff9): "HoleNanValue",
("read_only_space", 0x04005): "InfinityValue",
("read_only_space", 0x04011): "MinusInfinityValue",
("read_only_space", 0x0401d): "MaxSafeInteger",
("read_only_space", 0x04029): "MaxUInt32",
("read_only_space", 0x04035): "SmiMinValue",
("read_only_space", 0x04041): "SmiMaxValuePlusOne",
("read_only_space", 0x0404d): "HashSeed",
("read_only_space", 0x0405d): "SingleCharacterStringTable",
("read_only_space", 0x05465): "empty_string",
("read_only_space", 0x07b5d): "UninitializedValue",
("read_only_space", 0x07b95): "ArgumentsMarker",
("read_only_space", 0x07bcd): "TerminationException",
("read_only_space", 0x07c0d): "Exception",
("read_only_space", 0x07c29): "OptimizedOut",
("read_only_space", 0x07c61): "StaleRegister",
("read_only_space", 0x07c99): "SelfReferenceMarker",
("read_only_space", 0x07cd9): "BasicBlockCountersMarker",
("read_only_space", 0x081f1): "EmptyPropertyDictionary",
("read_only_space", 0x08219): "EmptySymbolTable",
("read_only_space", 0x08235): "EmptySlowElementDictionary",
("read_only_space", 0x08259): "EmptyOrderedHashMap",
("read_only_space", 0x0826d): "EmptyOrderedHashSet",
("read_only_space", 0x08281): "EmptyOrderedPropertyDictionary",
("read_only_space", 0x082a5): "EmptySwissPropertyDictionary",
("read_only_space", 0x082c5): "EmptyFeedbackMetadata",
("read_only_space", 0x082d1): "GlobalThisBindingScopeInfo",
("read_only_space", 0x082f1): "EmptyFunctionScopeInfo",
("read_only_space", 0x08315): "NativeScopeInfo",
("read_only_space", 0x0832d): "ShadowRealmScopeInfo",
("read_only_space", 0x0fffd): "WasmNull",
[flags] Remove --harmony-array-find-last The Array and TypedArray findLast and findLastIndex proposal has shipped since M97. Bug: v8:11990 Change-Id: Iece995c020c2b5535abc4dd2a47516265e445fc3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4144631 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Auto-Submit: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#85235}
2023-01-10 21:11:39 +00:00
("old_space", 0x0426d): "ArgumentsIteratorAccessor",
("old_space", 0x04285): "ArrayLengthAccessor",
("old_space", 0x0429d): "BoundFunctionLengthAccessor",
("old_space", 0x042b5): "BoundFunctionNameAccessor",
("old_space", 0x042cd): "ErrorStackAccessor",
("old_space", 0x042e5): "FunctionArgumentsAccessor",
("old_space", 0x042fd): "FunctionCallerAccessor",
("old_space", 0x04315): "FunctionNameAccessor",
("old_space", 0x0432d): "FunctionLengthAccessor",
("old_space", 0x04345): "FunctionPrototypeAccessor",
("old_space", 0x0435d): "StringLengthAccessor",
("old_space", 0x04375): "ValueUnavailableAccessor",
("old_space", 0x0438d): "WrappedFunctionLengthAccessor",
("old_space", 0x043a5): "WrappedFunctionNameAccessor",
("old_space", 0x043bd): "ExternalMap",
("old_space", 0x043e5): "JSMessageObjectMap",
("old_space", 0x0440d): "EmptyScript",
[compile hints] Collect compile hints data in v8 This adds the APIs for the embedder to 1) request compile hints collection for a script 2) retrieve the compile hint data Bug: chromium:1406506 Change-Id: Ic23430d3cff9fe71faa71f4c7be6635467e14268 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4154427 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#85461}
2023-01-24 13:16:41 +00:00
("old_space", 0x04455): "ManyClosuresCell",
("old_space", 0x04461): "ArrayConstructorProtector",
("old_space", 0x04475): "NoElementsProtector",
("old_space", 0x04489): "MegaDOMProtector",
("old_space", 0x0449d): "IsConcatSpreadableProtector",
("old_space", 0x044b1): "ArraySpeciesProtector",
("old_space", 0x044c5): "TypedArraySpeciesProtector",
("old_space", 0x044d9): "PromiseSpeciesProtector",
("old_space", 0x044ed): "RegExpSpeciesProtector",
("old_space", 0x04501): "StringLengthProtector",
("old_space", 0x04515): "ArrayIteratorProtector",
("old_space", 0x04529): "ArrayBufferDetachingProtector",
("old_space", 0x0453d): "PromiseHookProtector",
("old_space", 0x04551): "PromiseResolveProtector",
("old_space", 0x04565): "MapIteratorProtector",
("old_space", 0x04579): "PromiseThenProtector",
("old_space", 0x0458d): "SetIteratorProtector",
("old_space", 0x045a1): "StringIteratorProtector",
("old_space", 0x045b5): "NumberStringPrototypeNoReplaceProtector",
("old_space", 0x045c9): "StringSplitCache",
("old_space", 0x049d1): "RegExpMultipleCache",
("old_space", 0x04dd9): "BuiltinsConstantsTable",
("old_space", 0x053a9): "AsyncFunctionAwaitRejectSharedFun",
("old_space", 0x053cd): "AsyncFunctionAwaitResolveSharedFun",
("old_space", 0x053f1): "AsyncGeneratorAwaitRejectSharedFun",
("old_space", 0x05415): "AsyncGeneratorAwaitResolveSharedFun",
("old_space", 0x05439): "AsyncGeneratorYieldWithAwaitResolveSharedFun",
("old_space", 0x0545d): "AsyncGeneratorReturnResolveSharedFun",
("old_space", 0x05481): "AsyncGeneratorReturnClosedRejectSharedFun",
("old_space", 0x054a5): "AsyncGeneratorReturnClosedResolveSharedFun",
("old_space", 0x054c9): "AsyncIteratorValueUnwrapSharedFun",
("old_space", 0x054ed): "PromiseAllResolveElementSharedFun",
("old_space", 0x05511): "PromiseAllSettledResolveElementSharedFun",
("old_space", 0x05535): "PromiseAllSettledRejectElementSharedFun",
("old_space", 0x05559): "PromiseAnyRejectElementSharedFun",
("old_space", 0x0557d): "PromiseCapabilityDefaultRejectSharedFun",
("old_space", 0x055a1): "PromiseCapabilityDefaultResolveSharedFun",
("old_space", 0x055c5): "PromiseCatchFinallySharedFun",
("old_space", 0x055e9): "PromiseGetCapabilitiesExecutorSharedFun",
("old_space", 0x0560d): "PromiseThenFinallySharedFun",
("old_space", 0x05631): "PromiseThrowerFinallySharedFun",
("old_space", 0x05655): "PromiseValueThunkFinallySharedFun",
("old_space", 0x05679): "ProxyRevokeSharedFun",
("old_space", 0x0569d): "ShadowRealmImportValueFulfilledSFI",
("old_space", 0x056c1): "SourceTextModuleExecuteAsyncModuleFulfilledSFI",
("old_space", 0x056e5): "SourceTextModuleExecuteAsyncModuleRejectedSFI",
[ptr-compr][x64] Enable pointer compression on x64 Chromium LSAN bot failures are fixed on Chromium side: https://chromium-review.googlesource.com/c/chromium/src/+/1926472 Bug: v8:7703 Change-Id: I830b747ca2f2f1b3c5adf31b42b3b8112c5d4457 Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng,v8_linux64_tsan_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_cfi_rel_ng Cq-Include-Trybots: luci.chromium.try:fuchsia_x64,linux-rel,mac-rel,linux_chromium_asan_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1925149 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#65136}
2019-11-24 23:19:26 +00:00
}
# Lower 32 bits of first page addresses for various heap spaces.
HEAP_FIRST_PAGES = {
[ext-code-space] Enable external code space on x64 and desktop arm64 This is a reland #3. The fixes were landed separately. Perf Sheriffs: this CL might regress some benchmarks while improving the others. Bug: v8:11880 Change-Id: I8ed5bf59360649718960dc34c06015ee6ff1532a Cq-Include-Trybots: luci.v8.try:v8_android_arm64_compile_dbg Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3422643 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#78854}
2022-01-28 14:23:46 +00:00
0x000c0000: "old_space",
0x00000000: "read_only_space",
Generate grokdump constants with 'make grokdump' now. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/21771002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16022 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2013-08-02 09:02:02 +00:00
}
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
# List of known V8 Frame Markers.
FRAME_MARKERS = (
"ENTRY",
Naming consistency and further small cleanups to frames.h R=mstarzinger@chromium.org Bug: Change-Id: Ia416acd8c12a3c8e3fdfabc56a4cd31cb946c88c Reviewed-on: https://chromium-review.googlesource.com/599949 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#47135}
2017-08-03 14:30:20 +00:00
"CONSTRUCT_ENTRY",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"EXIT",
[wasm][debug] Rename WasmCompiledFrame to WasmFrame Also, rename the WASM_COMPILED frame type to just WASM. R=jkummerow@chromium.org Bug: v8:10389 Change-Id: I71f16f41a69f8b0295ba34bd7d7fad71729546f2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2187613 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#67698}
2020-05-07 12:29:48 +00:00
"WASM",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"WASM_TO_JS",
[cleanup] Fix frame mismatch for WasmToJs functions There are 2 kinds of WasmToJs code: one uses a WasmFrame and the other a simple TypedFrame TF frame. This CL introduces WasmToJsFunctionFrame (as a simple TypedFrame) to dfferentiate from the WasmFrame counterpart. This was not an issue before https://crrev.com/c9c490891ab3d63fc790770cb1c76f8013ba963f since we used to use a single master function for pointer iteration. No-Tree-Checks: true Bug: v8:13243 Change-Id: I97f7e8c897159ca3cafa65ff6ddf836c5ef7b76e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3865969 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#82856}
2022-08-31 09:17:01 +00:00
"WASM_TO_JS_FUNCTION",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"JS_TO_WASM",
[wasm] Add suspend wrapper stub - Add suspend asm builtin stub, and call it from the suspending wasm-to-js wrapper - Rename frame type to match both builtins (prompt and suspend) - Add suspend bool to the import cache key R=ahaas@chromium.org CC=​​fgm@chromium.org Bug: v8:12191 Change-Id: Ie5a8ca7cbe4bcb91697e05b6470e3d632d608993 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3345004 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#78628}
2022-01-14 14:20:07 +00:00
"STACK_SWITCH",
[wasm] Add a separate frame type for debug break frames The frame created by the WasmDebugBreak builtin now has a separate frame type, which will (later) allow to inspect the spilled registers. Once Liftoff supports reference types, this frame will also need special GC support for spilled heap references. R=jkummerow@chromium.org Bug: v8:10222 Change-Id: I110e51d1e6d09b0f44dcdd1cdcaafa2eaa64fddd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083013 Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66531}
2020-03-02 11:24:13 +00:00
"WASM_DEBUG_BREAK",
[wasm] [debug] Implement calling imported wasm functions The interpreter was not able to call imported wasm functions (hitting UNIMPLEMENTED). This CL fixes this by creating a "CWasmEntry", which is signature-specific. It has JS linkage and receives the wasm code object to call and a buffer containing all arguments (similar to the interpreter entry). It loads all arguments from the buffer and calls the given code object. The c-wasm-entry code objects are cached per instance, such that we only create them once per signature. These wasm entry stubs will also allow us to call back to compiled code from the interpreter, which we might want to do to reduce the slowdown of executing wasm for debugging. R=titzer@chromium.org Bug: chromium:735792 Change-Id: I7fecec3a7bec62a9de40fff115b684759b12a28b Reviewed-on: https://chromium-review.googlesource.com/600308 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#47195}
2017-08-07 11:40:21 +00:00
"C_WASM_ENTRY",
[wasm-c-api] New call descriptor and stackframe kind So far, calls to Wasm C/C++ API functions reused the call descriptors of WasmImportWrappers, and the stack frame type of regular Wasm functions. This CL cleans that up by introducing separate implementations for both. No change in functionality or performance is expected. Change-Id: I79301fa81da52283cc776ddf19d4712372f3a58b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1632235 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#61914}
2019-05-29 10:42:21 +00:00
"WASM_EXIT",
Reland "[wasm] Allocate feedback vectors on demand" This is a reland of commit 4804c4de313c2e5e41407518a97f61abf8d33331. There are major changes since the previous attempt: - The WasmLiftoffFrameSetup (formerly WasmGetFeedbackVector) builtin now performs as much of the frame setup work as possible, to reduce generated code size for each function. - The WasmLazyCompile builtin/runtime function no longer allocates, hence gets frame type INTERNAL, and is un-handlified. Original change's description: > [wasm] Allocate feedback vectors on demand > > We previously allocated feedback vectors when instantiating the module, > or when lazily compiling a function. That's not sufficient when there > are multiple instances of the same NativeModule, or when we eagerly > tier-down all code for debugging. This patch changes the "get vector from > instance" sequence at the beginning of every Liftoff function to "get > or allocate vector"; factored into a builtin call to avoid generating > more code for every function. > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3939667 > Cr-Commit-Position: refs/heads/main@{#83610} Bug: v8:12852 Change-Id: I58a6a02a55c3e29cae3cbdafad6cf81487faccbe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3942206 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#83794}
2022-10-19 09:59:44 +00:00
"WASM_LIFTOFF_SETUP",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"INTERPRETED",
[sparkplug] Change Sparkplug to Baseline Currently we sometimes refer to baseline code or the baseline compiler by its codename (Sparkplug). The codename is fun, but we should be consistent and call things by one name or the other. Following the pattern of Ignition stuff being called "interpreter", we call Sparkplug "baseline", and leave the codename only in flags and variants. Bug: v8:11420 Change-Id: I432e5629518be7c7ad38b6acff024c91d4cfd6d3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2692186 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#72696}
2021-02-12 11:41:57 +00:00
"BASELINE",
[maglev] Add marker for maglev frames Doesn't do much at the moment beyond not being a baseline frame. Fixes a DCHECK in tiering that checks the frame type, by removing the frame lookup there (which wasn't necessary anymore). Bug: v8:7700 Change-Id: Icecfe27771923d380a7d1dc1c29aa9c5c9dfbf0f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3644618 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#80512}
2022-05-13 08:00:10 +00:00
"MAGLEV",
[maglev] Make maglev frames optimized frames Split off a TurbofanFrame from OptimizedFrame, and make MaglevFrame a subclass of OptimizedFrame. This allows it to be treated as an optimized frame by code that is looking at deoptimization data. Bug: v8:7700 Change-Id: Ia38e0f1c2cd73f054f63be81dff187d9197c1202 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3644798 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#80592}
2022-05-17 12:57:14 +00:00
"TURBOFAN",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"STUB",
[cleanup] Iterate WasmFrame and TypedFrame This CL: - Separates Wasm frame pointer iteration from TypedFrame iteration - Introduces the frame StubWithContext that correspond to a TF-optimized code without JS linkage - Fixes WasmToJsFrame to be a WasmFrame - Fixes the hack with JsToWasmFrame that calls TypedFrame when not the right builtin - Cleans up TypedFrame::Iterate Change-Id: Ie238df5188f2e2f081f5353b4538b75b6e79f64a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3859787 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#82809}
2022-08-30 07:20:19 +00:00
"TURBOFAN_STUB_WITH_CONTEXT",
Inline Array.prototype.forEach in TurboFan This CL contains a few pieces: - A new mechanism to create "BuiltinContinuation" checkpoints in TurboFan graphs, which--when triggered--swizzle the values in the the FrameState to be parameters to a typically TF-generated builtin that resumes execution to finish the slow-case functionality. - Continuation builtins that have special handling in the deoptimizer and their own new frame type to ensure that the values they need to begin executing can be stashed away and restored immediately before the builtin is called via a trampoline that runs when the continuation builtin's frame execution resumes. - An implementation of Array.prototype.forEach in TurboFan that can be used to inline it. The inlined forEach implementation uses the checkpoints mechanism described above to deopt in the middle of the forEach in the cases that optimization invariants are violated. There is a slightly different continuation stub for each deopt point in the forEach implementation to ensure the correct side-effects, i.e. that the deopt of the builtin isn't programmatically observable. Review-Url: https://codereview.chromium.org/2803853005 Cr-Commit-Position: refs/heads/master@{#45764}
2017-06-07 13:23:33 +00:00
"BUILTIN_CONTINUATION",
"JAVA_SCRIPT_BUILTIN_CONTINUATION",
[promises/deoptimizer] Support "catching" builtin continuations This CL allows builtin continuations to handle pending exceptions. This implements exception handling for the promise constructor in case of deoptimization. Bug: v8:7584 Change-Id: Ib5df5eb6606abb3f9690f294397981858dbdbf25 Reviewed-on: https://chromium-review.googlesource.com/983912 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#52340}
2018-04-04 06:31:33 +00:00
"JAVA_SCRIPT_BUILTIN_CONTINUATION_WITH_CATCH",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
"INTERNAL",
"CONSTRUCT",
"BUILTIN",
"BUILTIN_EXIT",
[cpu-profiler] Introduce NativeFrame type. The new frame type is inteneded to represent native C++ stack frames. JS code may sometimes make calls to helper native functions that do not provide any special stack layout besides the return address and frame pointer. Currently the stack iterator bails out when it sees an unknown frame. The patch allows the iterator to unwind stacks having such frames. BUG=chromium:768540 Change-Id: I9c273c7015695a6733c0a0c52b522fca7b25de0d Reviewed-on: https://chromium-review.googlesource.com/794991 Commit-Queue: Alexei Filippov <alph@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#50058}
2017-12-12 22:19:44 +00:00
"NATIVE",
[tools] Improve grokdump.py - Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
2017-03-30 11:44:00 +00:00
)
Introduce mkgrokdump to update tools/v8heapconst.py. - Migrate make grokdump to GYP and GN - Move code from d8 into stand-alone execution - Add test case to ensure it's up-to-date Review-Url: https://codereview.chromium.org/2809653003 Cr-Original-Original-Commit-Position: refs/heads/master@{#44687} Committed: https://chromium.googlesource.com/v8/v8/+/0cc0c130fa56f129c90c2a74cb01bda85df5e42a Review-Url: https://codereview.chromium.org/2809653003 Cr-Original-Commit-Position: refs/heads/master@{#44710} Committed: https://chromium.googlesource.com/v8/v8/+/477f00557458d383bd9ebef281890ba485ee882a Review-Url: https://codereview.chromium.org/2809653003 Cr-Commit-Position: refs/heads/master@{#44738}
2017-04-20 06:14:53 +00:00
# This set of constants is generated from a shipping build.
Reference in New Issue Copy Permalink