Lines Matching refs:region
43 region is, by default, assumed to be the frame state for the next
44 region. Each region is thought of as being divided into a
68 of the region. For this reason, there is usually no need to describe
71 Within a region, each instruction that affects the frame state in some
73 purpose, each instruction in the region is assigned a unique index.
152 linked list of region-descriptors. See section ``Region
215 A region descriptor is a variable length structure that describes how
216 each instruction in the region affects the frame state. Of course,
217 most instructions in a region usualy do not change the frame state and
218 for those, nothing needs to be recorded in the region descriptor. A
219 region descriptor is a structure of type
223 next region. If this is the last region, \Var{next} is \Const{NULL}.
224 \item[\Type{int32\_t} \Var{insn\_count}] The length of the region in
227 \Var{insn\_count} may be negative in the last region of a procedure
229 negative value indicates that the region covers the last \emph{N}
238 A region descriptor with an \Var{insn\_count} of zero is an
239 \emph{empty region} and such regions are perfectly legal. In fact,
241 before the start of another region.
243 A single region list can be shared across multiple procedures provided
248 Since the body length is variable, the latter region would need to
250 \Prog{libunwind} knows that the region covers the end of the procedure
253 The region descriptor is a variable length structure to make it
255 memory-allocation request. To facilitate the allocation of a region
262 This routine returns the number of bytes needed to hold a region
265 with the number of directives in a region. Instead, it is sufficient
273 at a particular point within a region. The description is in
289 \item[\Type{int32\_t} \Var{when}] The region-relative number of
292 has taken place once the first instruction in the region has
330 region-descriptor are ignored. This tag is guaranteed to have a