\begin{longtable}{ll}
\textbf{Date} & \textbf{Issue Incorporated or Other Change} \\ \hline \\
\endhead
-5/14-16/2015 & More editorial work IV \\
+6/5-7/2015 & Add color to defining occurrence(s) of DWARF names. Choices include: \\
+ & \textcolor{red}{red}, \textcolor{green}{green}, \textcolor{blue}{blue},
+ \textcolor{yellow}{yellow}, \textcolor{cyan}{cyan}, \textcolor{magenta}{magenta} \\
+5/19-6/4/2015 & More editorial work V \\
+5/14-16/2015 & More editorial work IV (release to committee) \\
5/12-13/2015 & More editorial work III (Appendix B)\\
5/3-7/2015 & More editorial work II \\
4/24-26/2015 & More editorial work \\
a declaration, since the complete type is unknown and its
signature is therefore unavailable. There is also a reference
to \texttt{N::C}, using
-\DWFORMrefsigeight{} to
-refer to the type signature
-\addtoindexx{type signature}
-for that type.
+\DWFORMrefsigeight{} to refer to the type signature
+\addtoindexx{type signature} for that type.
\begin{figure}
\figurepart{1}{3}
the name attribute is omitted or its value consists of a single
zero byte.
-\item A \DWATexternal{} attribute,
+\item A \DWATexternalDEFN{} attribute,
\hypertarget{chap:DWATexternalexternalvariable}{}
which
\addtoindexx{external attribute}
represent.
\needlines{4}
-\item A \DWATvariableparameter{}
+\item A \DWATvariableparameterDEFN{}
attribute\addtoindexx{variable parameter attribute},
which is a \livelink{chap:classflag}{flag},
if a formal parameter entry represents a parameter whose
The absence of this attribute implies that the parameter\textquoteright s
value in the calling function cannot be modified by the callee.
-\item A \DWATisoptional{} attribute,
+\item A \DWATisoptionalDEFN{} attribute,
\hypertarget{chap:DWATisoptionaloptionalparameter}{}
which
\addtoindexx{is optional attribute}
is a \livelink{chap:classflag}{flag}, if a
parameter entry represents an \addtoindex{optional parameter}.
-\item A \DWATdefaultvalue{} attribute
+\item A \DWATdefaultvalueDEFN{} attribute
\addtoindexx{default value attribute}
for
\addtoindexx{formal parameter entry!with default value}
\textit{For a constant form there is no way to
express the absence of a default value.}
-\item A \DWATconstvalue{} attribute
-for
+\item A \DWATconstvalueDEFN{} attribute
+\addtoindexx{constant value attribute}
\hypertarget{chap:DWATconstvalueconstantobject}{}
-an entry describing a
+for an entry describing a
variable or formal parameter whose value is constant and not
represented by an object in the address space of the program,
or an entry describing a named constant. (Note that such
to a constant actual parameter of a call that is inlined.
}
-\item A \DWATstartscope{}
-attribute if the scope of
-\addtoindexx{start scope attribute}
-an
+\item A \DWATstartscopeDEFN{}\addtoindexx{start scope attribute}
\hypertarget{chap:DWATstartscopeobjectdeclaration}{}
-object is smaller than (that is, is a subset of the addresses
-of) the scope most closely enclosing the object. There are
-two cases:
+attribute if the address range for the scope of an
+object is a subset of the address range for the
+the lexical scope most closely enclosing the object.
+There are two cases:
\begin{enumerate}[a) ]
-\item If the scope of the object entry includes all of the
-containing scope except for a contiguous sequence of bytes at
-the beginning of that containing scope, then the scope of the
-object is specified using a value of class constant. If the
-containing scope is contiguous, the value of this attribute
-is the offset in bytes of the beginning of the scope for the
-object from the low PC value of the debugging information
-entry that defines its scope. If the containing scope
-is non-contiguous
+\item If address range for the scope of the object entry
+includes all of addresses for the containing scope except
+for a contiguous sequence of bytes at the beginning of the
+address range for the containing scope, then the address is
+specified using a value of class constant. If the address
+range for the containing scope is contiguous, the value of
+this attribute is the offset in bytes of the beginning of
+the address range for the scope of the object from the low
+PC value of the debugging information entry that defines
+that containing scope. If the address range of the containing
+scope is non-contiguous
(see \refersec{chap:noncontiguousaddressranges})
-the value of this
-attribute is the offset in bytes of the beginning of the scope
-for the object from the beginning of the first \addtoindex{range list} entry
-that is not a base selection entry, a default selection entry or an end-of-list entry.
+the value of this attribute is the offset in bytes of the
+beginning of the address range for the scope of the object
+from the beginning of the first \addtoindex{range list} entry
+for the containing scope that is not a base selection entry,
+a default selection entry or an end-of-list entry.
\needlines{4}
-\item Otherwise, the scope of the object is specified using
-a value of class \livelink{chap:classrangelistptr}{rangelistptr}.
-This value indicates the
-beginning of a \addtoindex{range list}
+\item Otherwise, the set of addresses for the scope of the
+object is specified using a value of class \CLASSrangelistptr{}.
+This value indicates the beginning of a \addtoindex{range list}
(see \ref{chap:noncontiguousaddressranges}).
\end{enumerate}
an object may not require its own \addtoindex{range list} even when the
containing scope is non\dash contiguous.}
-\item A \DWATendianity{} attribute,
-whose value
-\hypertarget{chap:DWATendianityendianityofdata}{}
-is a constant
+\item A \DWATendianityDEFN{} attribute,
\addtoindexx{endianity attribute}
-that
+\hypertarget{chap:DWATendianityendianityofdata}{}
+whose value is a constant that
\addtoindexx{big-endian encoding|see{endianity attribute}}
-specifies
-the endianity of the object. The value of
-this attribute specifies an ABI\dash defined
-byte ordering \addtoindexx{ordering attribute} for
+specifies the endianity of the object. The value of
+this attribute specifies an ABI-defined
+\byteorder{ing} \addtoindexx{ordering attribute} for
the value of the object. If omitted, the default endianity
of data for the given type is assumed.
\caption{Endianity attribute values}
\label{tab:endianityattributevalues}
\centering
-\begin{tabular}{l|p{9cm}}
+\begin{tabular}{l|P{9cm}}
\hline
Name&Meaning\\ \hline
\DWENDdefaultTARG{} & Default endian encoding
for different architectures.
\needlines{6}
-\item A \DWATconstexpr{} attribute,
-which
+\item A \DWATconstexprDEFN{} attribute,
+\addtoindex{constant expression attribute}
\hypertarget{chap:DWATconstexprcompiletimeconstantobject}{}
-is a \CLASSflag, if a
+which is a \CLASSflag, if a
variable entry represents a \addtoindex{C++} object declared with the
\texttt{constexpr} specifier. This attribute indicates that the
variable can be evaluated as a compile\dash time constant.
correspond to in the source program.
Each namelist item entry contains a
-\DWATnamelistitem{} attribute
+\DWATnamelistitemDEFN{} attribute
\addtoindexx{namelist item attribute}
whose
\addtoindexx{namelist item entry}
To ensure that extensions added by one vendor may be safely
ignored by consumers that do not understand those extensions,
-the following rules should be followed:
+the following rules must be followed:
\begin{enumerate}[1. ]
-\item New attributes should be added in such a way that a
+\item New attributes are added in such a way that a
debugger may recognize the format of a new attribute value
without knowing the content of that attribute value.
-\item The semantics of any new attributes should not alter
+\item The semantics of any new attributes do not alter
the semantics of previously existing attributes.
-\item The semantics of any new tags should not conflict with
+\item The semantics of any new tags do not conflict with
the semantics of previously existing tags.
-\item Do not add any new forms of attribute value.
+\item New forms of attribute value are not added.
\end{enumerate}
forms, base type encodings, location operations, languages,
line number program opcodes, macro information entries and tag
names to represent an error condition or unknown value. DWARF
-does not specify names for these reserved values, since they
-do not represent valid encodings for the given type and should
+does not specify names for these reserved values, because they
+do not represent valid encodings for the given type and do
not appear in DWARF debugging information.
opcode is a reference to a location within the virtual address space
of the program, and requires relocation.
- The \dotdebugstroffsets{} section contains a list of string offsets,
+\item The \dotdebugstroffsets{} section contains a list of string offsets,
each of which is an offset of a string in the \dotdebugstr{} section. Each
of these offsets requires relocation. Depending on the implementation,
these relocations may be implicit (that is, the producer may not need to
applies also to the corresponding split DWARF section (for example,
\dotdebuginfodwo).
+Split DWARF object files do not get linked with any other files,
+therefore references between sections must not make use of
+normal object file relocation information.
+
\subsection{Executable Objects}
\label{chap:executableobjects}
The relocated addresses in the debugging information for an
A DWARF package file is itself an object file, using the
\addtoindexx{package files}
\addtoindexx{DWARF package files}
-same object file format (including byte order) as the
+same object file format (including \byteorder) as the
corresponding application binary. It consists only of a file
header, section table, a number of DWARF debug information
sections, and two index sections.
various debug information sections. Each contribution is stored
as an offset within its corresponding section and a size.
-Each compilation unit set may contain contributions from the
+Each \compunitset{} may contain contributions from the
following sections:
\begin{alltt}
\dotdebuginfodwo{} (required)
\dotdebugmacrodwo
\end{alltt}
-\textit{Note that a set is not able to represent \dotdebugmacinfo{}
+\textit{Note that a \compunitset{} is not able to represent \dotdebugmacinfo{}
information from \DWARFVersionIV{} or earlier formats.}
\subsubsection{The Type Unit (TU) Index Section}
information sections. Each contribution is stored as an offset
within its corresponding section and a size.
-Each type unit set may contain contributions from the following
+Each \typeunitset{} may contain contributions from the following
sections:
\begin{alltt}
\dotdebuginfodwo{} (required)
\subsubsection{Format of the CU and TU Index Sections}
Both index sections have the same format, and serve to map a
64-bit signature to a set of contributions to the debug sections.
-Each section begins with a header, followed by a hash table of
+Each index section begins with a header, followed by a hash table of
signatures, a parallel table of indexes, a table of offsets, and
a table of sizes. The index sections are aligned at 8-byte
-boundaries in the file.
+boundaries in the DWARF package file.
\needlines{6}
The index section header contains the following fields:
\hspace{0.3cm}$2^k\ \ >\ \ 3*U/2$
The hash table begins at offset 16 in the section, and consists
-of an array of $S$ 64-bit slots. Each slot contains a 64-bit
+of an array of $S$ 8-byte slots. Each slot contains a 64-bit
signature.
-% (using the byte order of the application binary).
+% (using the \byteorder{} of the application binary).
The parallel table of indices begins immediately after the hash table
(at offset \mbox{$16 + 8 * S$} from the beginning of the section), and
-consists of an array of $S$ 32-bit slots,
+consists of an array of $S$ 4-byte slots,
% (using the byte order of the application binary),
corresponding 1-1 with slots in the hash
table. Each entry in the parallel table contains a row index into
\needlines{4}
The table of offsets begins immediately following the parallel
table (at offset \mbox{$16 + 12 * S$} from the beginning of the section).
-The table is a two-dimensional array of 32-bit words,
+The table is a two-dimensional array of 4-byte words,
%(using the byte order of the application binary),
with $C$ columns and $U + 1$
rows, in row-major order. Each row in the array is indexed
\end{longtable}
\end{centering}
-The offsets provided by the CU and TU index sections are the base
-offsets for the contributions made by each CU or TU to the
+The offsets provided by the CU and TU index sections are the
+base offsets for the contributions made by each CU or TU to the
corresponding section in the package file. Each CU and TU header
-contains an \texttt{abbrev\_offset} field, used to find the abbreviations
+contains a \HFNdebugabbrevoffset{} field, used to find the abbreviations
table for that CU or TU within the contribution to the
-\dotdebugabbrevdwo{} section for that CU or TU, and should be
+\dotdebugabbrevdwo{} section for that CU or TU, and are
interpreted as relative to the base offset given in the index
section. Likewise, offsets into \dotdebuglinedwo{} from
-\DWATstmtlist{} attributes should be interpreted as relative to
+\DWATstmtlist{} attributes are interpreted as relative to
the base offset for \dotdebuglinedwo{}, and offsets into other debug
-sections obtained from DWARF attributes should also be
+sections obtained from DWARF attributes are also
interpreted as relative to the corresponding base offset.
The table of sizes begins immediately following the table of
offsets, and provides the sizes of the contributions made by each
CU or TU to the corresponding section in the package file. Like
-the table of offsets, it is a two-dimensional array of 32-bit
+the table of offsets, it is a two-dimensional array of 4-byte
words, with $C$ columns and $U$ rows, in row-major order. Each row in
the array is indexed starting from 1 (row 0 of the table of
offsets also serves as the key for the table of sizes).
\needlines{4}
A DWARF \addtoindex{supplementary object file} is itself an object file,
using the same object
-file format, byte order, and size as the corresponding application executables
+file format, \byteorder{}, and size as the corresponding application executables
or shared libraries. It consists only of a file header, section table, and
a number of DWARF debug information sections. Both the
\addtoindex{supplementary object file}
attributes to refer to them and \DWFORMstrpsup{} form attributes to
refer to strings that are used by debug information of multiple
executables or shared object files. Within the \addtoindex{supplementary object file}'s
-debugging sections, form \DWFORMrefsup{} or \DWFORMstrpsup{} should
-not be used, and all reference forms referring to some other sections
+debugging sections, form \DWFORMrefsup{} or \DWFORMstrpsup{} are
+not used, and all reference forms referring to some other sections
refer to the local sections in the \addtoindex{supplementary object file}.
-In macro information, \DWMACROdefineindirectsup{} or
-\DWMACROundefindirectsup{} opcodes can refer to strings in the
+In macro information, \DWMACROdefinesup{} or
+\DWMACROundefsup{} opcodes can refer to strings in the
\dotdebugstr{} section of the \addtoindex{supplementary object file},
-or \DWMACROtransparentincludesup{}
+or \DWMACROimportsup{}
can refer to \dotdebugmacro{} section entries. Within the
\dotdebugmacro{} section of a \addtoindex{supplementary object file},
-\DWMACROdefineindirect{} and \DWMACROundefindirect{}
-opcodes refer to the local \dotdebugstr{} section, not the one in
+\DWMACROdefinestrp{} and \DWMACROundefstrp{}
+opcodes refer to the local \dotdebugstr{} section in that
+supplementary file, not the one in
the executable or shared object file.
There are two closely related file formats. In the 32-bit DWARF
format, all values that represent lengths of DWARF sections
and offsets relative to the beginning of DWARF sections are
-represented using 32-bits. In the 64-bit DWARF format, all
+represented using four bytes. In the 64-bit DWARF format, all
values that represent lengths of DWARF sections and offsets
relative to the beginning of DWARF sections are represented
-using 64-bits. A special convention applies to the initial
+using eight bytes. A special convention applies to the initial
length field of certain DWARF sections, as well as the CIE and
FDE structures, so that the 32-bit and 64-bit DWARF formats
can coexist and be distinguished within a single linked object.
\addtoindex{initial length} field (see
\addtoindexx{initial length!encoding}
Section \ref{datarep:initiallengthvalues} on page \pageref{datarep:initiallengthvalues})
-is an unsigned 32-bit integer (which
+is an unsigned 4-byte integer (which
must be less than \xfffffffzero); in the 64-bit DWARF format,
-an \addtoindex{initial length} field is 96 bits in size,
+an \addtoindex{initial length} field is 12 bytes in size,
and has two parts:
\begin{itemize}
-\item The first 32-bits have the value \xffffffff.
+\item The first four bytes have the value \xffffffff.
-\item The following 64-bits contain the actual length
-represented as an unsigned 64-bit integer.
+\item The following eight bytes contain the actual length
+represented as an unsigned 8-byte integer.
\end{itemize}
\textit{This representation allows a DWARF consumer to dynamically
in the headers of DWARF sections (other than initial length
\addtoindexx{initial length}
fields) are listed following. In the 32-bit DWARF format these
-are 32-bit unsigned integer values; in the 64-bit DWARF format,
-they are 64-bit unsigned integer values.
+are 4-byte unsigned integer values; in the 64-bit DWARF format,
+they are 8-byte unsigned integer values.
\begin{center}
\begin{tabular}{lll}
\item Within the body of the \dotdebuginfo{}
section, certain forms of attribute value depend on the choice
of DWARF format as follows. For the 32-bit DWARF format,
-the value is a 32-bit unsigned integer; for the 64-bit DWARF
-format, the value is a 64-bit unsigned integer.
+the value is a 4-byte unsigned integer; for the 64-bit DWARF
+format, the value is an 8-byte unsigned integer.
\begin{center}
\begin{tabular}{lp{6cm}}
Form & Role \\ \hline
\needlines{5}
\item Within the body of the \dotdebugline{} section, certain forms of content
description depend on the choice of DWARF format as follows: for the
-32-bit DWARF format, the value is a 32-bit unsigned integer; for the
-64-bit DWARF format, the value is a 64-bit unsigned integer.
+32-bit DWARF format, the value is a 4-byte unsigned integer; for the
+64-bit DWARF format, the value is a 8-byte unsigned integer.
\begin{center}
\begin{tabular}{lp{6cm}}
Form & Role \\ \hline
(TUs), which represents an offset in the
\dotdebuginfo{}
section, depends on the DWARF format as follows: in the
-32-bit DWARF format, each entry is a 32-bit unsigned integer;
-in the 64-bit DWARF format, it is a 64-bit unsigned integer.
+32-bit DWARF format, each entry is a 4-byte unsigned integer;
+in the 64-bit DWARF format, it is a 8-byte unsigned integer.
\needlines{4}
\item In the body of the \dotdebugstroffsets{} and \dotdebugstroffsetsdwo{}
sections, the size of entries in the body depend on the DWARF
-format as follows: in the 32-bit DWARF format, entries are 32-bit
+format as follows: in the 32-bit DWARF format, entries are 4-byte
unsigned integer values; in the 64-bit DWARF format, they are
-64-bit unsigned integers.
+8-byte unsigned integers.
\item In the body of the \dotdebugaddr{}, \dotdebugloc{} and \dotdebugranges{}
sections, the contents of the address size fields depends on the
\textit{This field is new in \DWARFVersionV.}
\needlines{4}
-\item \addttindex{debug\_abbrev\_offset} (\livelink{datarep:sectionoffsetlength}{section offset}) \\
-\addttindexx{debug\_abbrev\_offset}
+\item \HFNdebugabbrevoffset{} (\livelink{datarep:sectionoffsetlength}{section offset}) \\
A
\addtoindexx{section offset!in .debug\_info header}
4-byte or 8-byte unsigned offset into the
\textit{This field is new in \DWARFVersionV.}
\needlines{4}
-\item \addttindex{debug\_abbrev\_offset} (\livelink{datarep:sectionoffsetlength}{section offset}) \\
-\addttindexx{debug\_abbrev\_offset}
+\item \HFNdebugabbrevoffset{} (\livelink{datarep:sectionoffsetlength}{section offset}) \\
A
\addtoindexx{section offset!in .debug\_info header}
4-byte or 8-byte unsigned offset into the
\item \texttt{type\_signature} (8-byte unsigned integer) \\
\addttindexx{type\_signature}
\addtoindexx{type signature}
-A 64-bit unique signature (see Section
+A unique 64-bit signature (see Section
\refersec{datarep:typesignaturecomputation})
of the type described in this type
unit.
\livelink{chap:classexprloc}{exprloc}
\addtoindexx{rank attribute} \\
\DWATstroffsetsbase~\ddag&0x72&
- \livelinki{chap:classstring}{stroffsetsptr}{stroffsetsptr class}
+ \livelinki{chap:classstroffsetsptr}{stroffsetsptr}{stroffsetsptr class}
\addtoindexx{string offsets base!encoding} \\
\DWATaddrbase~\ddag &0x73&
\livelinki{chap:classaddrptr}{addrptr}{addrptr class}
Table \refersec{tab:attributeencodings}
determines the class of the form.
+In the form descriptions that follow, some forms are said
+to depend in part on the value of an attribute of the
+\definition{\associatedcompilationunit}:
+\begin{itemize}
+\item
+In the case of a \splitDWARFobjectfile{}, the associated
+compilation unit is the skeleton compilation unit corresponding
+to the containing unit.
+\item Otherwise, the associated compilation unit
+is the containing unit.
+\end{itemize}
\needlines{4}
-Each possible form belongs to one or more of the following classes:
+Each possible form belongs to one or more of the following classes
+(see Table \refersec{tab:classesofattributevalue} for a summary of
+the purpose and general usage of each class):
\begin{itemize}
\item \livelinki{chap:classaddress}{address}{address class} \\
index into an array of addresses in the \dotdebugaddr{} section.
The index is relative to the value of the \DWATaddrbase{} attribute
of the associated compilation unit.
+
\end{itemize}
\needlines{5}
constant, or anything else. A consumer must use context to
know how to interpret the bits, which if they are target
machine data (such as an integer or floating-point constant)
-will be in target machine byte\dash order.
+will be in target machine \byteorder.
\textit{If one of the \DWFORMdataTARG\textless n\textgreater
forms is used to represent a
\textit{This encoding is equally suitable whether the target machine
architecture represents data in big\dash\ endian or little\dash endian
-order. It is \doublequote{little\dash endian} only in the sense that it
+\byteorder. It is \doublequote{little\dash endian} only in the sense that it
avoids using space to represent the \doublequote{big} end of an
unsigned integer, when the big end is all zeroes or sign
extension bits.}
that an additional byte follows.
-The encoding for signed, two\textquoteright s complement LEB128
+The encoding for signed, two\textquoteright{s} complement LEB128
(\addtoindex{SLEB128}) \addtoindexx{LEB128!signed, encoding as}
numbers is similar, except that the criterion for discarding
high order bytes is not whether they are zero, but whether
they consist entirely of sign extension bits. Consider the
-32-bit integer -2. The three high level bytes of the number
+4-byte integer -2. The three high level bytes of the number
are sign extension, thus LEB128 would represent it as a single
byte containing the low order 7 bits, with the high order
bit cleared to indicate the end of the byte stream. Note
The encodings of the
\hypertarget{chap:DWATencodingencodingofbasetype}{}
-constants used in
-\addtoindexx{encoding attribute}
-the
-\DWATencoding{}
-attribute are given in
+constants used in the
+\DWATencodingDEFN{} attribute\addtoindexx{encoding attribute}
+are given in
Table \refersec{tab:basetypeencodingvalues}
\begin{centering}
The size in bytes of the abbreviations table.
\item \texttt{augmentation\_string\_size} (\HFTuword) \\
-The size in bytes of the augmentation string. This value should be
+The size in bytes of the augmentation string. This value is
rounded up to a multiple of 4.
\item \texttt{augmentation\_string} (\HFTaugstring) \\
A vendor-specific augmentation string, which provides additional
information about the contents of this index. If provided, the string
-should begin with a 4-character vendor ID. The remainder of the
+begins with a 4-character vendor ID. The remainder of the
string is meant to be read by a cooperating consumer, and its
contents and interpretation are not specified here. The
-string should be padded with null characters to a multiple of
+string is padded with null characters to a multiple of
four bytes in length.
\end{enumerate}
\hline \ddag~\textit{New in DWARF Version 5}
\endlastfoot
-\DWMACROdefine~\ddag &0x01 \\
-\DWMACROundef~\ddag &0x02 \\
-\DWMACROstartfile~\ddag &0x03 \\
-\DWMACROendfile~\ddag &0x04 \\
-\DWMACROdefineindirect~\ddag &0x05 \\
-\DWMACROundefindirect~\ddag &0x06 \\
-\DWMACROtransparentinclude~\ddag &0x07 \\
-\DWMACROdefineindirectsup~\ddag &0x08 \\
-\DWMACROundefindirectsup~\ddag &0x09 \\
-\DWMACROtransparentincludesup~\ddag&0x0a \\
-\DWMACROdefineindirectx~\ddag &0x0b \\
-\DWMACROundefindirectx~\ddag &0x0c \\
-\DWMACROlouser~\ddag &0xe0 \\
-\DWMACROhiuser~\ddag &\xff \\
+\DWMACROdefine~\ddag &0x01 \\
+\DWMACROundef~\ddag &0x02 \\
+\DWMACROstartfile~\ddag &0x03 \\
+\DWMACROendfile~\ddag &0x04 \\
+\DWMACROdefinestrp~\ddag &0x05 \\
+\DWMACROundefstrp~\ddag &0x06 \\
+\DWMACROimport~\ddag &0x07 \\
+\DWMACROdefinesup~\ddag &0x08 \\
+\DWMACROundefsup~\ddag &0x09 \\
+\DWMACROimportsup~\ddag &0x0a \\
+\DWMACROdefinestrx~\ddag &0x0b \\
+\DWMACROundefstrx~\ddag &0x0c \\
+\DWMACROlouser~\ddag &0xe0 \\
+\DWMACROhiuser~\ddag &\xff \\
\end{longtable}
\end{centering}
\DWATdiscrlist,
\DWATdiscrvalue,
\DWATencoding,
-\DWATenumclass,
\DWATendianity,
+\DWATenumclass,
\DWATexplicit,
\DWATisoptional,
\DWATlocation,
If an implementation defines any vendor-specific attributes,
any such attributes that are essential to the definition of
-the type should also be included at the end of the above list,
+the type are also included at the end of the above list,
in their own alphabetical suborder.
An attribute that refers to another type entry T is processed
Appendix \refersec{app:typesignaturecomputationgrammar}.
}
-\textit{An attribute that refers to another type entry should
-be recursively processed or replaced with the name of the
+\textit{An attribute that refers to another type entry is
+recursively processed or replaced with the name of the
referent (in Step 4, 5 or 6). If neither treatment applies to
an attribute that references another type entry, the entry
-that contains that attribute should not be considered for a
+that contains that attribute is not suitable for a
separate \addtoindex{type unit}.}
\textit{If a debugging information entry contains an attribute from
the list above that would require an unsupported form, that
-entry should not be considered for a separate
+entry is not suitable for a separate
\addtoindex{type unit}.}
-\textit{A type should be considered for a separate
+\textit{A type is suitable for a separate
\addtoindex{type unit} only
if all of the type entries that it contains or refers to in
-Steps 6 and 7 can themselves each be considered for a separate
+Steps 6 and 7 are themselves suitable for a separate
\addtoindex{type unit}.}
\needlines{4}
type is highly unlikely to produce the same string).}
\needlines{6}
-\textit{A debugging information entry should not be placed in a
+\textit{A debugging information entry is not be placed in a
separate \addtoindex{type unit}
if any of the following apply:}
is defined in \addtoindex{C} as shown in
Figure \referfol{fig:nametablehashfunctiondefinition}.\footnote{
This hash function is sometimes informally known as the
-"\addtoindex{TJB hash function}" or the "\addtoindex{Berstein hash function}"
+"\addtoindex{DJB hash function}" or the "\addtoindex{Berstein hash function}"
(see, for example,
\hrefself{http://en.wikipedia.org/wiki/List\_of\_hash\_functions} or
\hrefself{http://stackoverflow.com/questions/10696223/reason-for-5381-number-in-djb-hash-function)}.}
%
\node(zsectara) at ( 0, 15.0) [sect] {\dotdebugaranges};
\node(zlinka) at ( 0, 13.5) [link] {To compilation unit~~(a)};
-\node(zsectinf) at ( 0, 7.5) [sect] {\begin{tabular}{c}
- \dotdebuginfo
+\node(zsectinf) at ( 0, 7.5) [sect] {\begin{tabular}{c}
+ ~\\
+ \dotdebuginfo\\
+ ~
\end{tabular}};
\node(zcircs) at (-1, 5 ) [circ] {(s)};
\node(zlinkb) at ( 0, 1.5) [link] {To compilation unit~~(b)};
\draw[thick,to reversed-] (zsectinf) -- (zlinkj.west);
\draw[thick,to reversed-] (zsectinf) -- (zlinkk.north west);
-% The thrid column
+% The third column
%
\node(zsectabb) at (10, 15.00) [sect] {\dotdebugabbrev};
\node(zsectstr) at (10, 13.75) [sect] {\dotdebugstr};
\node(zlinkl) at (10, 12.50) [link] {To strings~~(l)};
\node(zsectstx) at (10, 11.25) [sect] {\dotdebugstroffsets};
\node(zlinkm) at (10, 9.50) [link] {\begin{tabular}{c}
- \DWMACROdefineindirectx \\
- \DWMACROundefindirectx \\
+ \DWMACROdefinestrx \\
+ \DWMACROundefstrx \\
(m)
\end{tabular}};
\node(zsectmac) at (10, 7.80) [sect] {\dotdebugmacro};
% The fourth column
%
\node(zlinky) at (15.6, 10.5) [link] {\begin{tabular}{c}
- \DWMACROdefineindirect \\
- \DWMACROundefindirect \\
+ \DWMACROdefinestrp \\
+ \DWMACROundefstrp \\
(p)
\end{tabular}};
\node(zlinkz) at (15.6, 6.4) [link] {\begin{tabular}{c}
- \DWMACROtransparentinclude \\
+ \DWMACROimport \\
(q)
\end{tabular}};
\node(zlinkx) at (15.6, 3.8) [link] {\DWFORMlinestrp~(r)};
%c
\itembfnl{(c) \dotdebuginfo{} to \dotdebugabbrev}
-The \texttt{debug\_abbrev\_offset} value in the header is the offset in the
+The \HFNdebugabbrevoffset{} value in the header is the offset in the
\dotdebugabbrev{}
section of the abbreviations for that compilation unit.
%m
\itembfnl{(m) \dotdebugmacro{} to \dotdebugstroffsets}
The second operand of a
-\DWMACROdefineindirectx{} or \DWMACROundefindirectx{}
+\DWMACROdefinestrx{} or \DWMACROundefstrx{}
macro information entry is an index
into the string offset table in the
\dotdebugstroffsets{} section.
%p
\itembfnl{(p) \dotdebugmacro{} to \dotdebugstr}
The second operand of a
-\DWMACROdefineindirect{} or \DWMACROundefindirect{} macro information
+\DWMACROdefinestrp{} or \DWMACROundefstrp{} macro information
entry is an index into the string table in the
\dotdebugstr{} section.
\needlines{4}
\itembfnl{(q) \dotdebugmacro{} to \dotdebugmacro}
The operand of a
-\DWMACROtransparentinclude{} macro information
+\DWMACROimport{} macro information
entry is an offset into another part of the
\dotdebugmacro{} section to the header for the
-sequence to be transparently included.
+sequence to be replicated.
%r
\needlines{4}
\node(ysectsto) at ( 5, 0.0) [sect] {\dotdebugstroffsets};
\node(ysectinf) at ( 5, 7) [sect] {\begin{tabular}{c}
+ ~\\
\dotdebuginfo \\
- skeleton
+ skeleton\\
+ ~
\end{tabular}};
\node(ysectinfdwo) at (10.5,7) [sect] {\begin{tabular}{c}
\draw[thick,-angle 90] (ysectinf) -- (ysectabb) node[midway, right] {(c)};
\draw[thick,-angle 90] (ysectinf) -- (ysectadd) node[midway, right] {(k)};
\draw[thick,-angle 90] (ysectara.east) -- (ysectinf) node[midway, left] {(a)};
-\draw[thick,-angle 90] (ysectinf) -- (ysectlin) node[midway, above] {(h)};
+\draw[thick,-angle 90] (ysectinf) -- (ysectlin.east) node[midway, above] {(h)};
\draw[thick,-angle 90] (ysectlin) -- (ysectlis) node[midway, right] {(l)};
\draw[thick,-angle 90] (ysectnam.east) -- (ysectinf) node[midway, left] {(b)};
\draw[thick,-angle 90] (ysectinf) -- (ysectran.east) node[left, near end] {(i)};
node[midway, above] {(did)};
\draw[thick,-angle 90] (ysectinfdwo) -- (ysectabbdwo) node[midway, right] {(co)};
-\draw[thick,-angle 90] (ysectinfdwo) -- (ysectlindwo) node[midway, above] {(ho)};
+\draw[thick,-angle 90] (ysectinfdwo) -- (ysectlindwo.west) node[midway, above] {(ho)};
\draw[thick,-angle 90] (ysectinfdwo) -- (ysectlocdwo.west) node[midway, below] {(jo)};
\draw[thick,-angle 90] (ysectinfdwo) -- (ysectmacdwo.west) node[near end, above] {(go)};
\draw[thick,-angle 90] (ysectinfdwo) -- (ysectstrdwo) node[midway, right] {(do)};
compilation unit and type units.
\itembfnl{(c) \dotdebuginfo{} skeleton to \dotdebugabbrev}
-The \texttt{debug\_abbrev\_offset} value in the header is
+The \HFNdebugabbrevoffset{} value in the header is
the offset in the \dotdebugabbrev{} section of the
abbreviations for that compilation unit skeleton.
\itembfnl{(co) \dotdebuginfodwo{} to \dotdebugabbrevdwo}
-The \texttt{debug\_abbrev\_offset} value in the header
+The \HFNdebugabbrevoffset{} value in the header
is the offset in the \dotdebugabbrevdwo{} section of the
abbreviations for that compilation unit.
% If draft is in the document class list, pix are just suggested
% by an outline, the pic does not appear as a picture.
%
-\newcommand{\docdate}{May 16, 2015}
+\newcommand{\docdate}{June 7, 2015}
%
\usepackage{ifthen}
\newboolean{isdraft}
\usepackage{needspace} % For assuring space remaining on a page
\usepackage{ifthen} % For conditional processing
\usepackage{changepage} % For odd/even page checks
-\usepackage{lscape}
-\usepackage{tikz} % graphics (Appendix B)
+\usepackage[usenames,dvipsnames]{xcolor}
+\usepackage{lscape} % For landscape mode (Appendix B)
+\usepackage{tikz} % graphics (Appendix B)
\usetikzlibrary{shapes.geometric}
\usetikzlibrary{arrows,decorations.pathmorphing}
\usepackage{makeidx} % For making an index
\begin{center} \textit{(empty page)} \end{center}
}
+% Define a new column type P that is just like p except
+% that it uses ragged right (rather than right justification}
+% within a column of a tabular environment. (See Goossens,
+% Mittelback&Samarin, "The LaTex Companion", pp108&114.)
+\newcommand{\PBS}[1]{\let\temp=\\#1\let\\=\temp}
+\newcolumntype{P}[1]{>{\PBS\raggedright\hspace{0pt}}p{#1}}
+
% A simple rule used in simple tables; default length is 2 inches
\newcommand{\simplerule}[1][2in]{\rule[4pt]{#1}{0.5pt}}
% Define commands for all of the DWARF names (DW\_*, .debug_*, a few others)
%
+\newcommand{\definition}[1]{\textcolor{red!80!black}{#1}}
\include{dwarfnamecmds}
%--- Begin the document pages
%
% A command to define multiple helpful DWARF name commands
+% nameLINK emits the name as hyperlink to nameTARG (or nameMARK)
+% nameTARG emit and index the name, and define this place as target for the name
+% nameINDX do not emit the name but index it anyway
+% nameMARK do not emit the name but index it and define this place as target anyway
+% nameNAME emit and index the name, but w/o hyperlink
+% nameDEFN secondary definition; like nameTARG but does not define target of hyperlink
+% name alias for nameLINK
%
\newcommand{\newdwfnamecommands}[2]{
\expandafter\def\csname #1LINK\endcsname{\index{#2}\hyperlink{chap:#1}{#2}}
- \expandafter\def\csname #1TARG\endcsname{\index{#2}\hypertarget{chap:#1}{#2}}
+ \expandafter\def\csname #1TARG\endcsname{\index{#2}\hypertarget{chap:#1}{\definition{#2}}}
\expandafter\def\csname #1INDX\endcsname{\index{#2}}
\expandafter\def\csname #1MARK\endcsname{\index{#2}\hypertarget{chap:#1}{}}
\expandafter\def\csname #1NAME\endcsname{\index{#2}{#2}}
+ \expandafter\def\csname #1DEFN\endcsname{\index{#2}{\definition{#2}}}
% The normal, most common use in running text...
\expandafter\def\csname #1\endcsname{\csname #1LINK\endcsname}
}
\newdwfnamecommands{DWMACROundef}{DW\_MACRO\_undef}
\newdwfnamecommands{DWMACROstartfile}{DW\_MACRO\_start\_file}
\newdwfnamecommands{DWMACROendfile}{DW\_MACRO\_end\_file}
-\newdwfnamecommands{DWMACROdefineindirect}{DW\_MACRO\_define\_indirect}
-\newdwfnamecommands{DWMACROundefindirect}{DW\_MACRO\_undef\_indirect}
-\newdwfnamecommands{DWMACROtransparentinclude}{DW\_MACRO\_transparent\_include}
-\newdwfnamecommands{DWMACROdefineindirectsup}{DW\_MACRO\_define\_indirect\_sup}
-\newdwfnamecommands{DWMACROundefindirectsup}{DW\_MACRO\_undef\_indirect\_sup}
-\newdwfnamecommands{DWMACROtransparentincludesup}{DW\_MACRO\_transparent\_include\_sup}
-\newdwfnamecommands{DWMACROdefineindirectx}{DW\_MACRO\_define\_indirectx}
-\newdwfnamecommands{DWMACROundefindirectx}{DW\_MACRO\_undef\_indirectx}
+\newdwfnamecommands{DWMACROdefinestrp}{DW\_MACRO\_define\_strp}
+\newdwfnamecommands{DWMACROundefstrp}{DW\_MACRO\_undef\_strp}
+\newdwfnamecommands{DWMACROimport}{DW\_MACRO\_import}
+\newdwfnamecommands{DWMACROdefinesup}{DW\_MACRO\_define\_sup}
+\newdwfnamecommands{DWMACROundefsup}{DW\_MACRO\_undef\_sup}
+\newdwfnamecommands{DWMACROimportsup}{DW\_MACRO\_import\_sup}
+\newdwfnamecommands{DWMACROdefinestrx}{DW\_MACRO\_define\_strx}
+\newdwfnamecommands{DWMACROundefstrx}{DW\_MACRO\_undef\_strx}
\newdwfnamecommands{DWMACROlouser}{DW\_MACRO\_lo\_user}
\newdwfnamecommands{DWMACROhiuser}{DW\_MACRO\_hi\_user}
%
\newcommand{\HFNdebuginfolength} {\addttindex{debug\_info\_length}}
\newcommand{\HFNdebuginfooffset} {\addttindex{debug\_info\_offset}}
\newcommand{\HFNdebuglineoffset} {\addttindex{debug\_line\_offset}}
+\newcommand{\HFNdebuglineoffsetflag} {\addttindex{debug\_line\_offset\_flag}}
\newcommand{\HFNdefaultisstmt} {\addttindex{default\_is\_stmt}}
\newcommand{\HFNdirectoryentryformatcount}{\addttindex{directory\_entry\_format\_count}}
\newcommand{\HFNdirectoryentryformat} {\addttindex{directory\_entry\_format}}
\newcommand{\HFNlinerange} {\addttindex{line\_range}}
\newcommand{\HFNminimuminstructionlength} {\addttindex{minimum\_instruction\_length}}
\newcommand{\HFNmaximumoperationsperinstruction}{\addttindex{maximum\_operations\_per\_instruction}}
+\newcommand{\HFNoffsetsizeflag} {\addttindex{offset\_size\_flag}}
\newcommand{\HFNopcodebase} {\addttindex{opcode\_base}}
\newcommand{\HFNopcodeoperandstable} {\addttindex{opcode\_operands\_table}}
+\newcommand{\HFNopcodeoperandstableflag} {\addttindex{opcode\_operands\_table\_flag}}
\newcommand{\HFNsegmentselectorsize} {\addttindex{segment\_selector\_size}}
\newcommand{\HFNstandardopcodelengths} {\addttindex{standard\_opcode\_lengths}}
\newcommand{\HFNtypeoffset} {\addttindex{type\_offset}}
\newcommand{\autoreturntype}{\texttt{auto} return type\index{auto return type@\texttt{auto} return type}}
\newcommand{\specialaddresstype}{\livelink{chap:specialaddresstype}{special address type}}
\newcommand{\splitDWARFobjectfile}{\addtoindex{split DWARF object file}}
+\newcommand{\compunitset}{\addtoindex{compilation unit set}}
+\newcommand{\typeunitset}{\addtoindex{type unit set}}
+\newcommand{\byteorder}{\addtoindex{byte order}}
+\newcommand{\associatedcompilationunit}{\addtoindex{associated compilation unit}}
%
% Anti-ligature commands added because \/ and {} don't work for unknown reasons
% nor does the microtext package DisableLigatures command...???
\begin{figure}[here]
\begin{lstlisting}
-type array_ptr
-real :: myvar
-real, dimension (:), pointer :: ap
-end type array_ptr
-type(array_ptr), allocatable, dimension(:) :: arrayvar
-allocate(arrayvar(20))
-do i = 1, 20
-allocate(arrayvar(i)%ap(i+10))
-end do
+ type array_ptr
+ real :: myvar
+ real, dimension (:), pointer :: ap
+ end type array_ptr
+ type(array_ptr), allocatable, dimension(:) :: arrayvar
+ allocate(arrayvar(20))
+ do i = 1, 20
+ allocate(arrayvar(i)%ap(i+10))
+ end do
\end{lstlisting}
-\caption{Fortran array example: source fragment} \label{fig:fortranarrayexamplesourcefragment}
+\caption{Fortran array example: source fragment}
+\label{fig:fortranarrayexamplesourcefragment}
\end{figure}
For allocatable and pointer arrays, it is essentially required
\needlines{5}
This section illustrates one possible representation of the
following \addtoindex{C} structure definition in both big-
-and little-endian byte orders:
+and little-endian \byteorder{s}:
\begin{lstlisting}
struct S {
\end{dwflisting}
\caption{Call Site Example \#2: DWARF Encoding}
\label{fig:callsiteexample2dwarf}
+\end{figure}
+
+
+\clearpage
+\section{Macro Example}
+\label{macroexample}
+Consider the \addtoindex{C} source in Figure
+\referfol{ref:macroexamplesource} which is used to illustrate the
+DWARF encoding of macro information (see Section \refersec{chap:macroinformation}).
+
+\begin{figure}[h]
+\textit{File a.c}
+\begin{lstlisting}
+#include "a.h"
+#define FUNCTION_LIKE_MACRO(x) 4+x
+#include "b.h"
+\end{lstlisting}
+\vspace{7mm}
+\textit{File a.h}
+\begin{lstlisting}
+#define LONGER_MACRO 1
+#define B 2
+#include "b.h"
+#define B 3
+\end{lstlisting}
+\vspace{7mm}
+\textit{File b.h}
+\begin{lstlisting}
+#undef B
+#define D 3
+#define FUNCTION_LIKE_MACRO(x) 4+x
+\end{lstlisting}
+\caption{Macro example: Source}
+\label{ref:macroexamplesource}
+\end{figure}
+
+Two possible encodings are shown. The first, in
+Figure \refersec{fig:macroexamplesimpledwarfencoding}, is perhaps the simplest
+possible encoding. It includes all macro information from the
+main source file (\texttt{a.c}) as well as its two included files
+(\texttt{a.h} and \texttt{b.h}) in a single macro unit. Further,
+all strings are included as immediate operands of the macro
+operators (that is, there is no string pooling). The size
+of the macro unit is 160 bytes.
+
+The second encoding, in
+Figure \refersec{fig:macroexampledsharablewarfencoding},
+saves space in two ways:
+\begin{enumerate}[1. ]
+\item Longer strings are pooled by storing them in the
+\dotdebugstr{} section where they can be referenced more than
+once.
+
+\item Macro information entries contained in included files
+are represented as separate macro units which are then
+imported for each \texttt{\#include} directive.
+
+\end{enumerate}
+The combined size of the three macro units and their referenced
+strings is 129 bytes.
+
+\needlines{4}
+A number of observations are worth mentioning:
+\begin{itemize}
+\item
+Strings that are the same size as a reference or less are
+better represented as immediate operands. Strings longer
+than twice the size of a reference are better stored in the
+string table if there are at least two references.
+
+\item
+There is a trade-off between the size of the macro information
+of a file and the number of times it is included when evaluating
+whether to create a separate macro unit. However, the amount
+of overhead (the size of a macro header) needed to represent a
+unit as well as the size of the operation to import a macro unit
+are both small.
+
+\item
+A macro unit need not describe all of the macro information in
+a file. For example, in Figure \ref{fig:macroexampledsharablewarfencoding}
+the second macro unit (beginning at \texttt{i\$1h}) includes macros
+from just the first two lines of file \texttt{a.h}.
+
+\item
+An implementation may be able to share macro units across object
+files (not shown in this example). To support this, it may be
+advantageous to create macro units in cases where they do not
+offer an advantage in a single compilation of itself.
+
+\needlines{6}
+\item
+The header of a macro unit that contains a \DWMACROstartfile{}
+operation must include a reference to the compilation line number
+header to allow interpretation of the file number operands in
+those commands. However, the presence of those offsets complicates
+or may preclude sharing across compilations.
+
+\end{itemize}
+
+
+\begin{figure}
+\begin{dwflisting}
+\begin{alltt}
+
+! *** Section \dotdebugmacro{} contents
+! Macro unit for "a.c"
+0$h: Version: 5
+ Flags: 2
+ \HFNoffsetsizeflag: 0 ! 4-byte offsets
+ \HFNdebuglineoffsetflag: 1 ! Line number offset present
+ \HFNopcodeoperandstableflag: 0 ! No extensions
+ Offset in \dotdebugline{} section: 0 ! Line number offset
+0$m: \DWMACROstartfile, 0, 0 ! Implicit Line: 0, File: 0 "a.c"
+ \DWMACROstartfile, 1, 1 ! #include Line: 1, File: 1 "a.h"
+ \DWMACROdefine, 1, "LONGER\_MACRO 1"
+ ! #define Line: 1, String: "LONGER\_MACRO 1"
+ \DWMACROdefine, 2, "B 2" ! #define Line: 2, String: "B 2"
+ \DWMACROstartfile, 3, 2 ! #include Line: 3, File: 2 "b.h"
+ \DWMACROundef, 1, "B" ! #undef Line: 1, String: "b"
+ \DWMACROdefine 2, "D 3" ! #define Line: 2, String: "D 3"
+ \DWMACROdefine, 3, "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ ! #define Line: 3,
+ ! String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ \DWMACROendfile{} ! End "b.h" -> back to "a.h"
+ \DWMACROdefine, 4, "B 3" ! #define Line: 4, String: "B 3"
+ \DWMACROendfile{} ! End "a.h" -> back to "a.c"
+ \DWMACROdefine, 2, "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ ! #define Line: 2,
+ ! String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ \DWMACROstartfile, 3, 2 ! #include Line: 3, File: 2 "b.h"
+ \DWMACROundef, 1, "B" ! #undef Line: 1, String: "b"
+ \DWMACROdefine, 2, "D 3" ! #define Line: 2, String: "D 3"
+ \DWMACROdefine, 3, "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ ! #define Line: 3,
+ ! String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ \DWMACROendfile{} ! End "b.h" -> back to "a.c"
+ \DWMACROendfile{} ! End "a.c" -> back to ""
+ 0 ! End macro unit
+\end{alltt}
+\end{dwflisting}
+\caption{Macro Example: Simple DWARF Encoding}
+\label{fig:macroexamplesimpledwarfencoding}
+\end{figure}
+
+
+\begin{figure}
+\begin{dwflisting}
+\begin{alltt}
+! *** Section \dotdebugmacro{} contents
+! Macro unit for "a.c"
+0$h: Version: 5
+ Flags: 2
+ \HFNoffsetsizeflag: 0 ! 4-byte offsets
+ \HFNdebuglineoffsetflag: 1 ! Line number offset present
+ \HFNopcodeoperandstableflag: 0 ! No extensions
+ Offset in \dotdebugline{} section: 0 ! Line number offset
+0$m: \DWMACROstartfile, 0, 0 ! Implicit Line: 0, File: 0 "a.c"
+ \DWMACROstartfile, 1, 1 ! #include Line: 1, File: 1 "a.h"
+ \DWMACROimport, i$1h ! Import unit at i$1h (lines 1-2)
+ \DWMACROstartfile, 3, 2 ! #include Line: 3, File: 2 "b.h"
+ \DWMACROimport, i$2h ! Import unit i$2h (lines all)
+ \DWMACROendfile{} ! End "b.h" -> back to "a.h"
+ \DWMACROdefine, 4, "B 3" ! #define Line: 4, String: "B 3"
+ \DWMACROendfile{} ! End "a.h" -> back to "a.c"
+ \DWMACROdefine, 2, s$1 ! #define Line: 3,
+ ! String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ \DWMACROstartfile, 3, 2 ! #include Line: 3, File: 2 "b.h"
+ \DWMACROimport, i$2h ! Import unit i$2h (lines all)
+ \DWMACROendfile{} ! End "b.h" -> back to "a.c"
+ \DWMACROendfile{} ! End "a.c" -> back to ""
+ 0 ! End macro unit
+! Macro unit for "a.h" lines 1-2
+i$1h: Version: 5
+ Flags: 0
+ \HFNoffsetsizeflag: 0 ! 4-byte offsets
+ \HFNdebuglineoffsetflag: 0 ! No line number offset
+ \HFNopcodeoperandstableflag: 0 ! No extensions
+i$1m: \DWMACROdefinestrp, 1, s$2 ! #define Line: 1, String: "LONGER\_MACRO 1"
+ \DWMACROdefine, 2, "B 2" ! #define Line: 2, String: "B 2"
+ 0 ! End macro unit
+! Macro unit for "b.h"
+i$2h: Version: 5
+ Flags: 0
+ \HFNoffsetsizeflag: 0 ! 4-byte offsets
+ \HFNdebuglineoffsetflag: 0 ! No line number offset
+ \HFNopcodeoperandstableflag: 0 ! No extensions
+i$2m: \DWMACROundef, 1, "B" ! #undef Line: 1, String: "B"
+ \DWMACROdefine, 2, "D 3" ! #define Line: 2, String: "D 3"
+ \DWMACROdefinestrp, 3, s$1 ! #define Line: 3,
+ ! String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+ 0 ! End macro unit
+! *** Section \dotdebugstr{} contents
+s$1: String: "FUNCTION\_LIKE\_MACRO(x) 4+x"
+s$2: String: "LONGER\_MACRO 1"
+\end{alltt}
+\end{dwflisting}
+\caption{Macro Example: Sharable DWARF Encoding}
+\label{fig:macroexampledsharablewarfencoding}
\end{figure}
\ No newline at end of file
The debugging information entries they identify are
described in Chapters 3, 4 and 5.
-% These each need to link to definition page: FIXME
-
\begin{table}[p]
\caption{Tag names}
\label{tab:tagnames}
among others.}
The debugging information entries are contained in the
-\dotdebuginfo{} sections of an object file.
+\dotdebuginfo{} and/or \dotdebuginfodwo{} sections of an object file.
\needlines{7}
Optionally, debugging information may be partitioned such
The executable or shared object file which contains references to
those debugging information entries contain a \dotdebugsup{} section
with information that identifies the \addtoindex{supplementary object file};
-the supplementary object file contains a variant of this same section
+the \addtoindex{supplementary object file} contains a variant of this same section
that is used to unambiguously associate it with the referencing object.
See Section \refersec{datarep:dwarfsupplemetaryobjectfiles} for
further details.
\setlength{\extrarowheight}{0.1cm}
\addtoindexx{attributes!list of}
-\begin{longtable}{l|p{9cm}}
+\begin{longtable}{l|P{9cm}}
\caption{Attribute names} \label{tab:attributenames} \\
\hline \bfseries Attribute&\bfseries Identifies or Specifies \\ \hline
\endfirsthead
{Subroutine or subroutine type}
{subroutine or subroutine type} \\
\DWATaddrbaseTARG
-&\livelinki{chap:DWATaddrbaseforaddresstable}{Base offset for address table}{address table} \\
+&\livelinki{chap:DWATaddrbaseforaddresstable}
+ {Base offset for address table}
+ {address table} \\
\DWATalignmentTARG
&\livelinki{chap:DWATalignmentnondefault}
{Non-default alignment of type, subprogram or variable}
%&\livelinki{chap:DWATbitoffsetbasetypebitlocation}{Base type bit location}{base type bit location} \\
%&\livelinki{chap:DWATbitoffsetdatamemberbitlocation}{Data member bit location}{data member bit location} \\
\DWATbitsizeTARG{}
-&\livelinki{chap:DWATbitsizebasetypebitsize}{Size of a base in bits}{base type bit size} \\
-&\livelinki{chap:DWATbitsizedatamemberbitsize}{Size of a data member in bits}{data member bit size} \\
+&\livelinki{chap:DWATbitsizebasetypebitsize}
+ {Size of a base type in bits}
+ {base type bit size} \\
+&\livelinki{chap:DWATbitsizedatamemberbitsize}
+ {Size of a data member in bits}
+ {data member bit size} \\
\DWATbitstrideTARG{}
&\livelinki{chap:DWATbitstridearrayelementstrideofarraytype}
{Array element stride (of array type)}
{argument value passed}
\index{call site!argument value passed} \\
\DWATcommonreferenceTARG
-&\livelinki{chap:commonreferencecommonblockusage}{Common block usage}{common block usage} \\
+&\livelinki{chap:commonreferencecommonblockusage}
+ {Common block usage}
+ {common block usage} \\
\DWATcompdirTARG
-&\livelinki{chap:DWATcompdircompilationdirectory}{Compilation directory}{compilation directory} \\
-\DWATconstvalueTARG
-&\livelinki{chap:DWATconstvalueconstantobject}{Constant object}{constant object} \\
-&\livelinki{chap:DWATconstvalueenumerationliteralvalue}{Enumeration literal value}{enumeration literal value} \\
-&\livelinki{chap:DWATconstvaluetemplatevalueparameter}{Template value parameter}{template value parameter} \\
+&\livelinki{chap:DWATcompdircompilationdirectory}
+ {Compilation directory}
+ {compilation directory} \\
\DWATconstexprTARG
&\livelinki{chap:DWATconstexprcompiletimeconstantobject}
{Compile-time constant object}
&\livelinki{chap:DWATconstexprcompiletimeconstantfunction}
{Compile-time constant function}
{compile-time constant function} \\
+\DWATconstvalueTARG
+&\livelinki{chap:DWATconstvalueconstantobject}
+ {Constant object}
+ {constant object} \\
+&\livelinki{chap:DWATconstvalueenumerationliteralvalue}
+ {Enumeration literal value}
+ {enumeration literal value} \\
+&\livelinki{chap:DWATconstvaluetemplatevalueparameter}
+ {Template value parameter}
+ {template value parameter} \\
\DWATcontainingtypeTARG
&\livelinki{chap:DWATcontainingtypecontainingtypeofpointertomembertype}
{Containing type of pointer to member type}
{containing type of pointer to member type} \\
\DWATcountTARG
-&\livelinki{chap:DWATcountelementsofsubrangetype}{Elements of subrange type}{elements of breg subrange type} \\
+&\livelinki{chap:DWATcountelementsofsubrangetype}
+ {Elements of subrange type}
+ {elements of breg subrange type} \\
\DWATdatabitoffsetTARG
-&\livelinki{chap:DWATdatabitoffsetbasetypebitlocation}{Base type bit location}{base type bit location} \\
-&\livelinki{chap:DWATdatabitoffsetdatamemberbitlocation}{Data member bit location}{data member bit location} \\
+&\livelinki{chap:DWATdatabitoffsetbasetypebitlocation}
+ {Base type bit location}
+ {base type bit location} \\
+&\livelinki{chap:DWATdatabitoffsetdatamemberbitlocation}
+ {Data member bit location}
+ {data member bit location} \\
\DWATdatalocationTARG{}
-&\livelinki{chap:DWATdatalocationindirectiontoactualdata}{Indirection to actual data}{indirection to actual data} \\
+&\livelinki{chap:DWATdatalocationindirectiontoactualdata}
+ {Indirection to actual data}
+ {indirection to actual data} \\
\DWATdatamemberlocationTARG
-&\livelinki{chap:DWATdatamemberlocationdatamemberlocation}{Data member location}{data member location} \\
-&\livelinki{chap:DWATdatamemberlocationinheritedmemberlocation}{Inherited member location}{inherited member location} \\
+&\livelinki{chap:DWATdatamemberlocationdatamemberlocation}
+ {Data member location}
+ {data member location} \\
+&\livelinki{chap:DWATdatamemberlocationinheritedmemberlocation}
+ {Inherited member location}
+ {inherited member location} \\
\DWATdecimalscaleTARG
-&\livelinki{chap:DWATdecimalscaledecimalscalefactor}{Decimal scale factor}{decimal scale factor} \\
+&\livelinki{chap:DWATdecimalscaledecimalscalefactor}
+ {Decimal scale factor}
+ {decimal scale factor} \\
\DWATdecimalsignTARG
-&\livelinki{chap:DWATdecimalsigndecimalsignrepresentation}{Decimal sign representation}{decimal sign representation} \\
+&\livelinki{chap:DWATdecimalsigndecimalsignrepresentation}
+ {Decimal sign representation}
+ {decimal sign representation} \\
\DWATdeclcolumnTARG
&\livelinki{chap:DWATdeclcolumncolumnpositionofsourcedeclaration}
{Column position of source declaration}
{Incomplete, non-defining, or separate entity declaration}
{incomplete, non-defining, or separate entity declaration} \\
\DWATdefaultedTARG
-&\livelinki{chap:DWATdefaulteddef}{Whether a member function has been declared as default}{defaulted attribute} \\
+&\livelinki{chap:DWATdefaulteddef}
+ {Whether a member function has been declared as default}
+ {defaulted attribute} \\
\DWATdefaultvalueTARG
-&\livelinki{chap:DWATdefaultvaluedefaultvalueofparameter}{Default value of parameter}{default value of parameter} \\
+&\livelinki{chap:DWATdefaultvaluedefaultvalueofparameter}
+ {Default value of parameter}
+ {default value of parameter} \\
\DWATdeletedTARG
-&\livelinki{chap:DWATdeleteddef}{Whether a member has been declared as deleted}{Deletion of member function} \\
+&\livelinki{chap:DWATdeleteddef}
+ {Whether a member has been declared as deleted}
+ {Deletion of member function} \\
\DWATdescriptionTARG{}
&\livelinki{chap:DWATdescriptionartificialnameordescription}
{Artificial name or description}
{Digit count for packed decimal or numeric string type}
{digit count for packed decimal or numeric string type} \\
\DWATdiscrTARG
-&\livelinki{chap:DWATdiscrdiscriminantofvariantpart}{Discriminant of variant part}{discriminant of variant part} \\
+&\livelinki{chap:DWATdiscrdiscriminantofvariantpart}
+ {Discriminant of variant part}
+ {discriminant of variant part} \\
\DWATdiscrlistTARG
-&\livelinki{chap:DWATdiscrlistlistofdiscriminantvalues}{List of discriminant values}{list of discriminant values} \\
+&\livelinki{chap:DWATdiscrlistlistofdiscriminantvalues}
+ {List of discriminant values}
+ {list of discriminant values} \\
\DWATdiscrvalueTARG
-&\livelinki{chap:DWATdiscrvaluediscriminantvalue}{Discriminant value}{discriminant value} \\
+&\livelinki{chap:DWATdiscrvaluediscriminantvalue}
+ {Discriminant value}
+ {discriminant value} \\
\DWATdwoidTARG
-&\livelinki{chap:DWATdwoidforunit}{Signature for compilation unit}{split DWARF object file!unit signature} \\
+&\livelinki{chap:DWATdwoidforunit}
+ {Signature for compilation unit}
+ {split DWARF object file!unit signature} \\
\DWATdwonameTARG
-&\livelinki{chap:DWATdwonameforunit}{Name of split DWARF object file}{split DWARF object file!object file name} \\
+&\livelinki{chap:DWATdwonameforunit}
+ {Name of split DWARF object file}
+ {split DWARF object file!object file name} \\
\DWATelementalTARG
&\livelinki{chap:DWATelementalelementalpropertyofasubroutine}
{Elemental property of a subroutine}
{elemental property of a subroutine} \\
\DWATencodingTARG
-&\livelinki{chap:DWATencodingencodingofbasetype}{Encoding of base type}{encoding of base type} \\
+&\livelinki{chap:DWATencodingencodingofbasetype}
+ {Encoding of base type}
+ {encoding of base type} \\
\DWATendianityTARG
-&\livelinki{chap:DWATendianityendianityofdata}{Endianity of data}{endianity of data} \\
+&\livelinki{chap:DWATendianityendianityofdata}
+ {Endianity of data}
+ {endianity of data} \\
\DWATentrypcTARG
-&\livelinki{chap:entryaddressofscope}{Entry address of a scope (compilation unit, \mbox{subprogram,} and so on)}{} \\
+&\livelinki{chap:entryaddressofscope}
+ {Entry address of a scope (compilation unit, \mbox{subprogram,} and so on)}
+ {entry address of a scope} \\
\DWATenumclassTARG
&\livelinki{chap:DWATenumclasstypesafeenumerationdefinition}
{Type safe enumeration definition}
{Previous namespace extension or original namespace}
{previous namespace extension or original namespace}\\
\DWATexternalTARG
-&\livelinki{chap:DWATexternalexternalsubroutine}{External subroutine}{external subroutine} \\
-&\livelinki{chap:DWATexternalexternalvariable}{External variable}{external variable} \\
+&\livelinki{chap:DWATexternalexternalsubroutine}
+ {External subroutine}
+ {external subroutine} \\
+&\livelinki{chap:DWATexternalexternalvariable}
+ {External variable}
+ {external variable} \\
\DWATframebaseTARG
-&\livelinki{chap:DWATframebasesubroutineframebaseaddress}{Subroutine frame base address}{subroutine frame base address} \\
+&\livelinki{chap:DWATframebasesubroutineframebaseaddress}
+ {Subroutine frame base address}
+ {subroutine frame base address} \\
\DWATfriendTARG
-&\livelinki{chap:DWATfriendfriendrelationship}{Friend relationship}{friend relationship} \\
+&\livelinki{chap:DWATfriendfriendrelationship}
+ {Friend relationship}
+ {friend relationship} \\
\DWAThighpcTARG
&\livelinki{chap:DWAThighpccontiguousrangeofcodeaddresses}
{Contiguous range of code addresses}
{contiguous range of code addresses} \\
\DWATidentifiercaseTARG
-&\livelinki{chap:DWATidentifiercaseidentifiercaserule}{Identifier case rule}{identifier case rule} \\
+&\livelinki{chap:DWATidentifiercaseidentifiercaserule}
+ {Identifier case rule}
+ {identifier case rule} \\
\DWATimportTARG
-&\livelinki{chap:DWATimportimporteddeclaration}{Imported declaration}{imported declaration} \\
-&\livelinki{chap:DWATimportimportedunit}{Imported unit}{imported unit} \\
-&\livelinki{chap:DWATimportnamespacealias}{Namespace alias}{namespace alias} \\
-&\livelinki{chap:DWATimportnamespaceusingdeclaration}{Namespace using declaration}{namespace using declaration} \\
-&\livelinki{chap:DWATimportnamespaceusingdirective}{Namespace using directive}{namespace using directive} \\
+&\livelinki{chap:DWATimportimporteddeclaration}
+ {Imported declaration}
+ {imported declaration} \\
+&\livelinki{chap:DWATimportimportedunit}
+ {Imported unit}
+ {imported unit} \\
+&\livelinki{chap:DWATimportnamespacealias}
+ {Namespace alias}
+ {namespace alias} \\
+&\livelinki{chap:DWATimportnamespaceusingdeclaration}
+ {Namespace using declaration}
+ {namespace using declaration} \\
+&\livelinki{chap:DWATimportnamespaceusingdirective}
+ {Namespace using directive}
+ {namespace using directive} \\
\DWATinlineTARG
-&\livelinki{chap:DWATinlineabstracttinstance}{Abstract instance}{abstract instance} \\
-&\livelinki{chap:DWATinlineinlinedsubroutine}{Inlined subroutine}{inlined subroutine} \\
+&\livelinki{chap:DWATinlineabstracttinstance}
+ {Abstract instance}
+ {abstract instance} \\
+&\livelinki{chap:DWATinlineinlinedsubroutine}
+ {Inlined subroutine}
+ {inlined subroutine} \\
\DWATisoptionalTARG
-&\livelinki{chap:DWATisoptionaloptionalparameter}{Optional parameter}{optional parameter} \\
+&\livelinki{chap:DWATisoptionaloptionalparameter}
+ {Optional parameter}
+ {optional parameter} \\
\DWATlanguageTARG
-&\livelinki{chap:DWATlanguageprogramminglanguage}{Programming language}{programming language} \\
+&\livelinki{chap:DWATlanguageprogramminglanguage}
+ {Programming language}
+ {programming language} \\
\DWATlinkagenameTARG
&\livelinki{chap:DWATlinkagenameobjectfilelinkagenameofanentity}
{Object file linkage name of an entity}
{object file linkage name of an entity}\\
\DWATlocationTARG
-&\livelinki{chap:DWATlocationdataobjectlocation}{Data object location}{data object location}\\
+&\livelinki{chap:DWATlocationdataobjectlocation}
+ {Data object location}
+ {data object location}\\
\DWATlowpcTARG
&\livelinki{chap:DWATlowpccodeaddressorrangeofaddresses}
{Code address or range of addresses}
{code address or range of addresses}\\
\DWATlowerboundTARG
-&\livelinki{chap:DWATlowerboundlowerboundofsubrange}{Lower bound of subrange}{lower bound of subrange} \\
+&\livelinki{chap:DWATlowerboundlowerboundofsubrange}
+ {Lower bound of subrange}
+ {lower bound of subrange} \\
\DWATmacroinfoTARG
&\livelinki{chap:DWATmacroinfomacroinformation}
{Macro preprocessor information (legacy)}
& \textit{(\texttt{\#define}, \texttt{\#undef}, and so on in \addtoindex{C},
\addtoindex{C++} and similar languages)} \\
\DWATmainsubprogramTARG
-&\livelinki{chap:DWATmainsubprogrammainorstartingsubprogram}{Main or starting subprogram}{main or starting subprogram} \\
+&\livelinki{chap:DWATmainsubprogrammainorstartingsubprogram}
+ {Main or starting subprogram}
+ {main or starting subprogram} \\
&\livelinki{chap:DWATmainsubprogramunitcontainingmainorstartingsubprogram}
{Unit containing main or starting subprogram}
{unit containing main or starting subprogram}\\
{Mutable property of member data}
{mutable property of member data} \\
\DWATnameTARG
-&\livelinki{chap:DWATnamenameofdeclaration}{Name of declaration}{name of declaration}\\
-&\livelinki{chap:DWATnamepathnameofcompilationsource}{Path name of compilation source}{path name of compilation source} \\
+&\livelinki{chap:DWATnamenameofdeclaration}
+ {Name of declaration}
+ {name of declaration}\\
+&\livelinki{chap:DWATnamepathnameofcompilationsource}
+ {Path name of compilation source}
+ {path name of compilation source} \\
\DWATnamelistitemTARG
-&\livelinki{chap:DWATnamelistitemnamelistitem}{Namelist item}{namelist item}\\
+&\livelinki{chap:DWATnamelistitemnamelistitem}
+ {Namelist item}
+ {namelist item}\\
\DWATnoreturnTARG
-&\livelinki{chap:DWATnoreturnofsubprogram}{\doublequote{no return} property of a subprogram}{noreturn attribute} \\
+&\livelinki{chap:DWATnoreturnofsubprogram}
+ {\doublequote{no return} property of a subprogram}
+ {noreturn attribute} \\
\DWATobjectpointerTARG
&\livelinki{chap:DWATobjectpointerobjectthisselfpointerofmemberfunction}
{Object (\texttt{this}, \texttt{self}) pointer of member function}
{object (\texttt{this}, \texttt{self}) pointer of member function}\\
\DWATorderingTARG
-&\livelinki{chap:DWATorderingarrayrowcolumnordering}{Array row/column ordering} {array row/column ordering}\\
+&\livelinki{chap:DWATorderingarrayrowcolumnordering}
+ {Array row/column ordering}
+ {array row/column ordering}\\
\DWATpicturestringTARG
&\livelinki{chap:DWATpicturestringpicturestringfornumericstringtype}
{Picture string for numeric string type}
{picture string for numeric string type} \\
\DWATpriorityTARG
-&\livelinki{chap:DWATprioritymodulepriority}{Module priority}{module priority}\\
+&\livelinki{chap:DWATprioritymodulepriority}
+ {Module priority}
+ {module priority}\\
\DWATproducerTARG
-&\livelinki{chap:DWATproducercompileridentification}{Compiler identification}{compiler identification}\\
+&\livelinki{chap:DWATproducercompileridentification}
+ {Compiler identification}
+ {compiler identification}\\
\DWATprototypedTARG
-&\livelinki{chap:DWATprototypedsubroutineprototype}{Subroutine prototype}{subroutine prototype}\\
+&\livelinki{chap:DWATprototypedsubroutineprototype}
+ {Subroutine prototype}
+ {subroutine prototype}\\
\DWATpureTARG
-&\livelinki{chap:DWATpurepurepropertyofasubroutine}{Pure property of a subroutine}{pure property of a subroutine} \\
+&\livelinki{chap:DWATpurepurepropertyofasubroutine}
+ {Pure property of a subroutine}
+ {pure property of a subroutine} \\
\DWATrangesTARG
&\livelinki{chap:DWATrangesnoncontiguousrangeofcodeaddresses}
{Non-contiguous range of code addresses}
{non-contiguous range of code addresses} \\
\DWATrangesbaseTARG
-&\livelinki{chap:DWATrangesbaseforrangelists}{Base offset for range lists}{ranges lists} \\
+&\livelinki{chap:DWATrangesbaseforrangelists}
+ {Base offset for range lists}
+ {ranges lists} \\
\DWATrankTARG
-&\livelinki{chap:DWATrankofdynamicarray}{Dynamic number of array dimensions}{dynamic number of array dimensions} \\
+&\livelinki{chap:DWATrankofdynamicarray}
+ {Dynamic number of array dimensions}
+ {dynamic number of array dimensions} \\
\DWATrecursiveTARG
&\livelinki{chap:DWATrecursiverecursivepropertyofasubroutine}
{Recursive property of a subroutine}
{\&\&-qualified non-static member function} \textit{(\addtoindex{C++})} \\
\DWATsegmentTARG
-&\livelinki{chap:DWATsegmentaddressinginformation}{Addressing information}{addressing information} \\
+&\livelinki{chap:DWATsegmentaddressinginformation}
+ {Addressing information}
+ {addressing information} \\
\DWATsiblingTARG
&\livelinki{chap:DWATsiblingdebugginginformationentryrelationship}
{Debugging information entry relationship}
{Incomplete, non-defining, or separate declaration corresponding to a declaration}
{incomplete, non-defining, or separate declaration corresponding to a declaration} \\
\DWATstartscopeTARG
-&\livelinki{chap:DWATstartscopeobjectdeclaration}{Object declaration}{object declaration}\\*
-&\livelinki{chap:DWATstartscopetypedeclaration}{Type declaration}{type declaration}\\
+&\livelinki{chap:DWATstartscopeobjectdeclaration}
+ {Object declaration}
+ {object declaration}\\*
+&\livelinki{chap:DWATstartscopetypedeclaration}
+ {Type declaration}
+ {type declaration}\\
\DWATstaticlinkTARG
-&\livelinki{chap:DWATstaticlinklocationofuplevelframe}{Location of uplevel frame}{location of uplevel frame} \\
+&\livelinki{chap:DWATstaticlinklocationofuplevelframe}
+ {Location of uplevel frame}
+ {location of uplevel frame} \\
\DWATstmtlistTARG
&\livelinki{chap:DWATstmtlistlinenumberinformationforunit}
{Line number information for unit}
{Size of string length of string type}
{string length of string type!size of} \\
\DWATstroffsetsbaseTARG
-&\livelinki{chap:DWATstroffsetbaseforindirectstringtable}{Base of string offsets table}{string offsets table} \\
+&\livelinki{chap:DWATstroffsetbaseforindirectstringtable}
+ {Base of string offsets table}
+ {string offsets table} \\
\DWATthreadsscaledTARG
-&\livelink{chap:DWATthreadsscaledupcarrayboundthreadsscalfactor}{UPC array bound THREADS scale factor}\\
+&\livelink{chap:DWATthreadsscaledupcarrayboundthreadsscalfactor}
+ {UPC array bound THREADS scale factor}\\
\DWATtrampolineTARG
-&\livelinki{chap:DWATtrampolinetargetsubroutine}{Target subroutine}{target subroutine of trampoline} \\
+&\livelinki{chap:DWATtrampolinetargetsubroutine}
+ {Target subroutine}
+ {target subroutine of trampoline} \\
\DWATtypeTARG
-&\livelinki{chap:DWATtypeofcallsite}{Type of call site}{type!of call site} \\
-&\livelinki{char:DWAATtypeofstringtype}{Type of string type components}{type!of string type components} \\
-&\livelinki{chap:DWATtypetypeofsubroutinereturn}{Type of subroutine return}{type!of subroutine return} \\
-&\livelinki{chap:DWATtypetypeofdeclaration}{Type of declaration}{type!of declaration} \\
+&\livelinki{chap:DWATtypeofcallsite}
+ {Type of call site}
+ {type!of call site} \\
+&\livelinki{char:DWAATtypeofstringtype}
+ {Type of string type components}
+ {type!of string type components} \\
+&\livelinki{chap:DWATtypetypeofsubroutinereturn}
+ {Type of subroutine return}
+ {type!of subroutine return} \\
+&\livelinki{chap:DWATtypetypeofdeclaration}
+ {Type of declaration}
+ {type!of declaration} \\
\DWATupperboundTARG
-&\livelinki{chap:DWATupperboundupperboundofsubrange}{Upper bound of subrange}{upper bound of subrange} \\
+&\livelinki{chap:DWATupperboundupperboundofsubrange}
+ {Upper bound of subrange}
+ {upper bound of subrange} \\
\DWATuselocationTARG
&\livelinki{chap:DWATuselocationmemberlocationforpointertomembertype}
{Member location for pointer to member type}
{Non-constant parameter flag}
{non-constant parameter flag} \\
\DWATvirtualityTARG
-&\livelinki{chap:DWATvirtualityvirtualityindication}{Virtuality indication}{virtuality indication} \\
-&\livelinki{chap:DWATvirtualityvirtualityofbaseclass}{Virtuality of base class} {virtuality of base class} \\
-&\livelinki{chap:DWATvirtualityvirtualityoffunction}{Virtuality of function}{virtuality of function} \\
+&\livelinki{chap:DWATvirtualityvirtualityindication}
+ {Virtuality indication}
+ {virtuality indication} \\
+&\livelinki{chap:DWATvirtualityvirtualityofbaseclass}
+ {Virtuality of base class}
+ {virtuality of base class} \\
+&\livelinki{chap:DWATvirtualityvirtualityoffunction}
+ {Virtuality of function}
+ {virtuality of function} \\
\DWATvisibilityTARG
-&\livelinki{chap:DWATvisibilityvisibilityofdeclaration}{Visibility of declaration}{visibility of declaration} \\
+&\livelinki{chap:DWATvisibilityvisibilityofdeclaration}
+ {Visibility of declaration}
+ {visibility of declaration} \\
\DWATvtableelemlocationTARG
&\livelinki{chap:DWATvtableelemlocationvirtualfunctiontablevtableslot}
{Virtual function vtable slot}
\addtoindexx{tag names!list of}
to one of the classes shown in Table \referfol{tab:classesofattributevalue}.
-\begin{longtable}{l|p{11cm}}
+\begin{longtable}{l|P{11cm}}
\caption{Classes of attribute value}
\label{tab:classesofattributevalue} \\
\hline \bfseries Attribute Class & \bfseries General Use and Encoding \\ \hline
\livelinki{datarep:classstroffsetsptr}{stroffsetsptr}{stroffsetsptr class}
&Refers to a base location in the DWARF section that holds
a series of offsets in the DWARF section that holds strings.
-Certain attributes refer one of these offsets by indexing
+Certain attributes refer to one of these offsets by indexing
\mbox{relative} to this base location. The resulting offset is then
used to index into the DWARF string section.
\\
\hypertarget{chap:DWATsiblingdebugginginformationentryrelationship}{}
it will be important for consumers of that information to
quickly scan chains of sibling entries, while ignoring the
-children of individual siblings, that producer may attach
+children of individual siblings, that producer may attach a
\addtoindexx{sibling attribute}
-a
-\DWATsibling{} attribute
+\DWATsiblingDEFN{} attribute
to any debugging information entry.
-The
-value of this attribute is a reference to the sibling entry
+The value of this attribute is a reference to the sibling entry
of the entry to which the attribute is attached.
-\section{Target Addresses}
+\section{Target Addressable Units and Addresses}
+\label{chap:targetaddressableunitsandaddresses}
+The standard assumes that the smallest directly
+\addtoindex{addressable unit} of memory on the
+target architecture is a byte consisting of eight bits.
+
\label{chap:targetaddresses}
Many places in this document refer to the size of an
\addtoindexx{size of an address|see{\textit{also} \texttt{address\_size}}}
\textit{%
Architectures which have multiple instruction sets are
-supported by the isa entry in the line number information
+supported by the \texttt{isa} entry in the line number information
(see Section \refersec{chap:statemachineregisters}).
}
information entry in the current compilation unit, which must be a
\DWTAGbasetype{} entry that provides the type of the constant provided. The
second operand is 1-byte unsigned integer that specifies the size of the
-constant value, which may not be larger than the size of the largest supported
-base type of the target machine. The third operand is a block of specified
+constant value, which is the same as the size of the base type referenced
+by the first operand. The third operand is a block of specified
size that is to be interpreted as a value of the referenced type.
\textit{While the size of the constant could be inferred from the base type
-definition, it is encoded explicitly into the expression so that the
-expression can be parsed easily without reference to the \dotdebuginfo{}
+definition, it is encoded explicitly into the operation so that the
+operation can be parsed easily without reference to the \dotdebuginfo{}
section.}
\end{enumerate}
In the \DWOPdereftypeNAME{} operation, the size in
bytes of the data retrieved from the dereferenced address is specified by
the first operand. This operand is a 1-byte unsigned integral constant whose
-value may not be larger than the size of the largest supported base type on
-the target machine. The second operand is an unsigned LEB128 integer that
+value which is the same as the size of the base type referenced
+by the second operand.
+The second operand is an unsigned LEB128 integer that
represents the offset of a debugging information entry in the current
compilation unit, which must be a \DWTAGbasetype{} entry that provides the
type of the data pushed.
+\textit{While the size of the pushed value could be inferred from the base
+type definition, it is encoded explicitly into the operation so that the
+operation can be parsed easily without reference to the \dotdebuginfo{}
+section.}
+
\needlines{7}
\itembfnl{\DWOPxderefTARG}
The \DWOPxderefNAME{} operation provides an extended dereference
an address space identifier, and pushes the value retrieved. In the
\DWOPxdereftypeNAME{} operation, the size in bytes of the data retrieved from
the dereferenced address is specified by the first operand. This operand is
-a 1-byte unsigned integral constant whose value may not be larger than the
-size of the largest supported base type on the target machine. The second
+a 1-byte unsigned integral constant whose value
+value which is the same as the size of the base type referenced
+by the second operand. The second
operand is an unsigned LEB128 integer that represents the offset of a
debugging information entry in the current compilation unit, which must be a
\DWTAGbasetype{} entry that provides the type of the data pushed.
\needlines{4}
\begin{enumerate}[1. ]
\itembfnl{\DWOPabsTARG}
-The \DWOPabsTARG{} operation pops the top stack entry, interprets
+The \DWOPabsNAME{} operation pops the top stack entry, interprets
it as a signed value and pushes its absolute value. If the
absolute value cannot be represented, the result is undefined.
\needlines{4}
\itembfnl{\DWOPandTARG}
-The \DWOPandTARG{} operation pops the top two stack values, performs
+The \DWOPandNAME{} operation pops the top two stack values, performs
a bitwise and operation on the two, and pushes the result.
\itembfnl{\DWOPdivTARG}
-The \DWOPdivTARG{} operation pops the top two stack values, divides the former second entry by
+The \DWOPdivNAME{} operation pops the top two stack values, divides the former second entry by
the former top of the stack using signed division, and pushes the result.
\itembfnl{\DWOPminusTARG}
-The \DWOPminusTARG{} operation pops the top two stack values, subtracts the former top of the
+The \DWOPminusNAME{} operation pops the top two stack values, subtracts the former top of the
stack from the former second entry, and pushes the result.
\itembfnl{\DWOPmodTARG}
-The \DWOPmodTARG{} operation pops the top two stack values and pushes the result of the
+The \DWOPmodNAME{} operation pops the top two stack values and pushes the result of the
calculation: former second stack entry modulo the former top of the stack.
\needlines{4}
\itembfnl{\DWOPmulTARG}
-The \DWOPmulTARG{} operation pops the top two stack entries, multiplies them together, and
+The \DWOPmulNAME{} operation pops the top two stack entries, multiplies them together, and
pushes the result.
\itembfnl{\DWOPnegTARG}
-The \DWOPnegTARG{} operation pops the top stack entry, interprets
+The \DWOPnegNAME{} operation pops the top stack entry, interprets
it as a signed value and pushes its negation. If the negation
cannot be represented, the result is undefined.
\itembfnl{\DWOPnotTARG}
-The \DWOPnotTARG{} operation pops the top stack entry, and pushes
+The \DWOPnotNAME{} operation pops the top stack entry, and pushes
its bitwise complement.
\itembfnl{\DWOPorTARG}
-The \DWOPorTARG{} operation pops the top two stack entries, performs
+The \DWOPorNAME{} operation pops the top two stack entries, performs
a bitwise or operation on the two, and pushes the result.
\itembfnl{\DWOPplusTARG}
-The \DWOPplusTARG{} operation pops the top two stack entries,
+The \DWOPplusNAME{} operation pops the top two stack entries,
adds them together, and pushes the result.
\needlines{6}
\itembfnl{\DWOPplusuconstTARG}
-The \DWOPplusuconstTARG{} operation pops the top stack entry,
+The \DWOPplusuconstNAME{} operation pops the top stack entry,
adds it to the unsigned LEB128\addtoindexx{LEB128!unsigned}
constant operand and pushes the result.
\needlines{3}
\itembfnl{\DWOPshlTARG}
-The \DWOPshlTARG{} operation pops the top two stack entries,
+The \DWOPshlNAME{} operation pops the top two stack entries,
shifts the former second entry left (filling with zero bits)
by the number of bits specified by the former top of the stack,
and pushes the result.
\itembfnl{\DWOPshrTARG}
-The \DWOPshrTARG{} operation pops the top two stack entries,
+The \DWOPshrNAME{} operation pops the top two stack entries,
shifts the former second entry right logically (filling with
zero bits) by the number of bits specified by the former top
of the stack, and pushes the result.
\needlines{3}
\itembfnl{\DWOPshraTARG}
-The \DWOPshraTARG{} operation pops the top two stack entries,
+The \DWOPshraNAME{} operation pops the top two stack entries,
shifts the former second entry right arithmetically (divide
the magnitude by 2, keep the same sign for the result) by
the number of bits specified by the former top of the stack,
and pushes the result.
\itembfnl{\DWOPxorTARG}
-The \DWOPxorTARG{} operation pops the top two stack entries,
+The \DWOPxorNAME{} operation pops the top two stack entries,
performs a bitwise exclusive\dash or operation on the two, and
pushes the result.
\needlines{4}
\itembfnl{\DWOPregxTARG}
-The \DWOPregxTARG{} operation has a single
+The \DWOPregxNAME{} operation has a single
unsigned LEB128\addtoindexx{LEB128!unsigned} literal
operand that encodes the name of a register.
or is computed from other locations and values in the program.
\begin{enumerate}[1. ]
\itembfnl{\DWOPimplicitvalueTARG}
-The \DWOPimplicitvalueTARG{}
+The \DWOPimplicitvalueNAME{}
operation specifies an immediate value
using two operands: an unsigned LEB128\addtoindexx{LEB128!unsigned}
length, followed by
in bytes of the \nolink{block}.
\itembfnl{\DWOPstackvalueTARG}
-The \DWOPstackvalueTARG{}
+The \DWOPstackvalueNAME{}
operation specifies that the object
does not exist in memory but its value is nonetheless known
and is at the top of the DWARF expression stack. In this form
\textit{DWARF location expressions are intended to yield the \textbf{location}
of a value rather than the value itself. An optimizing compiler
may perform a number of code transformations where it becomes
-impossible to give a location for a value, but remains possible
+impossible to give a location for a value, but it remains possible
to describe the value itself.
Section \refersec{chap:registerlocationdescriptions}
describes operators that can be used to
of the resultant value is contained.
\begin{enumerate}[1. ]
\itembfnl{\DWOPpieceTARG}
-The \DWOPpieceTARG{} operation takes a
+The \DWOPpieceNAME{} operation takes a
single operand, which is an
unsigned LEB128\addtoindexx{LEB128!unsigned} number.
The number describes the size in bytes
refers to. }
\itembfnl{\DWOPbitpieceTARG}
-The \DWOPbitpieceTARG{}
+The \DWOPbitpieceNAME{}
operation takes two operands. The first
is an unsigned LEB128\addtoindexx{LEB128!unsigned}
number that gives the size in bits
Any debugging information entry describing a declaration that
has a type has
\addtoindexx{type attribute}
-a \DWATtype{} attribute, whose value is a
+a \DWATtypeDEFN{} attribute, whose value is a
reference to another debugging information entry. The entry
referenced may describe a base type, that is, a type that is
not defined in terms of other data types, or it may describe a
volatile, which in turn will reference another entry describing
a type or type modifier (using
\addtoindexx{type attribute}
-a \DWATtype{} attribute of its
+a \DWATtypeNAME{} attribute of its
own). See
Section \referfol{chap:typeentries}
for descriptions of the entries describing
The accessibility of a declaration is
\hypertarget{chap:DWATaccessibilitycandadadeclarations}{}
represented by a
-\DWATaccessibility{}
+\DWATaccessibilityDEFN{}
attribute, whose
\addtoindexx{accessibility attribute}
value is a constant drawn from the set of codes listed in Table
The
\hypertarget{chap:DWATvisibilityvisibilityofdeclaration}{}
visibility of a declaration is represented
-by a \DWATvisibility{}
+by a \DWATvisibilityDEFN{}
attribute\addtoindexx{visibility attribute}, whose value is a
constant drawn from the set of codes listed in
Table \refersec{tab:visibilitycodes}.
The
\hypertarget{chap:DWATvirtualityvirtualityindication}{}
virtuality of a declaration is represented by a
-\DWATvirtuality{}
+\DWATvirtualityDEFN{}
attribute\addtoindexx{virtuality attribute}, whose value is a constant drawn
from the set of codes listed in
Table \refersec{tab:virtualitycodes}.
a compiler and not explicitly declared by the source program
\hypertarget{chap:DWATartificialobjectsortypesthat}{}
may have a
-\DWATartificial{} attribute,
+\DWATartificialDEFN{} attribute,
which is a \livelink{chap:classflag}{flag}.
\needlines{6}
Any debugging information entry that contains a description
\hypertarget{chap:DWATsegmentaddressinginformation}{}
of the location of an object or subroutine may have a
-\DWATsegment{} attribute,
+\DWATsegmentDEFN{} attribute,
\addtoindexx{segment attribute}
whose value is a location
description. The description evaluates to the segment selector
of the item being described. If the entry containing the
-\DWATsegment{} attribute has a
+\DWATsegmentNAME{} attribute has a
\DWATlowpc,
\DWAThighpc,
\DWATranges{} or
values represent the offset portion of the address within
the segment specified
\addtoindexx{segment attribute}
-by \DWATsegment.
+by \DWATsegmentNAME.
If an entry has no
-\DWATsegment{} attribute, it inherits
+\DWATsegmentNAME{} attribute, it inherits
\addtoindexx{segment attribute}
the segment value from its parent entry. If none of the
entries in the chain of parents for this entry back to
its containing compilation unit entry have
-\DWATsegment{} attributes,
+\DWATsegmentNAME{} attributes,
then the entry is assumed to exist within a flat
address space.
Similarly, if the entry has a
-\DWATsegment{} attribute
+\DWATsegmentNAME{} attribute
\addtoindexx{segment attribute}
containing an empty location description, that
entry is assumed to exist within a
\addtoindex{incomplete declaration}
of a program entity has a
\addtoindexx{declaration attribute}
-\DWATdeclaration{} attribute, which is a
+\DWATdeclarationDEFN{} attribute, which is a
\livelink{chap:classflag}{flag}.
\subsection{Declarations Completing Non-Defining Declarations}
A debugging information entry that represents a
declaration\hypertarget{chap:DWATspecificationincompletenondefiningorseparatedeclaration}{}
that completes another (earlier) non-defining declaration may have a
-\DWATspecification{}
+\DWATspecificationDEFN{}
attribute whose value is a \livelink{chap:classreference}{reference} to
the debugging information entry representing the non-defining declaration.
A debugging information entry with a
-\DWATspecification{}
+\DWATspecificationNAME{}
attribute does not need to duplicate information provided by the
debugging information entry referenced by that specification attribute.
may
\addtoindex{declaration line attribute}
have
-\DWATdeclfile,
-\DWATdeclline{} and
-\DWATdeclcolumn{}
+\DWATdeclfileDEFN,
+\DWATdecllineDEFN{} and
+\DWATdeclcolumnDEFN{}
attributes each of whose value is an unsigned
\livelink{chap:classconstant}{integer constant}.
representing
\addtoindexx{names!identifier}
a program entity that has been given a name may have a
-\DWATname{}
+\DWATnameDEFN{}
attribute\addtoindexx{name attribute}, whose value of
\CLASSstring{} represents the name as it appears in
the source program. A debugging information entry containing
may have
\addtoindexx{location attribute}
a
-\DWATlocation{} attribute,
+\DWATlocationDEFN{} attribute,
\addtoindexx{location attribute}
whose value is a location description
(see Section \refersec{chap:locationdescriptions}).
A
\addtoindex{DWARF procedure}
is represented by any
-kind of debugging information entry that has
+kind of debugging information entry that has a
\addtoindexx{location attribute}
-a
-\DWATlocation{}
+\DWATlocationNAME{}
attribute.
\addtoindexx{location attribute}
If a suitable entry is not otherwise available,
tag \DWTAGdwarfprocedureTARG{}
together with
\addtoindexx{location attribute}
-a \DWATlocation{} attribute.
+a \DWATlocationNAME{} attribute.
A DWARF procedure
is called by a \DWOPcalltwo,
Any debugging information entry describing an entity that has
a machine code address or range of machine code addresses,
which includes compilation units, module initialization,
-\hypertarget{chap:DWATrangesnoncontiguousrangeofcodeaddresses}{}
subroutines, ordinary \nolink{blocks},
try/catch \nolink{blocks} (see Section\refersec{chap:tryandcatchblockentries}),
labels and the like, may have
\begin{itemize}
-\item A \DWATlowpc{} attribute for
+\item A \DWATlowpcDEFN{} attribute for
\hypertarget{chap:DWATlowpccodeaddressorrangeofaddresses}{}
a single address,
-\item A \DWATlowpc{}
+\item A \DWATlowpcDEFN{}
\addtoindexx{low PC attribute}
and
-\DWAThighpc{}
+\DWAThighpcDEFN{}
\addtoindexx{high PC attribute}
\hypertarget{chap:DWAThighpccontiguousrangeofcodeaddresses}{}
pair of attributes for
a single contiguous range of
addresses, or
-\item A \DWATranges{} attribute
+\item A \DWATrangesDEFN{} attribute
\addtoindexx{ranges attribute}
+\hypertarget{chap:DWATrangesnoncontiguousrangeofcodeaddresses}{}
for a non-contiguous range of addresses.
\end{itemize}
module initialization, subroutines,
\livelink{chap:lexicalblock}{lexical \nolink{blocks}},
\livelink{chap:tryandcatchblockentries}{try/catch \nolink{blocks}},
-and the like, may have a \DWATentrypcNAME{} attribute
+and the like, may have a \DWATentrypcDEFN{} attribute
\addtoindexx{entry PC address}
to indicate the first executable instruction within that
range\hypertarget{chap:entryaddressofscope}{}
Generally, any debugging information entry that
\hypertarget{chap:DWATdescriptionartificialnameordescription}{}
-has, or may have,
-\addtoindexx{name attribute}
-a
-\DWATname{} attribute, may
-also have
+has, or may have, a \DWATname{} attribute, may
+also have a
\addtoindexx{description attribute}
-a
-\DWATdescription{} attribute whose value is a
+\DWATdescriptionDEFN{} attribute whose value is a
null-terminated string providing a description of the entity.
\textit{It is expected that a debugger will only display these
\label{chap:byteandbitsizes}
% Some trouble here with hbox full, so we try optional word breaks.
Many debugging information entries allow either a
-\DWATbytesize{} attribute or a
-\DWATbitsize{} attribute,
+\DWATbytesizeNAME{} attribute or a
+\DWATbitsizeNAME{} attribute,
whose \livelink{chap:classconstant}{integer constant} value
(see Section \ref{chap:staticanddynamicvaluesofattributes})
specifies an
amount of storage. The value of the
-\DWATbytesize{} attribute
+\DWATbytesizeDEFN{} attribute
is interpreted in bytes and the value of the
-\DWATbitsize{}
+\DWATbitsizeDEFN{}
attribute is interpreted in bits. The
\DWATstringlengthbytesize{} and
\DWATstringlengthbitsize{}
}
% Some trouble maybe with hbox full, so we try optional word breaks.
-A debugging information entry may have
+A debugging information entry may have a
\addtoindexx{linkage name attribute}
-a
-\DWATlinkagename{}
+\DWATlinkagenameDEFN{}
attribute whose value is a null-terminated string containing the
object file linkage name associated with the corresponding entity.
actual compile-time or run-time constant value
of the value parameter for this instantiation.
This can be a
-\DWATconstvalue{}\livetarg{chap:DWATconstvaluetemplatevalueparameter}{}
-attribute, whose value is the compile-time constant value
+\DWATconstvalueDEFN{} attribute,
+\addtoindexx{constant value attribute}
+\livetarg{chap:DWATconstvaluetemplatevalueparameter}{}
+whose value is the compile-time constant value
as represented on the target architecture, or a
\DWATlocation{} attribute, whose value is a
single location description for the run-time constant address.
\label{chap:alignment}
\livetarg{chap:DWATalignmentnondefault}{}
A debugging information entry may have a
-\DWATalignment{} attribute\addtoindexx{alignment attribute}
+\DWATalignmentDEFN{} attribute\addtoindexx{alignment attribute}
that describes the (non-default) alignment requirements of the entry.
\DWATalignment{} has a positive, non-zero, integer constant value
describing the strictest specified (non-default) alignment of the entity.
entry for each unique type unit in the module. Each list is indexed
starting at 0.
-The list of foreign TUs is an array of 8-byte (\DWFORMrefsigeight) type
+The list of foreign TUs is an array of 64-bit (\DWFORMrefsigeight) type
signatures, representing types referenced by the index whose
definitions have been placed in a different object file (that is, a split
DWARF object). This list may be empty.
The foreign TU list immediately follows the local TU list
and they both use the same index, so that if there are $N$ local TU entries,
-the index for the first foreign TU is $N+1$.
+the index for the first foreign TU is $N$.
The name table is logically a table with a row for each unique name in
the index, and two columns. The first column contains a reference to
\subsubsubsection{List of Foreign TUs}
The list of foreign TUs immediately follows the list of local TUs.
-Each entry in the list is an 8-byte type signature (as described by
+Each entry in the list is an 64-bit type signature (as described by
\DWFORMrefsigeight).
The number of entries in the list is given by \texttt{foreign\_type\_unit\_count}.
The following terms are used in the description of the line
number information format:
-\begin{longtable} {lp{9cm}}
+\begin{longtable} {lP{9cm}}
state machine &
The hypothetical machine used by a consumer of the line number
information to expand the byte\dash coded
The line number information state machine has a number of
registers as shown in Table \referfol{tab:statemachineregisters}.
-\begin{longtable}{l|p{9cm}}
+\begin{longtable}{l|P{9cm}}
\caption{State machine registers } \label{tab:statemachineregisters} \\
\hline \bfseries Register name&\bfseries Meaning\\ \hline
\endfirsthead
\textit{The representation of debugging information in the \dotdebugmacinfo{} section is specified
in earlier versions of the DWARF standard. Note that the \dotdebugmacinfo{} section does not contain
-any headers and does not support indirect string encodings or transparent includes (see below).}
+any headers and does not support sharing of strings or sharing of repeated macro sequences.}
-The macro information for each
-compilation unit starts with a header followed by a series of
-macro information
-entries. Each entry consists of an opcode
-followed by zero or more operands. The series of entries for a
-given compilation unit ends with an entry containing an opcode of 0.
+The macro information for each compilation unit consists of one or
+more macro units. Each macro unit starts with a header
+and is followed by a series of macro information entries or file
+inclusion entries. Each entry consists of an opcode followed by
+zero or more operands. Each macro unit ends with an entry
+containing an opcode of 0.
+\needlines{6}
\subsection{Macro Information Header}
The macro information header contains the following fields:
of flags, some of which may indicate that additional fields follow.
The following flags, beginning with the least significant bit, are defined:
\begin{itemize}
-\item \addttindex{offset\_size\_flag} \\
-If the \texttt{offset\_size} flag is zero, the header is for a 32-bit
+\item \HFNoffsetsizeflag \\
+If the \HFNoffsetsizeflag{} is zero, the header is for a 32-bit
DWARF format macro section and all offsets are 4 bytes long;
if it is one, the header is for a 64-bit DWARF format macro section
and all offsets are 8 bytes long.
allocated in the range from \DWMACROlouser{} to \DWMACROhiuser. Other
unassigned codes are reserved for future DWARF standards.
+\needlines{4}
The table starts with a 1-byte \texttt{count} of the defined opcodes, followed by
an entry for each of those opcodes. Each entry starts with a 1-byte unsigned
opcode number, followed by unsigned LEB128\addtoindexx{ULEB128} encoded number of operands
\subsection{Macro Information Entries}
\label{chap:macroinformationentries}
All macro information entries within a \dotdebugmacro{}
-section for a
-given compilation unit appear in the same order in which the
-directives were processed by the compiler.
+section for a given compilation unit appear in the same
+order in which the directives were processed by the
+compiler (after taking into account the effect of the
+macro import directives).
\subsubsection{Define and Undefine Entries}
The second operand is a null-terminated character
string for the macro being defined or undefined.
-The contents of the string is described below (see Sections
+The contents of the operands are described below (see Sections
\ref{chap:macrodefinestring} and \referfol{chap:macroundefinestring}).
-\itembfnl{\DWMACROdefineindirectTARG{}, \DWMACROundefindirectTARG{}}
-A \DWMACROdefineindirectNAME{} or \DWMACROundefindirectNAME{}
-entry has two operands. The first operand encodes the line number
+\itembfnl{\DWMACROdefinestrpTARG{}, \DWMACROundefstrpTARG{}}
+A \DWMACROdefinestrpNAME{} or \DWMACROundefstrpNAME{}
+entry has two operands. The first operand encodes the source line number
of the \texttt{\#define} or \texttt{\#undef} macro directive.
The second operand consists of an offset into a string table contained in
the \dotdebugstr{} section of the object file. The size of the operand is
-given in the header \texttt{offset\_size} field.
+given in the header \HFNoffsetsizeflag{} field.
-The contents of the string is described below (see Sections
+The contents of the operands are described below (see Sections
\ref{chap:macrodefinestring} and \referfol{chap:macroundefinestring}).
-\itembfnl{\DWMACROdefineindirectxTARG{}, \DWMACROundefindirectxTARG{}}
-A \DWMACROdefineindirectxNAME{} or \DWMACROundefindirectxNAME{} entry
+\itembfnl{\DWMACROdefinestrxTARG{}, \DWMACROundefstrxTARG{}}
+A \DWMACROdefinestrxNAME{} or \DWMACROundefstrxNAME{} entry
has two operands. The first operand encodes the line number
of the \texttt{\#define} or \texttt{\#undef} macro directive.
-
The second operand identifies a string; it is represented using an
unsigned LEB128\addtoindexx{ULEB128} encoded value,
which is interpreted as a zero-based index into an array of offsets in the
\dotdebugstroffsets{} section.
-The contents of the string is described below (see Sections
+The contents of the operands are described below (see Sections
\ref{chap:macrodefinestring} and \referfol{chap:macroundefinestring}).
\needlines{6}
-\itembfnl{\DWMACROdefineindirectsupTARG{}, \DWMACROundefindirectsupTARG{}}
-A \DWMACROdefineindirectsupNAME{} or \DWMACROundefindirectsupNAME{} entry
+\itembfnl{\DWMACROdefinesupTARG{}, \DWMACROundefsupTARG{}}
+A \DWMACROdefinesupNAME{} or \DWMACROundefsupNAME{} entry
has two operands. The first operand encodes the line number
of the \texttt{\#define} or \texttt{\#undef} macro directive.
The second operand identifies a string; it is represented as
an offset into a string table contained in the \dotdebugstr{}
section of the \addtoindex{supplementary object file}.
The size of the operand depends on the macro section header
-\texttt{offset\_size} field.
+\HFNoffsetsizeflag{} field.
-The contents of the string is described below (see Sections
+The contents of the operands are described below (see Sections
\ref{chap:macrodefinestring} and \referfol{chap:macroundefinestring}).
\end{enumerate}
\subsubsection{Macro Source Line Number}
\label{char:macrosourcelinenumber}
-In all the define and undefine macro information entries,
+In all define and undefine macro information entries,
+as well as the \DWMACROstartfile{} entry,
the line number of the entry occurs is encoded as an
unsigned LEB128 integer.
\label{chap:macrodefinestring}
In the case of a
\DWMACROdefine{},
-\DWMACROdefineindirect{},
-\DWMACROdefineindirectx{} or
-\DWMACROdefineindirectsup{}
+\DWMACROdefinestrp{},
+\DWMACROdefinestrx{} or
+\DWMACROdefinesup{}
entry, the value of the
second operand is the name of the macro symbol that is defined
at the indicated source line, followed immediately by the
\label{chap:macroundefinestring}
In the case of a
\DWMACROundef{},
-\DWMACROundefindirect{},
-\DWMACROundefindirectx{} or
-\DWMACROundefindirectsup{}
+\DWMACROundefstrp{},
+\DWMACROundefstrx{} or
+\DWMACROundefsup{}
entry, the value of the second string is the name of the pre-processor
symbol that is undefined at the indicated source line.
\subsubsection{Entries for Command Line Options}
\label{chap:entriesforcommandlineoptions}
-\DWMACROdefineINDX{}\DWMACROdefineindirectINDX{}\DWMACROdefineindirectxINDX
-\DWMACROundefINDX{}\DWMACROundefindirectINDX{}\DWMACROundefindirectxINDX
+\DWMACROdefineINDX{}\DWMACROdefinestrpINDX{}\DWMACROdefinestrxINDX
+\DWMACROundefINDX{}\DWMACROundefstrpINDX{}\DWMACROundefstrxINDX
A DWARF producer
generates a define or undefine entry for
each pre-processor symbol which is defined or undefined by
All such define and undefine entries representing compilation
options appear before the first \DWMACROstartfile{}
entry for that compilation unit
-(see Section \referfol{chap:fileinclusionentries}
+(see Section \referfol{chap:fileinclusionentries})
and encode the value 0 in their line number operands.
\subsection{File Inclusion Entries}
\label{chap:fileinclusionentries}
+\subsubsection{Source Include Directives}
+\label{chap:sourceincludedirectives}
+
+The following directives describe a source
+file inclusion directive (\texttt{\#include} in
+\addtoindex{C}/\addtoindex{C++}) and the
+ending of an included file.
+
\begin{enumerate}[1. ]
\itembfnl{\DWMACROstartfileTARG{}}
A \DWMACROstartfileNAME{} entry has two operands. The
first operand encodes the line number of the source line on
-which the \texttt{\#include} macro directive occurred
+which the \texttt{\#include} macro directive occur
(see Section \refersec{char:macrosourcelinenumber}).
The second operand encodes a source file name index.
the file entry in the line number information table for the
primary source file.
-\subsubsection{Inclusion of a Sequence of Entries}
-\label{chap:transparentincludeofasequenceofentries}
-The transparent include entry types make it possible
-to share duplicate sequences of macro information entries.
-The first form supports sharing within the current compilation
-and the second form supports sharing across separate
+\subsubsection{Importation of Macro Units}
+\label{chap:importationofmacrounits}
+The import entries make it possible to replicate macro units.
+The first form supports replication within the current compilation
+and the second form supports replication across separate
executable or shared object files.
+\textit{Import entries do not reflect the source program
+and, in fact, are not necessary at all. However, they do
+provide a mechanism that can be used to reduce redundancy
+in the macro information and thereby to save space.}
\begin{enumerate}[1. ]
-\itembfnl{\DWMACROtransparentincludeTARG{}}
-A \DWMACROtransparentincludeNAME{} entry has one operand, an offset into
-another part of the \dotdebugmacro{} section. The size of the operand
-depends on the header \texttt{offset\_size} field. The
-\DWMACROtransparentincludeNAME{} entry instructs the consumer to
-replace it with a sequence of entries beginning at the given
+\itembfnl{\DWMACROimportTARG{}}
+A \DWMACROimportNAME{} entry has one operand, an offset into
+another part of the \dotdebugmacro{} section that is
+the beginning of a target macro unit. The size of the operand
+depends on the header \HFNoffsetsizeflag{} field. The
+\DWMACROimportNAME{} entry instructs the consumer to
+replicate the sequence of entries following the target macro
+header which begins at the given
\dotdebugmacro{} offset, up to, but excluding,
-the terminating entry with opcode \texttt{0}.
+the terminating entry with opcode \texttt{0},
+as though it occurs in place of the import operation.
-\itembfnl{\DWMACROtransparentincludesupTARG}
-A \DWMACROtransparentincludesupNAME{} entry has one operand, an
+\itembfnl{\DWMACROimportsupTARG}
+A \DWMACROimportsupNAME{} entry has one operand, an
offset from the start of the \dotdebugmacro{} section in the
\addtoindex{supplementary object file}.
The size of the operand depends on the section header
-\texttt{offset\_size} field.
-Apart from the different location in which to find the sequence of
-macro information entries this entry type is equivalent to
-\DWMACROtransparentinclude.
+\HFNoffsetsizeflag{} field.
+Apart from the different location in which to find the macro unit,
+this entry type is equivalent to \DWMACROimport.
\textit{This entry type is aimed at sharing duplicate
-sequences of macro information entries between \dotdebugmacro{}
+macro units between \dotdebugmacro{}
sections from different executable or shared object files.}
\needlines{4}
From within the \dotdebugmacro{} section of the
-\addtoindex{supplementary object file}, \DWMACROdefineindirect{}
-and \DWMACROundefindirect{} entries refer to the
+\addtoindex{supplementary object file}, \DWMACROdefinestrp{}
+and \DWMACROundefstrp{} entries refer to the
\dotdebugstr{} section of that same supplementary file;
-similarly, \DWMACROtransparentinclude{} entries refer to the
+similarly, \DWMACROimport{} entries refer to the
\dotdebugmacro{} section of that same supplementary file.
\end{enumerate}
\needlines{6}
The register rules are:
-\begin{longtable}{lp{8cm}}
+\begin{longtable}{lP{9cm}}
undefined
&A register that has this rule has no recoverable value in the previous frame.
(By convention, it is not preserved by a callee.) \\
contiguous, there may be multiple CIEs and FDEs corresponding
to the parts of that function.}
-
+\needlines{6}
A Common Information Entry holds information that is shared
among many Frame Description Entries. There is at least one
CIE in every non-empty \dotdebugframe{} section. A CIE contains
\item \texttt{instructions} (array of \HFTubyte) \\
A sequence of table defining instructions that are described below.
+\needlines{4}
\item \texttt{padding} (array of \HFTubyte) \\
Enough \DWCFAnop{} instructions
to make the size of this entry match the length value above.
All other values in the new row are initially identical to the
current row
+\needlines{6}
\item \textbf{\DWCFAadvanceloconeTARG{}} \\
The \DWCFAadvanceloconeNAME{} instruction takes a single \HFTubyte{}
operand that represents a constant delta. This instruction
is identical to \DWCFAadvanceloc{} except for the encoding
and size of the delta operand.
-\needlines{6}
\item \textbf{\DWCFAadvanceloctwoTARG} \\
The \DWCFAadvanceloctwoNAME{} instruction takes a single \HFTuhalf{}
operand that represents a constant delta. This instruction
operation is valid only if the current CFA rule is defined
to use a register and offset.
-
+\needlines{6}
\item \textbf{\DWCFAdefcfaoffsetsfTARG} \\
The \DWCFAdefcfaoffsetsfNAME{} instruction takes a signed
LEB128\addtoindexx{LEB128!signed} operand representing a factored offset. This instruction
\DWCFAoffset{}
except for the encoding and size of the register operand.
+\needlines{6}
\item \textbf{\DWCFAoffsetextendedsfTARG} \\
The \DWCFAoffsetextendedsfNAME{}
instruction takes two operands:
\addtoindexx{range list}
(see Section \refersec{chap:noncontiguousaddressranges}).
-\item A \DWATname{} attribute
+\item A \DWATnameDEFN{} attribute
\addtoindexx{name attribute}
-whose value is a null\dash terminated
-string
+whose value is a null-terminated string
\hypertarget{chap:DWATnamepathnameofcompilationsource}{}
containing the full or relative path name of the primary
source file from which the compilation unit was derived.
-\item A \DWATlanguage{} attribute
+\item A \DWATlanguageDEFN{} attribute
\addtoindexx{language attribute}
whose constant value is an
\hypertarget{chap:DWATlanguageprogramminglanguage}{}
\end{centering}
\needlines{6}
-\item A \DWATstmtlist{}\hypertarget{chap:DWATstmtlistlinenumberinformationforunit}{}
-attribute whose value is
+\item A \DWATstmtlistDEFN{}
+\hypertarget{chap:DWATstmtlistlinenumberinformationforunit}{}
\addtoindexx{statement list attribute}
-a
+attribute whose value is a
\addtoindexx{section offset!in statement list attribute}
section offset to the line number information for this compilation
unit.
information for this compilation unit
(see Section \refersec{chap:linenumberinformation}).
-\item A \DWATmacros{}\hypertarget{chap:DWATmacrosmacroinformation}{}
+\item A \DWATmacrosDEFN{}\hypertarget{chap:DWATmacrosmacroinformation}{}
attribute
\addtoindexx{macro information attribute}
whose value is a
information for this compilation unit
(see Section \refersec{chap:macroinformation}).
-\textit{The \DWATmacros{} attribute is new in \DWARFVersionV,
+\textit{The \DWATmacrosNAME{} attribute is new in \DWARFVersionV,
and supersedes the
-\DWATmacroinfo{} attribute of earlier DWARF versions.
+\DWATmacroinfoDEFN{} attribute of earlier DWARF versions.
\livetarg{chap:DWATmacroinfomacroinformation}{}
-While \DWATmacros{} and \DWATmacroinfo{} attributes cannot both occur in the same
+While \DWATmacrosNAME{} and \DWATmacroinfoNAME{} attributes cannot both occur in the same
compilation unit, both may be found in the set of units that make up an executable
or shared object file. The two attributes have distinct encodings to facilitate such
coexistence.}
\needlines{6}
\item A
-\DWATcompdir{}
-attribute
+\DWATcompdirDEFN{} attribute\addtoindexx{compilation directory attribute}
\hypertarget{chap:DWATcompdircompilationdirectory}{}
whose value is a
-null\dash terminated string containing the current working directory
+null-terminated string containing the current working directory
of the compilation command that produced this compilation
unit in whatever form makes sense for the host system.
-\item A \DWATproducer{} attribute
+\item A \DWATproducerDEFN{} attribute
\addtoindexx{producer attribute}
-whose value is a null\dash
-terminated string containing information about the compiler
+whose value is a null-terminated string containing
+information about the compiler
\hypertarget{chap:DWATproducercompileridentification}{}
that produced the compilation unit. The actual contents of
the string will be specific to each producer, but should
with other producer values.
\needlines{4}
-\item A \DWATidentifiercase{}
+\item A \DWATidentifiercaseDEFN{}
attribute
\addtoindexx{identifier case attribute}
whose integer
access those names.
\needlines{5}
-\item A \DWATbasetypes{} attribute whose value is a
-\livelink{chap:classreference}{reference}.
-
-This
+\item A \DWATbasetypesDEFN{} attribute whose value is a
+\livelink{chap:classreference}{reference}. This
\hypertarget{chap:DWATbasetypesprimitivedatatypesofcompilationunit}{}
attribute
\addtoindexx{base types attribute}
\hypertarget{chap:DWATuseUTF8compilationunitusesutf8strings}{}
correctly.}
-\item A \DWATuseUTFeight{} attribute,
+\item A \DWATuseUTFeightDEFN{} attribute,
\addtoindexx{use UTF8 attribute}\addtoindexx{UTF-8}
which is a \livelink{chap:classflag}{flag} whose
presence indicates that all strings (such as the names of
are represented using the UTF\dash 8 representation.
\needlines{4}
-\item A \DWATmainsubprogram{} attribute, which is a \livelink{chap:classflag}{flag}
+\item A \DWATmainsubprogramDEFN{} attribute, which is a
+\livelink{chap:classflag}{flag}
\addtoindexx{main subprogram attribute}
whose presence indicates
\hypertarget{chap:DWATmainsubprogramunitcontainingmainorstartingsubprogram}{}
Section \refersec{chap:entryaddress}).
\needlines{8}
-\item A \DWATstroffsetsbaseNAME\addtoindexx{string offset base attribute}
+\item A \DWATstroffsetsbaseDEFN\addtoindexx{string offset base attribute}
\hypertarget{chap:DWATstroffsetbaseforindirectstringtable}{}
attribute, whose value is a reference.
This attribute points to the first string
interpreted as indices relative to this base.
\needlines{5}
-\item A \DWATrangesbaseNAME\addtoindexx{ranges table base attribute}
+\item A \DWATrangesbaseDEFN\addtoindexx{ranges table base attribute}
\hypertarget{chap:DWATrangesbaseforrangelists}{}
attribute, whose value is a reference.
This attribute points to the beginning of the compilation
When generating a \splitDWARFobjectfile{} (see
Section \refersec{datarep:splitdwarfobjectfiles}), the
compilation unit in the \dotdebuginfo{} section is a "skeleton"
-compilation unit, which contains \DWATdwoname{} and \DWATdwoid{}
-attributes as well as a subset of the
+compilation unit with the tag \DWTAGcompileunit, which contains
+\DWATdwoname{} and \DWATdwoid{} attributes as well as a subset of the
attributes of a full normal or partial compilation unit. In general,
it contains those attributes that are necessary for the consumer
to locate the object file where the full compilation unit
\item
\livetarg{chap:DWATdwonameforunit}{}
-A \DWATdwonameNAME{} attribute whose value is a
+A \DWATdwonameDEFN{} attribute
+\addtoindexx{split DWARF object file name attribute}
+whose value is a
null-terminated string containing the full or relative
path name of the object file that contains the full
compilation unit.
\item
\livetarg{chap:DWATdwoidforunit}{}
-A \DWATdwoidNAME{} attribute whose value is an 8-byte
+A \DWATdwoidDEFN{} attribute\addtoindexx{unit signature attribute}
+whose value is an 8-byte
unsigned hash of the full compilation unit. This hash
value is computed by the method described in
Section \refersec{datarep:typesignaturecomputation}.
both entries so that the consumer can verify that it has
found the correct object file.
+\textit{The \DWATaddrbase{}, \DWATrangesbase{} and \DWATstroffsetsbase{}
+attributes provide context that may be necessary to interpret the contents
+of the corresponding \splitDWARFobjectfile.}
+
\needlines{6}
\subsection{Type Unit Entries}
\label{chap:typeunitentries}
information for this type unit.
Because type units do not describe any code, they
do not actually need a line number table, but the line number
-tables also contain a list of directories and file names that
-may be referenced by the \DWATdeclfile{} attribute. In a
+headers contain a list of directories and file names that
+may be referenced by the \DWATdeclfile{} attribute of the
+type or part of its description.
+\begin{itemize}
+\item In a
normal object file with a regular compilation unit entry, the
type unit entries can simply refer to the line number table
-used by the compilation unit. In a \splitDWARFobjectfile, where
+used by the compilation unit.
+\item In a \splitDWARFobjectfile, where
the type units are located in a separate DWARF object file,
the \DWATstmtlist{} attribute refers to a "specialized"
line number table in the \dotdebuglinedwo{} section, which
contains only the list of directories and file names. All
type unit entries in a \splitDWARFobjectfile{} may (but are not
required to) refer to the same \addtoindex{specialized line number table}.
+\end{itemize}
\item A \DWATuseUTFeight{} attribute, which is a flag
whose presence indicates that all strings referred to by this type
If
\hypertarget{chap:DWATprioritymodulepriority}{}
-the module has been assigned a priority, it may have
+the module has been assigned a priority, it may have a
\addtoindexx{priority attribute}
-a
-\DWATpriority{} attribute.
+\DWATpriorityDEFN{} attribute.
The value of this attribute is a
reference to another debugging information entry describing
a variable with a constant value. The value of this variable
A namespace extension is
\hypertarget{chap:DWATextensionpreviousnamespaceextensionororiginalnamespace}{}
represented by a
-\DWTAGnamespace{} entry
+\DWTAGnamespaceNAME{} entry
with
\addtoindexx{extension attribute}
a
-\DWATextension{}
+\DWATextensionDEFN{}
attribute referring to the previous extension, or if there
is no previous extension, to the original
-\DWTAGnamespace{}
+\DWTAGnamespaceNAME{}
entry. A namespace extension entry does not need to duplicate
information in a previous extension entry of the namespace
nor need it duplicate information in the original namespace
a \DWATname{} attribute
\addtoindexx{name attribute}
need only be attached directly to the original
-\DWTAGnamespace{} entry.)
+\DWTAGnamespaceNAME{} entry.)
\needlines{4}
Namespace and namespace extension entries may own
function definitions.}
A namespace may have a
-\DWATexportsymbolsNAME{}\livetarg{chap:DWATexportsymbolsofnamespace}{}
+\DWATexportsymbolsDEFN{}\livetarg{chap:DWATexportsymbolsofnamespace}{}
attribute\addtoindexx{export symbols attribute}
\addtoindexx{inline namespace|see{\textit{also} export symbols attribute}}
which indicates that all member names defined within the
given another name.
}
-An
-imported declaration is represented by one or
+An imported declaration is represented by one or
\addtoindexx{imported declaration entry}
more debugging information entries with the
tag \DWTAGimporteddeclarationTARG.
each overloading.
\addtoindexx{import attribute}
Each imported declaration entry has a
-\DWATimport{} attribute,
+\DWATimportDEFN{} attribute,
whose value is a \livelink{chap:classreference}{reference} to the
debugging information entry representing the declaration that
is being imported.
an entity, regardless of the context in which the importing
declaration or the imported entity occurs.
-\textit{A \addtoindex{C++} namespace alias may be represented by an imported
+\textit{A \addtoindex{C++} namespace alias may be represented
+by an imported
\hypertarget{chap:DWATimportnamespacealias}{}
declaration entry
\addtoindexx{namespace (C++)!alias}
with a name attribute whose value is
-a null\dash terminated string containing the alias name as it
-appears in the source program and an import attribute whose
-value is a \livelink{chap:classreference}{reference} to the applicable original namespace or
-namespace extension entry.
+a null-terminated string containing the alias name as it
+appears in the source program and a \DWATimportDEFN{} attribute
+whose value is a \livelink{chap:classreference}{reference} to the
+applicable original namespace or namespace extension entry.
}
-\textit{A \addtoindex{C++} using declaration may be represented by one or more
+\textit{A \addtoindex{C++} using declaration may be represented
+by one or more
\hypertarget{chap:DWATimportnamespaceusingdeclaration}{}
imported
\addtoindexx{namespace (C++)!using declaration}
refers to an overloaded function, there is one imported
declaration entry corresponding to each overloading. Each
imported declaration entry has no name attribute but it does
-have an import attribute that refers to the entry for the
+have a \DWATimportDEFN{} attribute that refers to the entry for the
entity being imported. (\addtoindex{C++}
provides no means to \doublequote{rename}
an imported entity, other than a namespace).
\addtoindexx{using directive|see {namespace (C++), using directive}}
may be represented by an imported module
\hypertarget{chap:DWATimportnamespaceusingdirective}{}
-entry, with an import attribute referring to the namespace
+entry, with a \DWATimportDEFN{} attribute referring to the namespace
entry of the appropriate extension of the namespace (which
might be the original namespace entry) and no owned entries.
}
An imported unit entry contains
\addtoindexx{import attribute}
a
-\DWATimport{} attribute
+\DWATimportDEFN{} attribute
whose value is a \livelink{chap:classreference}{reference} to the
normal or partial compilation unit whose declarations logically
belong at the place of the imported unit entry.
compilation unit, that entry has
\addtoindexx{external attribute}
a
-\DWATexternalNAME{} attribute,
+\DWATexternalDEFN{} attribute,
which is a \livelink{chap:classflag}{flag}.
\textit{Additional attributes for functions that are members of a
\hypertarget{chap:DWATmainsubprogrammainorstartingsubprogram}{}
subroutine entry
may contain a
-\DWATmainsubprogramNAME{}
+\DWATmainsubprogramDEFN{}
attribute
\addtoindexx{main subprogram attribute}
which is
A subroutine entry may
\hypertarget{chap:DWATcallingconventionforsubprograms}{}
contain a
-\DWATcallingconventionNAME{}
-\addtoindexx{calling convention attribute}
+\DWATcallingconventionDEFN{}
+\addtoindexx{calling convention attribute!for subprogram}
attribute, whose value is an
\livelink{chap:classconstant}{integer constant}. The set of
\addtoindexi{calling convention codes for subroutines}{calling convention codes!for subroutines}
where functions support recursion by default.
}
-A subprogram entry
+A subprogram entry may have a
\hypertarget{chap:DWATelementalelementalpropertyofasubroutine}{}
-may have
-\addtoindexx{elemental attribute}
-a
-\DWATelementalNAME{} attribute, which
-is a \livelink{chap:classflag}{flag}.
+\DWATelementalDEFN{} attribute,\addtoindexx{elemental attribute}
+which is a \livelink{chap:classflag}{flag}.
The attribute indicates whether the subroutine
or entry point was declared with the \doublequote{elemental} keyword
or property.
subprogram entry may have
\addtoindexx{pure attribute}
a
-\DWATpureNAME{} attribute, which is
+\DWATpureDEFN{} attribute, which is
a \livelink{chap:classflag}{flag}.
The attribute indicates whether the subroutine was
declared with the \doublequote{pure} keyword or property.
A
\hypertarget{chap:DWATrecursiverecursivepropertyofasubroutine}{}
subprogram entry may have a
-\DWATrecursiveNAME{} attribute, which
+\DWATrecursiveDEFN{} attribute, which
is a \livelink{chap:classflag}{flag}.
The attribute indicates whether the subroutine
or entry point was declared with the \doublequote{recursive} keyword
or property.
A subprogram entry may have a
-\DWATnoreturnNAME
+\DWATnoreturnDEFN{}
\livetargi{chap:DWATnoreturnofsubprogram}{ attribute}{noreturn attribute},
which is a \CLASSflag. The attribute
indicates whether the subprogram was declared with the \doublequote{noreturn} keyword or property
the following attributes provide summary information about the calls
that occur within a subprogram.}
-A subroutine entry may have \DWATcallalltailcalls, \DWATcallallcalls{}
-and/or \DWATcallallsourcecalls{} attributes, each of which is a
+A subroutine entry may have \DWATcallalltailcallsNAME,
+\DWATcallallcallsNAME{} and/or \DWATcallallsourcecallsNAME{}
+attributes, each of which is a
\livelink{chap:classflag}{flag}.
\addtoindexx{call site summary information}
\addtoindexx{subroutine call site summary attributes}
-These flags indicate the completeness of the call site information
-provided by call site entries (see
+These flags indicate the completeness of the call site
+information provided by call site entries (see
Section \refersec{chap:callsiteentries}) within the subprogram.
-The \DWATcallalltailcallsNAME{}
+The \DWATcallalltailcallsDEFN{}
\livetargi{chap:DWATcallalltailcallsofasubprogram}{attribute}{all tail calls summary attribute}
indicates that every tail call
that occurs in the code for the subprogram is described by a
(There may or may not be other non-tail calls to some of the same
target subprograms.)
-The \DWATcallallcallsNAME{}
+The \DWATcallallcallsDEFN{}
\livetargi{chap:DWATcallallcallsofasubprogram}{attribute}{all calls summary attribute}
indicates that every non-inlined call
(either a tail call or a normal call) that occurs in the code for the subprogram
is described by a \DWTAGcallsite{} entry.
-The \DWATcallallsourcecallsNAME{}
+The \DWATcallallsourcecallsDEFN{}
\livetargi{chap:DWATcallallsourcecallsofasubprogram}{attribute}{all source calls summary attribute}
indicates that every call that occurs in the
code for the subprogram, including every call inlined into it, is described by either a
is a function that returns a
value, then its debugging information entry has
\addtoindexx{type attribute}
-a \DWATtype{} attribute
+a \DWATtypeDEFN{} attribute
to denote the type returned by that function.
\textit{Debugging information entries for
may also have
\DWATsegment{}
and
-\DWATaddressclass{} attributes,
+\DWATaddressclassDEFN{} attributes,
as appropriate, to specify
which segments the code for the subroutine resides in and
the addressing mode to be used in calling that subroutine.
The
\hypertarget{chap:commonreferencecommonblockusage}{}
common inclusion entry has a
-\DWATcommonreference{} attribute
+\DWATcommonreferenceDEFN{} attribute
+\addtoindexx{common block reference attribute}
whose value is a \livelink{chap:classreference}{reference}
to the debugging information entry
for the common \nolink{block} being included
A
\hypertarget{chap:DWATreturnaddrsubroutinereturnaddresssavelocation}{}
-subroutine or entry point entry may have
+subroutine or entry point entry may have a
\addtoindexx{return address attribute}
-a
-\DWATreturnaddr{}
+\DWATreturnaddrDEFN{}
attribute, whose value is a location description. The location
specified is the place where the return address for the
subroutine or entry point is stored.
subroutine or entry point entry may also have
\addtoindexx{frame base attribute}
a
-\DWATframebase{} attribute, whose value is a location
+\DWATframebaseDEFN{} attribute, whose value is a location
description that describes the \doublequote{frame base} for the
subroutine or entry point. If the location description is
a simple register location description, the given register
\addtoindexx{address!uplevel|see {static link attribute}}
\addtoindexx{uplevel address|see {static link attribute}}
subroutine or entry point is nested, it may have a
-\DWATstaticlink{}
+\DWATstaticlinkDEFN{}
attribute, whose value is a location
description that computes the frame base of the relevant
instance of the subroutine that immediately encloses the
that was expanded inline implicitly by the compiler has
\addtoindexx{inline attribute}
a
-\DWATinline{} attribute whose value is an
+\DWATinlineDEFN{} attribute whose value is an
\livelink{chap:classconstant}{integer constant}. The
set of values for the \DWATinline{} attribute is given in
Table \refersec{tab:inlinecodes}.
\centering
\caption{Inline codes}
\label{tab:inlinecodes}
-\begin{tabular}{l|p{8cm}}
+\begin{tabular}{l|P{8cm}}
\hline
Name&Meaning\\ \hline
\DWINLnotinlinedTARG{} & Not declared inline nor inlined by the
\subsubsection{Abstract Instances}
\label{chap:abstractinstances}
Any subroutine entry that contains a
-\DWATinline{} attribute\addtoindexx{inline attribute}
+\DWATinlineDEFN{} attribute\addtoindexx{inline attribute}
whose value is other than
\DWINLnotinlined{}
is known as an
\hypertarget{chap:DWATcallcolumncolumnpositionofinlinedsubroutinecall}{}
entry
\hypertarget{chap:DWATcallfilefilecontaininginlinedsubroutinecall}{}
-may also have \DWATcallfile,
-\DWATcallline{} and \DWATcallcolumn{} attributes,
+may also have \DWATcallfileDEFN,
+\DWATcalllineDEFN{} and \DWATcallcolumnDEFN{} attributes,
+\addtoindexx{inlined call location attributes}
each of whose
value is an \livelink{chap:classconstant}{integer constant}.
These attributes represent the
An inlined subroutine entry
\hypertarget{chap:DWATconstexprcompiletimeconstantfunction}{}
may have a
-\DWATconstexpr{}
-attribute, which is a \livelink{chap:classflag}{flag}
+\DWATconstexprDEFN{} attribute,\addtoindexx{constant expression attribute}
+which is a \livelink{chap:classflag}{flag}
whose presence indicates that the
subroutine has been evaluated as a compile\dash time constant. Such
an entry may also have a \DWATconstvalue{} attribute,
concrete inlined instance entry
\addtoindexx{abstract origin attribute}
has a
-\DWATabstractorigin{}
+\DWATabstractoriginDEFN{}
attribute that may be used to obtain the missing information
(indirectly) from the associated abstract instance entry. The
value of the abstract origin attribute is a reference to the
to be inline can necessitate the generation of a concrete
out\dash of\dash line instance of the given function.}
-The DWARF representation of a concrete out\dash of\dash line instance
+The DWARF representation of a concrete out-of-line instance
of an inlined subroutine is essentially the same as for a
concrete inlined instance of that subroutine (as described in
the preceding section). The representation of such a concrete
% It is critical that the hypertarget and livelink be
% separated to avoid problems with latex.
-out\dash of\dash line
+out-of-line
\addtoindexx{abstract origin attribute}
instance
\hypertarget{chap:DWATabstractoriginoutoflineinstance}{}
makes use of
-\DWATabstractorigin{}
+\DWATabstractoriginDEFN{}
attributes in exactly the same way as they are used for
a concrete inlined instance (that is, as references to
corresponding entries within the associated abstract instance
with the tag \DWTAGsubprogram{} or \DWTAGinlinedsubroutine{}
that has
\addtoindexx{trampoline attribute}
-a \DWATtrampoline{} attribute.
+a \DWATtrampolineDEFN{} attribute.
The value of that
attribute indicates the target subroutine of the trampoline,
that is, the subroutine to which the trampoline passes
(see Section \refersec{chap:inlinedsubroutines}).
The call site entry has a
-\DWATcallreturnpcNAME{}
+\DWATcallreturnpcDEFN{}
\livetargi{chap:DWATcallreturnpcofcallsite}{attribute}{call return pc attribute}
which is the return address after the call.
The value of this attribute corresponds to the return address computed by
be an address after the delay slot of the call.}
The call site entry may have a
-\DWATcallpcNAME{}
+\DWATcallpcDEFN{}
\livetargi{chap:DWATcallpcofcallsite}{attribute}{call pc attribute} which is the
address of the call instruction.
If the call site entry corresponds to a tail call, it has the
-\DWATcalltailcallNAME{}
+\DWATcalltailcallDEFN{}
\livetargi{chap:DWATcalltailcallofcallsite}{attribute}{call tail call attribute},
which is a \CLASSflag.
The call site entry may have a
-\DWATcalloriginNAME{}
+\DWATcalloriginDEFN{}
\livetargi{chap:DWATcalloriginofcallsite}{attribute}{call origin attribute}
which is a \CLASSreference. For direct calls or jumps where the called subprogram is
known it is a reference to the called subprogram's debugging
\needlines{4}
The call site may have a
-\DWATcalltargetNAME{}
+\DWATcalltargetDEFN{}
\livetargi{chap:DWATcalltargetofcallsite}{attribute}{call target attribute} which is
a DWARF expression. For indirect calls or jumps where it is unknown at
compile time which subprogram will be called the expression computes the
\needlines{4}
The call site entry may have a
-\DWATcalltargetclobberedNAME{}
+\DWATcalltargetclobberedDEFN{}
\livetargi{chap:DWATcalltargetclobberedofcallsite}{attribute}{call target clobbered attribute}
which is a DWARF expression. For indirect calls or jumps where the
address is not computable without use of registers or memory locations that
might be clobbered by the call the \DWATcalltargetclobberedNAME{}
attribute is used instead of the \DWATcalltarget{} attribute.
-The call site entry may have a \DWATtypeNAME{}
+The call site entry may have a \DWATtypeDEFN{}
\livetargi{chap:DWATtypeofcallsite}{attribute}{type attribute!of call site entry}
referencing a debugging information entry for the type of the called function.
contents of the stack register plus some offset).
Each \DWTAGcallsiteparameter{} entry may have a
-\DWATcallvalueNAME{}
+\DWATcallvalueDEFN{}
\livetargi{chap:DWATcallvalueofcallparameter}{attribute}{call value attribute}
which is a DWARF expression. This expression computes the value
passed for that parameter. The expression should not use registers or memory
whose value is a location expression and a
\DWATcalldatavalueNAME{}
\livetargi{chap:DWATcalldatavalueofcallparameter}{attribute}{call data value attribute}
-whose value is a DWARF expression. The \DWATcalldatalocationNAME{} attribute
+whose value is a DWARF expression. The \DWATcalldatalocationDEFN{} attribute
+\addtoindexx{call data location attribute}
describes where the referenced value lives during the call. If it is just
\DWOPpushobjectaddress{}, it may be left out. The
-\DWATcalldatavalueNAME{} attribute describes the value in that location.
+\DWATcalldatavalueNAME{} attribute\addtoindexx{call data value attribute}
+describes the value in that location.
The expression should not use registers or memory
locations that might be clobbered by the call, as it might be evaluated after
unwinding from the called function back to the caller.
\needlines{4}
Each call site parameter entry may also have a
-\DWATcallparameter{}
+\DWATcallparameterDEFN{}
\livetargi{chap:DWATcallparameterofcallparameter}{attribute}{call parameter attribute}
which contains a reference to a \DWTAGformalparameter{} entry,
\DWATtype{} attribute referencing the type of the parameter or \DWATname{}
\begin{figure}[H]
\begin{center}
-\footnotesize
+\small
+%\footnotesize
\begin{tabular}{cl|cl}
Slot & String & Slot & String \\
\hline
\end{figure}
Each entry in the table is the offset of the string, which is
-contained in the \dotdebugstrdwo{} section. In a split DWARF
-object file, these offsets have no relocations, since they
-are not part of the relocatable object file. When combined into a
-DWARF package file, however, each slot must be adjusted to
-refer to the appropriate offset within the merged string table.
+contained in the \dotdebugstrdwo{} section.
+
+In a split DWARF object file, all references to
+strings go through this table (there are no
+other offsets to \dotdebugstrdwo{} in a split
+DWARF object file). That is, there
+is no use of \DWFORMstrp{} in a split DWARF object file.
+
+The offsets in these slots have no associated relocations,
+because they are not part of a relocatable object file.
+
+When combined into a DWARF package file, however, each
+slot must be adjusted to refer to the appropriate offset
+within the merged string table (\dotdebugstrdwo{}).
The tool that builds the DWARF package file must understand
-the structure of the section in order to apply the necessary
-adjustments. (See Section \refersec{app:dwarfpackagefileexample}
+the structure of the \dotdebugstroffsetsdwo{} section in
+order to apply the necessary adjustments.
+(See Section \refersec{app:dwarfpackagefileexample}
for an example of a DWARF package file.)
\needlines{4}
\hypertarget{chap:DWATstartscopetypedeclaration}{}
the low PC value for the scope most closely enclosing the
declaration, the declaration may have a
-\DWATstartscope{}
+\DWATstartscopeDEFN{}
attribute as described for objects in
Section \refersec{chap:dataobjectentries}.
If the value of an object of the given type does not fully
occupy the storage described by a byte size attribute,
\hypertarget{chap:DWATdatabitoffsetbasetypebitlocation}{}
-the base type entry may also have
+the base type entry may also have a
+\DWATbitsizeDEFN{} and a \DWATdatabitoffsetDEFN{} attribute,
\addtoindexx{bit size attribute}
-a
-\DWATbitsize{} and a
-\DWATdatabitoffset{} attribute,
-both
\addtoindexx{data bit offset attribute}
-of whose values are
+both of whose values are
\livelink{chap:classconstant}{integer constant} values
(see Section \refersec{chap:staticanddynamicvaluesofattributes}).
The bit size
\caption{Encoding attribute values}
\label{tab:encodingattributevalues}
\centering
-\begin{tabular}{l|p{8cm}}
+\begin{tabular}{l|P{8cm}}
\hline
\bfseries Name & \bfseries Meaning\\ \hline
\hypertarget{chap:DWATbinaryscalebinaryscalefactorforfixedpointtype}{}
For a data type with a binary scale factor, the fixed
-binary type entry has a \DWATbinaryscale{} attribute.
-The \DWATbinaryscale{} attribute\addtoindexx{binary scale attribute}
+binary type entry has a \DWATbinaryscaleNAME{} attribute.
+The \DWATbinaryscaleDEFN{} attribute\addtoindexx{binary scale attribute}
is an \livelink{chap:classconstant}{integer constant} value
that represents the exponent of the base two scale factor to
be applied to an instance of the type. Zero scale puts the
For
\hypertarget{chap:DWATsmallscalefactorforfixedpointtype}{}
a data type with a non-decimal and non-binary scale factor,
-the fixed binary type entry has a \DWATsmall{} attribute which
+the fixed binary type entry has a \DWATsmallDEFN{} attribute which
\addtoindexx{small attribute} references a
\DWTAGconstant{} entry. The scale factor value
is interpreted in accordance with the value defined by the
\subsubsection{Decimal String Encodings}
\label{chap:decimalstringencodings}
-The \DWATEpackeddecimal{} and \DWATEnumericstring{}
+The \DWATEpackeddecimalDEFN{} and \DWATEnumericstringDEFN{}
base type encodings
represent packed and unpacked decimal string numeric data
types, respectively, either of which may be either
\addtoindexx{decimal sign attribute}
or
\addtoindexx{digit count attribute}
-unsigned.
-\hypertarget{chap:DWATdecimalsigndecimalsignrepresentation}{}
-These
-\hypertarget{chap:DWATdigitcountdigitcountforpackeddecimalornumericstringtype}{}
+unsigned. These
base types are used in combination with
\DWATdecimalsign,
\DWATdigitcount{} and
attributes.
\needlines{5}
-A \DWATdecimalsign{} attribute
+\hypertarget{chap:DWATdecimalsigndecimalsignrepresentation}{}
+A \DWATdecimalsignDEFN{} attribute
\addtoindexx{decimal sign attribute}
is an \livelink{chap:classconstant}{integer constant} that
conveys the representation of the sign of the decimal type
\caption{Decimal sign attribute values}
\label{tab:decimalsignattributevalues}
\centering
-\begin{tabular}{l|p{9cm}}
+\begin{tabular}{l|P{9cm}}
\hline
Name & Meaning \\
\hline
\needlines{4}
\hypertarget{chap:DWATdecimalscaledecimalscalefactor}{}
-The \DWATdecimalscale{}
+The \DWATdecimalscaleDEFN{}
attribute
\addtoindexx{decimal scale attribute}
is an integer constant value
is larger than the digit count, this implies additional zero
digits on the left are not stored in an instance of the type.
-The \DWATdigitcount{} attribute
+The \DWATdigitcountDEFN{} attribute
\addtoindexx{digit count attribute}
+\hypertarget{chap:DWATdigitcountdigitcountforpackeddecimalornumericstringtype}{}
is an \livelink{chap:classconstant}{integer constant}
value that represents the number of digits in an instance of
the type.
\hypertarget{chap:DWATpicturestringpicturestringfornumericstringtype}{}
type is used to represent an edited
numeric or alphanumeric data type. It is used in combination
-with a \DWATpicturestring{} attribute whose value is a
+with a \DWATpicturestringDEFN{} attribute whose value is a
null\dash terminated string containing the target\dash dependent picture
string associated with the type.
have
\hypertarget{chap:DWATadressclasspointerorreferencetypes}{}
a
-\DWATaddressclass{}
+\DWATaddressclassDEFN{}
attribute to describe how objects having the given pointer
or reference type ought to be dereferenced.
\caption{Type modifier tags}
\label{tab:typemodifiertags}
\centering
-\begin{tabular}{l|p{9cm}}
+\begin{tabular}{l|P{9cm}}
\hline
Name&Meaning\\ \hline
\DWTAGatomictypeTARG{} & C \addtoindex{\_Atomic} qualified type \\
\hypertarget{chap:DWATorderingarrayrowcolumnordering}{}
array type entry describing a multidimensional array may
\addtoindexx{array!element ordering}
-have a \DWATordering{} attribute whose
+have a \DWATorderingDEFN{} attribute whose
\livelink{chap:classconstant}{integer constant} value is
interpreted to mean either row-major or column-major ordering
of array elements. The set of values and their meanings
indicated element type, then the array type
\addtoindexx{bit stride attribute}
entry has either a
-\DWATbytestride{}
+\DWATbytestrideDEFN{}
or
\addtoindexx{byte stride attribute}
-a \DWATbitstride{}
+a \DWATbitstrideDEFN{}
attribute,
\addtoindexx{bit stride attribute}
whose value
and appear in the same order as the corresponding declarations
in the source program.
-A structure, union, or class type may have a \DWATexportsymbolsNAME{}
-attribute
+A structure, union, or class type may have a \DWATexportsymbolsDEFN{}
+attribute\addtoindexx{export symbols (of structure, class or union) attribute}
\livetarg{chap:DWATexportsymbolsofstructunionclass}{}
which indicates that all member names defined within
the structure, union, or class may be referenced as if they were
an incomplete declaration
\addtoindexx{incomplete type}
of that type in the compilation unit may provide
-the unique 64-bit signature of the type using
+the unique 64-bit signature of the type using a
\addtoindexx{type signature}
-a \DWATsignature{}
-attribute.
+\DWATsignatureDEFN{} attribute.
If a structure, union or class entry represents the definition
of a structure, union or class member corresponding to a prior
\needlines{4}
A structure type, union type or class type entry may have a
-\DWATcallingconvention{} attribute,
-\addtoindexx{calling convention attribute}
+\DWATcallingconventionDEFN{} attribute,
+\addtoindexx{calling convention attribute!for types}
whose value indicates whether a value of the type should be passed by reference
or passed by value. The set of calling convention codes for use with types
\addtoindexx{calling convention codes!for types}
\addtoindexx{inheritance entry}
for a class that derives from or extends
\hypertarget{chap:DWATdatamemberlocationinheritedmemberlocation}{}
-another class or struct also has
+another class or struct also has a
+\DWATdatamemberlocationDEFN{} attribute,
\addtoindexx{data member location attribute}
-a
-\DWATdatamemberlocation{}
-attribute, whose value describes the location of the beginning
+whose value describes the location of the beginning
of the inherited type relative to the beginning address of the
instance of the derived class. If that value is a constant, it is the offset
in bytes from the beginning of the class to the beginning of
may
\addtoindexx{accessibility attribute}
have a
-\DWATaccessibility{}
+\DWATaccessibilityDEFN{}
attribute.
If no accessibility attribute is present, private access
is assumed for an entry of a class and public access is
\addtoindexx{inheritance entry}
inheritance entry serves
as a \addtoindex{C++} virtual base class, the inheritance entry has a
-\DWATvirtuality{} attribute.
+\DWATvirtualityDEFN{} attribute.
\textit{For a \addtoindex{C++} virtual base, the
\addtoindex{data member location attribute}
\hypertarget{chap:DWATaccessibilitycppbaseclasses}{}
also
has a
-\DWATaccessibility{}
+\DWATaccessibilityDEFN{}
attribute describing the declared accessibility of the named
entities.
that is a child of the structure, union or class type entry;
the friend entry has the tag \DWTAGfriendTARG.
-A friend entry has a \DWATfriendNAME{} attribute,
+A friend entry has a \DWATfriendDEFN{} attribute,
\addtoindexx{friend attribute} whose value is
a reference to the debugging information entry describing
the declaration of the friend.
\addtoindexx{member entry (data)}
may
\addtoindexx{mutable attribute}
-have a \DWATmutable{} attribute,
+have a \DWATmutableDEFN{} attribute,
which is a \livelink{chap:classflag}{flag}.
This attribute indicates whether the data
member was declared with the mutable storage class specifier.
The member entry
\addtoindexx{member entry (data)}
-corresponding to a data member that is
+corresponding to a data member that is defined
\hypertarget{chap:DWATdatabitoffsetdatamemberbitlocation}{}
-defined
\hypertarget{chap:DWATdatamemberlocationdatamemberlocation}{}
-in a structure, union or class may have either
+in a structure, union or class may have either a
+\DWATdatamemberlocationDEFN{} attribute
\addtoindexx{data member location attribute}
-a
-\DWATdatamemberlocation{} attribute or a
-\DWATdatabitoffset{}
-attribute. If the beginning of the data member is the same as
+or a \DWATdatabitoffsetDEFN{} attribute.
+\addtoindexx{data bit offset attribute}
+If the beginning of the data member is the same as
the beginning of the containing entity then neither attribute
is required.
\addtoindexx{data member location attribute}
there are two cases:
\begin{enumerate}[1. ]
-\item If the value is an \livelink{chap:classconstant}{integer constant},
+\item If the value is an
+\livelink{chap:classconstant}{integer constant},
it is the offset
in bytes from the beginning of the containing entity. If
the beginning of the containing entity has a non-zero bit
\hypertarget{chap:DWATvirtualityvirtualityoffunction}{}
the member function entry describes a virtual function,
then that entry has a
-\DWATvirtuality{} attribute.
+\DWATvirtualityDEFN{} attribute.
If
\hypertarget{chap:DWATexplicitexplicitpropertyofmemberfunction}{}
function, then that entry has
\addtoindexx{explicit attribute}
a
-\DWATexplicit{} attribute.
+\DWATexplicitDEFN{} attribute.
An
\hypertarget{chap:DWATvtableelemlocationvirtualfunctiontablevtableslot}{}
entry for a virtual function also has a
-\DWATvtableelemlocation{}
+\DWATvtableelemlocationDEFN{}
\addtoindexi{attribute}{vtable element location attribute} whose value contains
a \addtoindex{location description}
yielding the address of the slot
\addtoindexx{self pointer attribute|see{object pointer attribute}}
has
\addtoindexx{object pointer attribute}
-a \DWATobjectpointer{}
-attribute
+a \DWATobjectpointerDEFN{} attribute
whose value is a \livelink{chap:classreference}{reference}
to the formal parameter entry
that corresponds to the object for which the function is
object values on which the function can be invoked.}
\needlines{6}
-The member function entry may have an \DWATreferenceNAME{} attribute
+The member function entry may have an \DWATreferenceDEFN{} attribute
\livetarg{chap:DWATreferenceofnonstaticmember}{}
to indicate a non-static member function that can only be called on
-lvalue objects, or the \DWATrvaluereferenceNAME{} attribute
+lvalue objects, or the \DWATrvaluereferenceDEFN{} attribute
\livetarg{chap:DWATrvaluereferenceofnonstaticmember}{}
to indicate that it can only be called on prvalues and xvalues.
when used on other member functions.}
If the member function entry has been declared as deleted,
-then that entry has a \DWATdeletedNAME{}\livetarg{chap:DWATdeleteddef}{}
+then that entry has a \DWATdeletedDEFN{}\livetarg{chap:DWATdeleteddef}{}
attribute.\addtoindexx{deleted attribute}
\textit{In \addtoindex{C++}, a special member function may be
class.}
If the member function has been declared as defaulted,
-then the entry has a \DWATdefaultedNAME{}\livetarg{chap:DWATdefaulteddef}{}
+then the entry has a \DWATdefaultedDEFN{}\livetarg{chap:DWATdefaulteddef}{}
attribute\addtoindexx{defaulted attribute}
whose integer constant value indicates whether, and if so,
how, that member is defaulted. The possible values and
of a
\addtoindexx{member entry (data)!as discriminant}
structure data member entry. The variant part entry will
-\addtoindexx{discriminant attribute}
have a
-\DWATdiscr{} attribute
+\DWATdiscrDEFN{} attribute \addtoindexx{discriminant attribute}
whose value is a \livelink{chap:classreference}{reference} to
the member entry for the discriminant.
tag \DWTAGvariantTARG{}
and is a child of the variant part entry. The value that
selects a given variant may be represented in one of three
-ways. The variant entry may have a \DWATdiscrvalue{} attribute
+ways. The variant entry may have a \DWATdiscrvalueDEFN{}
+attribute\addtoindexx{discriminant value attribute}
whose value represents the discriminant value selecting
this variant. The value of this
attribute is encoded as an LEB128 number. The number is signed
\hypertarget{chap:DWATdiscrlistlistofdiscriminantvalues}{}
the variant entry may contain
\addtoindexx{discriminant list attribute}
-a \DWATdiscrlist{}
+a \DWATdiscrlistDEFN{}
attribute, whose value represents a list of discriminant
values. This list is represented by any of the
\livelink{chap:classblock}{block} forms and may contain a
then the \addtoindex{enumeration type entry} may
\addtoindexx{enum class|see{type-safe enumeration}}
-have a \DWATenumclass{}
+have a \DWATenumclassDEFN{}
attribute, which is a \livelink{chap:classflag}{flag}.
In a language that offers only
one kind of enumeration declaration, this attribute is not
\needlines{4}
Each \addtoindex{enumerator entry} has a \DWATname{} attribute, whose
\addtoindexx{name attribute}
-value is a null\dash terminated string containing the name of the
+value is a null-terminated string containing the name of the
\hypertarget{chap:DWATconstvalueenumerationliteralvalue}{}
enumeration literal as it appears in the source program.
Each enumerator entry also has a
-\DWATconstvalue{} attribute,
+\DWATconstvalueDEFN{} attribute,
+\addtoindexx{constant value attribute}
whose value is the actual numeric value of the enumerator as
represented on the target system.
is different than what would otherwise be determined, then
\hypertarget{chap:DWATbitstrideenumerationstridedimensionofarraytype}{}
the enumeration type entry has either a
-\DWATbytestride{}
-or \DWATbitstride{} attribute
+\DWATbytestrideDEFN{}
+or \DWATbitstrideDEFN{} attribute
\addtoindexx{bit stride attribute}
which specifies the separation
between successive elements along the dimension as described
declaration may have
\addtoindexx{prototyped attribute}
a
-\DWATprototyped{} attribute, which is
+\DWATprototypedDEFN{} attribute, which is
a \livelink{chap:classflag}{flag}.
\needlines{4}
a null\dash terminated string containing the string type name as
it appears in the source program.
-A string type entry may have a \DWATtype{}
+A string type entry may have a \DWATtypeDEFN{}
\livetargi{char:DWAATtypeofstringtype}{attribute}{type attribute!of string type entry}
describing how each character is encoded and is to be interpreted.
The value of this attribute is a \CLASSreference{} to a
The
\hypertarget{chap:DWATstringlengthstringlengthofstringtype}{}
string type entry may also have a
-\DWATstringlength{} attribute
+\DWATstringlengthDEFN{} attribute
whose
\addtoindexx{string length attribute}
value is a
\addtoindex{location description} yielding the location
where the length of the string is stored in the program.
-If the \DWATstringlength{} attribute is not present, the size
+If the \DWATstringlengthNAME{} attribute is not present, the size
of the string is assumed to be the amount of storage that is
allocated for the string (as specified by the \DWATbytesize{}
or \DWATbitsize{} attribute).
The string type entry may also have a
-\DWATstringlengthbytesizeNAME{} or
-\DWATstringlengthbitsizeNAME{} attribute,
+\DWATstringlengthbytesizeDEFN{} or
+\DWATstringlengthbitsizeDEFN{} attribute,
\addtoindexx{string length size attribute}
\addtoindexx{string length attribute!size of length data}
whose value (see Section \refersec{chap:byteandbitsizes})
The
\hypertarget{chap:DWATthreadsscaledupcarrayboundthreadsscalfactor}{}
subrange entry may have a
-\DWATthreadsscaled{} attribute\addtoindexx{threads scaled attribute},
+\DWATthreadsscaledDEFN{} attribute\addtoindexx{threads scaled attribute},
which is a \livelink{chap:classflag}{flag}.
If present, this attribute indicates whether
this subrange represents a \addtoindex{UPC} array bound which is scaled
subrange
\hypertarget{chap:DWATupperboundupperboundofsubrange}{}
entry may have the attributes
-\DWATlowerbound{}
+\DWATlowerboundDEFN{}
\addtoindexx{lower bound attribute}
-and \DWATupperbound{}
+and \DWATupperboundDEFN{}
\addtoindexx{upper bound attribute} to specify, respectively, the lower
and upper bound values of the subrange. The
-\DWATupperbound{}
-attribute
+\DWATupperboundNAME{} attribute
\hypertarget{chap:DWATcountelementsofsubrangetype}{}
-may
-% FIXME: The following matches DWARF4: odd as there is no default count.
+may be replaced by a
\addtoindexx{count attribute!default}
-be
\addtoindexx{count attribute}
-replaced by a
-\DWATcount{} attribute,
-whose
-value describes the number of elements in the subrange rather
-than the value of the last element. The value of each of
-these attributes is determined as described in
+\DWATcountDEFN{} attribute,
+whose value describes the number of elements in the subrange
+rather than the value of the last element. The value of each
+of these attributes is determined as described in
Section \refersec{chap:staticanddynamicvaluesofattributes}.
If the lower bound value is missing, the value is assumed to
-be a language\dash dependent default constant as defined in
+be a language-dependent default constant as defined in
Table \refersec{tab:languageencodings}.
\addtoindexx{lower bound attribute!default}
the subrange type entry has either
\addtoindexx{byte stride attribute}
a
-\DWATbytestride{} or
-\DWATbitstride{} attribute
+\DWATbytestrideDEFN{} or
+\DWATbitstrideDEFN{} attribute
\addtoindexx{bit stride attribute}
which specifies the separation
-between successive elements along the dimension as described
-in
+between successive elements along the dimension as described in
Section \refersec{chap:byteandbitsizes}.
\textit{Note that the stride can be negative.}
The \addtoindexx{pointer to member} entry also
\hypertarget{chap:DWATcontainingtypecontainingtypeofpointertomembertype}{}
-has a
-\DWATcontainingtype{}
-attribute, whose value is a \livelink{chap:classreference}{reference} to a debugging
+has a \DWATcontainingtypeDEFN{} attribute,
+\addtoindexx{containing type (of pointer) attribute}
+whose value is a \livelink{chap:classreference}{reference} to a debugging
information entry for the class or structure to whose members
objects of this type may point.
The \addtoindex{pointer to member entry}
\hypertarget{chap:DWATuselocationmemberlocationforpointertomembertype}{}
has a
-\DWATuselocation{} attribute
+\DWATuselocationDEFN{} attribute
\addtoindexx{use location attribute}
whose value is a
\addtoindex{location description} that computes the
about the data that represents the value for that object.}
\hypertarget{chap:DWATdatalocationindirectiontoactualdata}{}
-The \DWATdatalocation{}
-attribute may be used with any
-\addtoindexx{data location attribute}
-type that provides one or more levels of
+The \DWATdatalocationDEFN{} attribute
+\addtoindexx{data (indirect) location attribute}
+may be used with any type that provides one or more levels of
\addtoindexx{hidden indirection|see{data location attribute}}
hidden indirection
-and/or run\dash time parameters in its representation. Its value
+and/or run-time parameters in its representation. Its value
is a \addtoindex{location description}.
The result of evaluating this
description yields the location of the data for an object.
under explicit program control.}
\hypertarget{chap:DWATallocatedallocationstatusoftypes}{}
-The \DWATallocated{} attribute\addtoindexx{allocated attribute}
+The \DWATallocatedDEFN{} attribute\addtoindexx{allocated attribute}
may be used with any
type for which objects of the type can be explicitly allocated
and deallocated. The presence of the attribute indicates that
\needlines{4}
\hypertarget{chap:DWATassociatedassociationstatusoftypes}{}
The
-\DWATassociated{} attribute
+\DWATassociatedDEFN{} attribute
may
\addtoindexx{associated attribute}
optionally be used with
\hypertarget{chap:DWATrankofdynamicarray}{\DWATrankINDX}
attribute indicates that an array's rank
(number of dimensions) is dynamic, and therefore unknown at compile
-time. The value of the \DWATrankNAME{} attribute is either an integer constant
+time. The value of the \DWATrankDEFN{} attribute is either an integer constant
or a DWARF expression whose evaluation yields the dynamic rank.
The bounds of an array with dynamic rank are described using a
DWARF Git Projects / dwarf-doc.git / commitdiff