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

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

358 lines
13 KiB
Python
Raw Normal View History

[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
# Copyright 2017 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.
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",
18: "EXTERNAL_INTERNALIZED_STRING_WITH_ONE_BYTE_DATA_TYPE",
34: "SHORT_EXTERNAL_INTERNALIZED_STRING_TYPE",
42: "SHORT_EXTERNAL_ONE_BYTE_INTERNALIZED_STRING_TYPE",
50: "SHORT_EXTERNAL_INTERNALIZED_STRING_WITH_ONE_BYTE_DATA_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
64: "STRING_TYPE",
65: "CONS_STRING_TYPE",
66: "EXTERNAL_STRING_TYPE",
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
67: "SLICED_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
69: "THIN_STRING_TYPE",
72: "ONE_BYTE_STRING_TYPE",
73: "CONS_ONE_BYTE_STRING_TYPE",
74: "EXTERNAL_ONE_BYTE_STRING_TYPE",
75: "SLICED_ONE_BYTE_STRING_TYPE",
77: "THIN_ONE_BYTE_STRING_TYPE",
82: "EXTERNAL_STRING_WITH_ONE_BYTE_DATA_TYPE",
98: "SHORT_EXTERNAL_STRING_TYPE",
106: "SHORT_EXTERNAL_ONE_BYTE_STRING_TYPE",
114: "SHORT_EXTERNAL_STRING_WITH_ONE_BYTE_DATA_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
128: "SYMBOL_TYPE",
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
129: "HEAP_NUMBER_TYPE",
[bigint] Introduce BigInt type. BigInt is a new primitive type of arbitrary precision integers, proposed in https://tc39.github.io/proposal-bigint. This CL introduces a corresponding instance type, map, and C++ class to V8 and adds BigInt support to a few operations (see the test file). Much more is to come. Also, the concrete representation of BigInts is not yet fixed, currently a BigInt is simply a wrapped Smi. Bug: v8:6791 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ia2901948efd7808f17cfc945f0d56e23e8ae0b45 Reviewed-on: https://chromium-review.googlesource.com/657022 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#47956}
2017-09-11 13:16:27 +00:00
130: "BIGINT_TYPE",
131: "ODDBALL_TYPE",
132: "MAP_TYPE",
133: "CODE_TYPE",
134: "MUTABLE_HEAP_NUMBER_TYPE",
135: "FOREIGN_TYPE",
136: "BYTE_ARRAY_TYPE",
137: "BYTECODE_ARRAY_TYPE",
138: "FREE_SPACE_TYPE",
139: "FIXED_INT8_ARRAY_TYPE",
140: "FIXED_UINT8_ARRAY_TYPE",
141: "FIXED_INT16_ARRAY_TYPE",
142: "FIXED_UINT16_ARRAY_TYPE",
143: "FIXED_INT32_ARRAY_TYPE",
144: "FIXED_UINT32_ARRAY_TYPE",
145: "FIXED_FLOAT32_ARRAY_TYPE",
146: "FIXED_FLOAT64_ARRAY_TYPE",
147: "FIXED_UINT8_CLAMPED_ARRAY_TYPE",
148: "FIXED_DOUBLE_ARRAY_TYPE",
149: "FILLER_TYPE",
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
150: "ACCESS_CHECK_INFO_TYPE",
151: "ACCESSOR_INFO_TYPE",
152: "ACCESSOR_PAIR_TYPE",
153: "ALIASED_ARGUMENTS_ENTRY_TYPE",
154: "ALLOCATION_MEMENTO_TYPE",
155: "ALLOCATION_SITE_TYPE",
156: "ASYNC_GENERATOR_REQUEST_TYPE",
157: "CONTEXT_EXTENSION_TYPE",
158: "DEBUG_INFO_TYPE",
159: "FUNCTION_TEMPLATE_INFO_TYPE",
160: "INTERCEPTOR_INFO_TYPE",
161: "MODULE_INFO_ENTRY_TYPE",
162: "MODULE_TYPE",
163: "OBJECT_TEMPLATE_INFO_TYPE",
164: "PROMISE_REACTION_JOB_INFO_TYPE",
165: "PROMISE_RESOLVE_THENABLE_JOB_INFO_TYPE",
166: "PROTOTYPE_INFO_TYPE",
167: "SCRIPT_TYPE",
168: "STACK_FRAME_INFO_TYPE",
169: "TUPLE2_TYPE",
170: "TUPLE3_TYPE",
171: "FIXED_ARRAY_TYPE",
172: "DESCRIPTOR_ARRAY_TYPE",
173: "HASH_TABLE_TYPE",
174: "TRANSITION_ARRAY_TYPE",
175: "CELL_TYPE",
176: "CODE_DATA_CONTAINER_TYPE",
[runtime] Introduce Load/StoreHandler heap objects. They will eventually be used instead of Tuple3/FixedArray by the IC system. Bug: v8:5561, v8:7159 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I39faad1b2dc10ce7d42cb7477ea87b64d1e0b44c Reviewed-on: https://chromium-review.googlesource.com/806178 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#49908}
2017-12-06 16:52:26 +00:00
177: "FEEDBACK_VECTOR_TYPE",
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
178: "LOAD_HANDLER_TYPE",
179: "PROPERTY_ARRAY_TYPE",
180: "PROPERTY_CELL_TYPE",
181: "SHARED_FUNCTION_INFO_TYPE",
182: "SMALL_ORDERED_HASH_MAP_TYPE",
183: "SMALL_ORDERED_HASH_SET_TYPE",
184: "STORE_HANDLER_TYPE",
185: "WEAK_CELL_TYPE",
32768: "JS_PROXY_TYPE",
32769: "JS_GLOBAL_OBJECT_TYPE",
32770: "JS_GLOBAL_PROXY_TYPE",
32771: "JS_MODULE_NAMESPACE_TYPE",
33024: "JS_SPECIAL_API_OBJECT_TYPE",
33025: "JS_VALUE_TYPE",
33280: "JS_API_OBJECT_TYPE",
33281: "JS_OBJECT_TYPE",
33282: "JS_ARGUMENTS_TYPE",
33283: "JS_ARRAY_BUFFER_TYPE",
33284: "JS_ARRAY_TYPE",
33285: "JS_ASYNC_FROM_SYNC_ITERATOR_TYPE",
33286: "JS_ASYNC_GENERATOR_OBJECT_TYPE",
33287: "JS_CONTEXT_EXTENSION_OBJECT_TYPE",
33288: "JS_DATE_TYPE",
33289: "JS_ERROR_TYPE",
33290: "JS_GENERATOR_OBJECT_TYPE",
33291: "JS_MAP_TYPE",
33292: "JS_MAP_KEY_ITERATOR_TYPE",
33293: "JS_MAP_KEY_VALUE_ITERATOR_TYPE",
33294: "JS_MAP_VALUE_ITERATOR_TYPE",
33295: "JS_MESSAGE_OBJECT_TYPE",
33296: "JS_PROMISE_TYPE",
33297: "JS_REGEXP_TYPE",
33298: "JS_SET_TYPE",
33299: "JS_SET_KEY_VALUE_ITERATOR_TYPE",
33300: "JS_SET_VALUE_ITERATOR_TYPE",
33301: "JS_STRING_ITERATOR_TYPE",
33302: "JS_WEAK_MAP_TYPE",
33303: "JS_WEAK_SET_TYPE",
33304: "JS_TYPED_ARRAY_TYPE",
33305: "JS_DATA_VIEW_TYPE",
33306: "JS_TYPED_ARRAY_KEY_ITERATOR_TYPE",
33307: "JS_FAST_ARRAY_KEY_ITERATOR_TYPE",
33308: "JS_GENERIC_ARRAY_KEY_ITERATOR_TYPE",
33309: "JS_UINT8_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33310: "JS_INT8_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33311: "JS_UINT16_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33312: "JS_INT16_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33313: "JS_UINT32_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33314: "JS_INT32_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33315: "JS_FLOAT32_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33316: "JS_FLOAT64_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33317: "JS_UINT8_CLAMPED_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33318: "JS_FAST_SMI_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33319: "JS_FAST_HOLEY_SMI_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33320: "JS_FAST_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33321: "JS_FAST_HOLEY_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33322: "JS_FAST_DOUBLE_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33323: "JS_FAST_HOLEY_DOUBLE_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33324: "JS_GENERIC_ARRAY_KEY_VALUE_ITERATOR_TYPE",
33325: "JS_UINT8_ARRAY_VALUE_ITERATOR_TYPE",
33326: "JS_INT8_ARRAY_VALUE_ITERATOR_TYPE",
33327: "JS_UINT16_ARRAY_VALUE_ITERATOR_TYPE",
33328: "JS_INT16_ARRAY_VALUE_ITERATOR_TYPE",
33329: "JS_UINT32_ARRAY_VALUE_ITERATOR_TYPE",
33330: "JS_INT32_ARRAY_VALUE_ITERATOR_TYPE",
33331: "JS_FLOAT32_ARRAY_VALUE_ITERATOR_TYPE",
33332: "JS_FLOAT64_ARRAY_VALUE_ITERATOR_TYPE",
33333: "JS_UINT8_CLAMPED_ARRAY_VALUE_ITERATOR_TYPE",
33334: "JS_FAST_SMI_ARRAY_VALUE_ITERATOR_TYPE",
33335: "JS_FAST_HOLEY_SMI_ARRAY_VALUE_ITERATOR_TYPE",
33336: "JS_FAST_ARRAY_VALUE_ITERATOR_TYPE",
33337: "JS_FAST_HOLEY_ARRAY_VALUE_ITERATOR_TYPE",
33338: "JS_FAST_DOUBLE_ARRAY_VALUE_ITERATOR_TYPE",
33339: "JS_FAST_HOLEY_DOUBLE_ARRAY_VALUE_ITERATOR_TYPE",
33340: "JS_GENERIC_ARRAY_VALUE_ITERATOR_TYPE",
33341: "WASM_INSTANCE_TYPE",
33342: "WASM_MEMORY_TYPE",
33343: "WASM_MODULE_TYPE",
33344: "WASM_TABLE_TYPE",
33345: "JS_BOUND_FUNCTION_TYPE",
33346: "JS_FUNCTION_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 = {
[bigint] Introduce BigInt type. BigInt is a new primitive type of arbitrary precision integers, proposed in https://tc39.github.io/proposal-bigint. This CL introduces a corresponding instance type, map, and C++ class to V8 and adds BigInt support to a few operations (see the test file). Much more is to come. Also, the concrete representation of BigInts is not yet fixed, currently a BigInt is simply a wrapped Smi. Bug: v8:6791 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ia2901948efd7808f17cfc945f0d56e23e8ae0b45 Reviewed-on: https://chromium-review.googlesource.com/657022 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#47956}
2017-09-11 13:16:27 +00:00
0x02201: (138, "FreeSpaceMap"),
[ic] Remove extra-ic-state and Map::code_cache There are only very few custom compiled IC handlers left that go in there, and for each compiled handler we only have 1 cache hit on top25; maximally saving 60ms over 33s. Additionally we'll migrate the remaining handlers to data-driven handlers anyway. Let's try to remove this code. Bug: Change-Id: Ib874cc498015046a3ff67c83ea8b10b3c4eb7d0f Reviewed-on: https://chromium-review.googlesource.com/668409 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#48201}
2017-09-28 10:47:51 +00:00
0x02251: (132, "MetaMap"),
0x022a1: (131, "NullMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x022f1: (172, "DescriptorArrayMap"),
0x02341: (171, "FixedArrayMap"),
[runtime] Introduce instance type for descriptor arrays. This simplifies handling of DescriptorArray objects in deserializer. Bug: v8:5799 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie4f9c6903afd8273d6320e6b0e0b05231db6cc00 Reviewed-on: https://chromium-review.googlesource.com/785676 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#49605}
2017-11-23 10:45:46 +00:00
0x02391: (149, "OnePointerFillerMap"),
0x023e1: (149, "TwoPointerFillerMap"),
0x02431: (131, "UninitializedMap"),
0x02481: (8, "OneByteInternalizedStringMap"),
0x024d1: (131, "UndefinedMap"),
0x02521: (129, "HeapNumberMap"),
0x02571: (131, "TheHoleMap"),
0x025c1: (131, "BooleanMap"),
0x02611: (136, "ByteArrayMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x02661: (171, "FixedCOWArrayMap"),
0x026b1: (173, "HashTableMap"),
[runtime] Introduce instance type for descriptor arrays. This simplifies handling of DescriptorArray objects in deserializer. Bug: v8:5799 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie4f9c6903afd8273d6320e6b0e0b05231db6cc00 Reviewed-on: https://chromium-review.googlesource.com/785676 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#49605}
2017-11-23 10:45:46 +00:00
0x02701: (128, "SymbolMap"),
0x02751: (72, "OneByteStringMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x027a1: (171, "ScopeInfoMap"),
0x027f1: (181, "SharedFunctionInfoMap"),
[runtime] Introduce instance type for descriptor arrays. This simplifies handling of DescriptorArray objects in deserializer. Bug: v8:5799 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie4f9c6903afd8273d6320e6b0e0b05231db6cc00 Reviewed-on: https://chromium-review.googlesource.com/785676 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#49605}
2017-11-23 10:45:46 +00:00
0x02841: (133, "CodeMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x02891: (171, "FunctionContextMap"),
0x028e1: (175, "CellMap"),
0x02931: (185, "WeakCellMap"),
0x02981: (180, "GlobalPropertyCellMap"),
[runtime] Introduce instance type for descriptor arrays. This simplifies handling of DescriptorArray objects in deserializer. Bug: v8:5799 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie4f9c6903afd8273d6320e6b0e0b05231db6cc00 Reviewed-on: https://chromium-review.googlesource.com/785676 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#49605}
2017-11-23 10:45:46 +00:00
0x029d1: (135, "ForeignMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x02a21: (174, "TransitionArrayMap"),
[runtime] Introduce Load/StoreHandler heap objects. They will eventually be used instead of Tuple3/FixedArray by the IC system. Bug: v8:5561, v8:7159 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I39faad1b2dc10ce7d42cb7477ea87b64d1e0b44c Reviewed-on: https://chromium-review.googlesource.com/806178 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#49908}
2017-12-06 16:52:26 +00:00
0x02a71: (177, "FeedbackVectorMap"),
[runtime] Introduce instance type for descriptor arrays. This simplifies handling of DescriptorArray objects in deserializer. Bug: v8:5799 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ie4f9c6903afd8273d6320e6b0e0b05231db6cc00 Reviewed-on: https://chromium-review.googlesource.com/785676 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#49605}
2017-11-23 10:45:46 +00:00
0x02ac1: (131, "ArgumentsMarkerMap"),
0x02b11: (131, "ExceptionMap"),
0x02b61: (131, "TerminationExceptionMap"),
0x02bb1: (131, "OptimizedOutMap"),
0x02c01: (131, "StaleRegisterMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x02c51: (171, "NativeContextMap"),
0x02ca1: (171, "ModuleContextMap"),
0x02cf1: (171, "EvalContextMap"),
0x02d41: (171, "ScriptContextMap"),
0x02d91: (171, "BlockContextMap"),
0x02de1: (171, "CatchContextMap"),
0x02e31: (171, "WithContextMap"),
0x02e81: (171, "DebugEvaluateContextMap"),
0x02ed1: (171, "ScriptContextTableMap"),
[snapshot] no longer iterate strong roots twice. Previously, in order to get immortal immovable objects onto the first page, the serializer would iterate the root list twice. The first time it would prioritize immortal immovables. The second time it would serialize the rest. This does not guarantee that immortal immovable objects actually end up on the first page, and by now this is not necessary anymore, since we mark all pages created during heap init as immortal immovable pages. R=mlippautz@chromium.org Change-Id: Ie95fcd779377a75337621ba862bc1a745ed5cbaa Reviewed-on: https://chromium-review.googlesource.com/768731 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#49468}
2017-11-19 08:07:00 +00:00
0x02f21: (148, "FixedDoubleArrayMap"),
0x02f71: (134, "MutableHeapNumberMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x02fc1: (173, "OrderedHashMapMap"),
0x03011: (173, "OrderedHashSetMap"),
0x03061: (173, "NameDictionaryMap"),
0x030b1: (173, "GlobalDictionaryMap"),
0x03101: (173, "NumberDictionaryMap"),
0x03151: (173, "StringTableMap"),
0x031a1: (173, "WeakHashTableMap"),
0x031f1: (171, "SloppyArgumentsElementsMap"),
0x03241: (182, "SmallOrderedHashMapMap"),
0x03291: (183, "SmallOrderedHashSetMap"),
0x032e1: (176, "CodeDataContainerMap"),
0x03331: (33295, "JSMessageObjectMap"),
0x03381: (33281, "ExternalMap"),
[snapshot] introduce more maps for rehashing. R=mstarzinger@chromium.org Bug: v8:6593 Change-Id: Ica794c7b0d779f04647d2b2c5ce7762a537620ae Reviewed-on: https://chromium-review.googlesource.com/759793 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#49469}
2017-11-19 10:06:32 +00:00
0x033d1: (137, "BytecodeArrayMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x03421: (171, "ModuleInfoMap"),
0x03471: (175, "NoClosuresCellMap"),
0x034c1: (175, "OneClosureCellMap"),
0x03511: (175, "ManyClosuresCellMap"),
0x03561: (179, "PropertyArrayMap"),
[snapshot] introduce more maps for rehashing. R=mstarzinger@chromium.org Bug: v8:6593 Change-Id: Ica794c7b0d779f04647d2b2c5ce7762a537620ae Reviewed-on: https://chromium-review.googlesource.com/759793 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#49469}
2017-11-19 10:06:32 +00:00
0x035b1: (130, "BigIntMap"),
0x03601: (106, "NativeSourceStringMap"),
0x03651: (64, "StringMap"),
0x036a1: (73, "ConsOneByteStringMap"),
0x036f1: (65, "ConsStringMap"),
0x03741: (77, "ThinOneByteStringMap"),
0x03791: (69, "ThinStringMap"),
0x037e1: (67, "SlicedStringMap"),
0x03831: (75, "SlicedOneByteStringMap"),
0x03881: (66, "ExternalStringMap"),
0x038d1: (82, "ExternalStringWithOneByteDataMap"),
0x03921: (74, "ExternalOneByteStringMap"),
0x03971: (98, "ShortExternalStringMap"),
0x039c1: (114, "ShortExternalStringWithOneByteDataMap"),
0x03a11: (0, "InternalizedStringMap"),
0x03a61: (2, "ExternalInternalizedStringMap"),
0x03ab1: (18, "ExternalInternalizedStringWithOneByteDataMap"),
0x03b01: (10, "ExternalOneByteInternalizedStringMap"),
0x03b51: (34, "ShortExternalInternalizedStringMap"),
0x03ba1: (50, "ShortExternalInternalizedStringWithOneByteDataMap"),
0x03bf1: (42, "ShortExternalOneByteInternalizedStringMap"),
0x03c41: (106, "ShortExternalOneByteStringMap"),
0x03c91: (140, "FixedUint8ArrayMap"),
0x03ce1: (139, "FixedInt8ArrayMap"),
0x03d31: (142, "FixedUint16ArrayMap"),
0x03d81: (141, "FixedInt16ArrayMap"),
0x03dd1: (144, "FixedUint32ArrayMap"),
0x03e21: (143, "FixedInt32ArrayMap"),
0x03e71: (145, "FixedFloat32ArrayMap"),
0x03ec1: (146, "FixedFloat64ArrayMap"),
0x03f11: (147, "FixedUint8ClampedArrayMap"),
Leave spaces between instance types. We used to frequently break the ABI when we introduced new instance types because some instance types are hard-coded in v8.h. Now that we have more instance types available, we can leave some room to anticipate future new instance types. Also take this opportunity to reorder some instance types. Also see: https://github.com/nodejs/node/issues/17754 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I9b59eeab9dfcdf11d779f0b700fc5dce30d3eebe Reviewed-on: https://chromium-review.googlesource.com/833874 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#50223}
2017-12-19 13:21:23 +00:00
0x03f61: (169, "Tuple2Map"),
0x03fb1: (167, "ScriptMap"),
0x04001: (160, "InterceptorInfoMap"),
0x04051: (151, "AccessorInfoMap"),
0x040a1: (150, "AccessCheckInfoMap"),
0x040f1: (152, "AccessorPairMap"),
0x04141: (153, "AliasedArgumentsEntryMap"),
0x04191: (154, "AllocationMementoMap"),
0x041e1: (155, "AllocationSiteMap"),
0x04231: (156, "AsyncGeneratorRequestMap"),
0x04281: (157, "ContextExtensionMap"),
0x042d1: (158, "DebugInfoMap"),
0x04321: (159, "FunctionTemplateInfoMap"),
0x04371: (161, "ModuleInfoEntryMap"),
0x043c1: (162, "ModuleMap"),
0x04411: (163, "ObjectTemplateInfoMap"),
0x04461: (164, "PromiseReactionJobInfoMap"),
0x044b1: (165, "PromiseResolveThenableJobInfoMap"),
0x04501: (166, "PrototypeInfoMap"),
0x04551: (168, "StackFrameInfoMap"),
0x045a1: (170, "Tuple3Map"),
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 = {
[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
("OLD_SPACE", 0x02201): "NullValue",
("OLD_SPACE", 0x02231): "EmptyDescriptorArray",
[cleanup] Unify enum cache handling. Introduce a proper empty_descriptor_array, which has the proper layout (length is 2 and the two fields are set properly). Also add a special EnumCache class and a matching empty_enum_cache. The contract now is that we only need to check the EnumLength on the map to know whether we are allowed to use the enum cache. This greatly simplifies the handling of the enum cache (and also the descriptor arrays), especially for the future work on optimizing keyed access via the enum cache indices. Bug: v8:6702 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I5ef517a3041163cd65ef003f691139ea52233e83 Reviewed-on: https://chromium-review.googlesource.com/641030 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#47697}
2017-08-30 04:21:29 +00:00
("OLD_SPACE", 0x02251): "EmptyFixedArray",
("OLD_SPACE", 0x02261): "UninitializedValue",
("OLD_SPACE", 0x022e1): "UndefinedValue",
("OLD_SPACE", 0x02311): "NanValue",
("OLD_SPACE", 0x02321): "TheHoleValue",
("OLD_SPACE", 0x02371): "HoleNanValue",
("OLD_SPACE", 0x02381): "TrueValue",
("OLD_SPACE", 0x023f1): "FalseValue",
("OLD_SPACE", 0x02441): "empty_string",
("OLD_SPACE", 0x02459): "EmptyScopeInfo",
("OLD_SPACE", 0x02469): "ArgumentsMarker",
("OLD_SPACE", 0x024c1): "Exception",
("OLD_SPACE", 0x02519): "TerminationException",
("OLD_SPACE", 0x02579): "OptimizedOut",
("OLD_SPACE", 0x025d1): "StaleRegister",
[snapshot] no longer iterate strong roots twice. Previously, in order to get immortal immovable objects onto the first page, the serializer would iterate the root list twice. The first time it would prioritize immortal immovables. The second time it would serialize the rest. This does not guarantee that immortal immovable objects actually end up on the first page, and by now this is not necessary anymore, since we mark all pages created during heap init as immortal immovable pages. R=mlippautz@chromium.org Change-Id: Ie95fcd779377a75337621ba862bc1a745ed5cbaa Reviewed-on: https://chromium-review.googlesource.com/768731 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#49468}
2017-11-19 08:07:00 +00:00
("OLD_SPACE", 0x02651): "EmptyByteArray",
("OLD_SPACE", 0x02661): "EmptyFixedUint8Array",
("OLD_SPACE", 0x02681): "EmptyFixedInt8Array",
("OLD_SPACE", 0x026a1): "EmptyFixedUint16Array",
("OLD_SPACE", 0x026c1): "EmptyFixedInt16Array",
("OLD_SPACE", 0x026e1): "EmptyFixedUint32Array",
("OLD_SPACE", 0x02701): "EmptyFixedInt32Array",
("OLD_SPACE", 0x02721): "EmptyFixedFloat32Array",
("OLD_SPACE", 0x02741): "EmptyFixedFloat64Array",
("OLD_SPACE", 0x02761): "EmptyFixedUint8ClampedArray",
("OLD_SPACE", 0x02781): "EmptyScript",
("OLD_SPACE", 0x02809): "UndefinedCell",
("OLD_SPACE", 0x02819): "EmptySloppyArgumentsElements",
("OLD_SPACE", 0x02839): "EmptySlowElementDictionary",
[snapshot] introduce more maps for rehashing. R=mstarzinger@chromium.org Bug: v8:6593 Change-Id: Ica794c7b0d779f04647d2b2c5ce7762a537620ae Reviewed-on: https://chromium-review.googlesource.com/759793 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#49469}
2017-11-19 10:06:32 +00:00
("OLD_SPACE", 0x02881): "EmptyOrderedHashMap",
("OLD_SPACE", 0x028a9): "EmptyOrderedHashSet",
("OLD_SPACE", 0x028d1): "EmptyPropertyCell",
("OLD_SPACE", 0x028f9): "EmptyWeakCell",
[cleanup] Rename "array protector" to "no elements protector". The "array protector" now guards the Object.prototype, the Array.prototype and the String.prototype, so the name was a bit misleading nowadays. So the new name "no elements protector" was chosen. Bug: v8:6936, v8:7014, v8:7027 Change-Id: I9a9d7caa2caf0ac9e78cc6658de2f0506970dfa2 Reviewed-on: https://chromium-review.googlesource.com/778162 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#49471}
2017-11-20 08:42:53 +00:00
("OLD_SPACE", 0x02969): "NoElementsProtector",
[snapshot] introduce more maps for rehashing. R=mstarzinger@chromium.org Bug: v8:6593 Change-Id: Ica794c7b0d779f04647d2b2c5ce7762a537620ae Reviewed-on: https://chromium-review.googlesource.com/759793 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#49469}
2017-11-19 10:06:32 +00:00
("OLD_SPACE", 0x02991): "IsConcatSpreadableProtector",
("OLD_SPACE", 0x029a1): "SpeciesProtector",
("OLD_SPACE", 0x029c9): "StringLengthProtector",
("OLD_SPACE", 0x029d9): "FastArrayIterationProtector",
("OLD_SPACE", 0x029e9): "ArrayIteratorProtector",
("OLD_SPACE", 0x02a11): "ArrayBufferNeuteringProtector",
("OLD_SPACE", 0x02a39): "InfinityValue",
("OLD_SPACE", 0x02a49): "MinusZeroValue",
("OLD_SPACE", 0x02a59): "MinusInfinityValue",
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",
"OPTIMIZED",
"WASM_COMPILED",
"WASM_TO_JS",
[wasm] Distinguish WASM_TO_WASM_FUNCTION Identify wasm-to-wasm wrappers separately from wasm-to-js ones. Bug: Change-Id: I853ed8fb999297f8a951ebb0e5be1c99bfacc18c Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Reviewed-on: https://chromium-review.googlesource.com/782680 Reviewed-by: Brad Nelson <bradnelson@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Mircea Trofin <mtrofin@chromium.org> Cr-Commit-Position: refs/heads/master@{#49580}
2017-11-21 18:21:22 +00:00
"WASM_TO_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
"JS_TO_WASM",
"WASM_INTERPRETER_ENTRY",
[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",
[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",
"STUB",
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",
[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",
"ARGUMENTS_ADAPTOR",
"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