Lines Matching full:descriptions
1 # Allow Location Descriptions on the DWARF Expression Stack <!-- omit in toc -->
14 that allows both typed values and location descriptions to be manipulated on the
15 evaluation stack. Both single and multiple location descriptions are supported
17 support the full generality of location descriptions. This is done in a manner
21 The extension permits operations to act on location descriptions in an
205 DWARF defines the locations of objects in terms of location descriptions.
220 values, location descriptions are not pushed on the stack. Instead they are
221 conceptually placed in a location area. Unlike values, location descriptions do
278 DWARF defines composite location descriptions that can have one or more parts.
304 bytes. If there are no other location descriptions in the location area, and no
366 operations on location descriptions.
546 With location descriptions on the stack, the definition of `DW_OP_use_location`
732 With location descriptions on the stack, the definition of
769 model to allow location descriptions to be manipulated on the stack. It presents
777 descriptions, the extension defines a uniform way to handle all location kinds.
779 composite location descriptions.
816 Existing DWARF expression operations that create location descriptions are
817 changed to pop and push location descriptions on the stack. For example, the
821 New operations that act on location descriptions can be added. For example, a
826 To allow incremental and nested creation of composite location descriptions, a
838 result from allowing location descriptions on the stack.
1037 multiple composite location descriptions on the stack which can be used to pass
1039 beneficial to factor the incrementally creation of location descriptions.
1085 All operations that act on location descriptions work with memory locations
1091 Generalizing memory location descriptions to include an address space component
1095 operation works on memory location descriptions that have an address space just
1114 With the generalization of location descriptions on the stack, it is possible to
1183 operations to be used to factor the creation of location descriptions. The
1205 create location descriptions out of other location descriptions in a general
1215 out of two location descriptions, a bit mask value, and an element size. The
1228 composite location description out of two location descriptions, an offset
1230 equivalent to one of the location descriptions, but with the other location
1251 is adequate as non-memory location descriptions can only be computed as the last
1254 However, allowing location descriptions on the stack permits non-memory location
1255 descriptions to be used in the middle of expression evaluation. For example, the
1259 descriptions.
1269 to allow an entry to be one or more single location descriptions. In doing this,
1273 All operations that act on location descriptions are extended to act on multiple
1274 single location descriptions. For example, the DW_OP_offset operation adds the
1276 read the storage of one of the single location descriptions, since multiple
1277 single location descriptions must all hold the same value. Similarly, if the
1279 descriptions, the consumer can ensure any updates are done to all of them, and
1300 > location descriptions that support multiple places.
1337 > descriptions having an undefined location description. Then operations that
1499 This is a list of values or location descriptions that will be pushed on the
1507 The result is undefined if any location descriptions are invalid (see [2.5.3
1569 descriptions.
1571 Location descriptions can consist of one or more single location descriptions.
1612 <i>Location descriptions are a language independent representation of addressing
1651 descriptions (since they all refer to location storage that has the same value),
1652 but must write any changed value to all the single location descriptions.</i>
1702 avoid such problems is to recompute location descriptions associated with
1790 > descriptions.
1793 > location descriptions, then would need to define that the composite location
1987 > descriptions), and the `DW_AT_proc` attribute expression is always
2226 one of the single location descriptions SL of L.
2241 > storage. Particularly since these extensions extend location descriptions
2265 for special rules concerning implicit location descriptions created by the
2388 This section describes the operations that push location descriptions on the
2591 describe using ordinary DWARF location descriptions. Instead of forcing
2753 descriptions created by the `DW_OP_implicit_pointer` operation.
2755 Note: Since location descriptions are allowed on the stack, the
2808 descriptions.</i>
2888 one or more single location descriptions SL. If there are more than one SL then
2938 location descriptions from any other location description, including those that
2939 have multiple single location descriptions, and those that have composite
2940 location descriptions.</i>
2996 > NOTE: Since these extensions allow location descriptions to be entries on
2997 > the stack, a simpler operation to create composite location descriptions
3001 > complexities of incomplete composite location descriptions, but it may
3106 single location descriptions of the location description result of each
3387 > description, and those with single location descriptions that are of any
3480 > including those with composite and implicit location descriptions.
3983 > location descriptions into DWARF expressions.
3988 > the unification of location descriptions into DWARF expressions.
4013 - [Allow Location Descriptions on the DWARF Expression Stack](https://llvm.org/docs/AMDGPUDwarfExte…