replaces with latex commands to do the same job.
All the following had utf-8 in them till now.
Which came from the DWARF4 pdf creation process.
compression.tex datarepresentation.tex examples.tex
foreword4.1.tex generaldescription.tex gnulicense.tex
otherdebugginginformation.tex programscope.tex typeentries.tex
B.o apply to the remaining one of the two identical section
groups. This saves space.
-An important part of making it possible to “redirect”
+An important part of making it possible to \doublequote{redirect}
references to the surviving
\addtoindex{section group} is the use of
consistently chosen linker global symbols for referring to
\end{figure}
Next, consider one possible representation of the DWARF
-information that describes the type “struct C” as shown
+information that describes the type \doublequote{struct C} as shown
in
\refersec{fig:typesignaturecomputation1dwarfrepresentation}:
shared objects position independent. Virtual addresses in a
shared object may be calculated by adding the offset to the
base address at which the object was attached. This offset
-is available in the run\dash time linker’s data structures.}
+is available in the run\dash time linker\textquoteright s data structures.}
section. As described above, the abbreviation
code 0 is reserved for null debugging information entries. The
abbreviation code is followed by another unsigned LEB128
-number that encodes the entry’s tag. The encodings for the
+number that encodes the entry\textquoteright s tag. The encodings for the
tag names are given in
Table \refersec{tab:tagencodings}.
the next physically succeeding entry of any debugging
information entry using this abbreviation is the first
child of that entry. If the 1\dash byte value following the
-abbreviation’s tag encoding is
+abbreviation\textquoteright s tag encoding is
\livetarg{chap:DWCHILDRENno}{DW\-\_CHILDREN\-\_no}, the next
physically succeeding entry of any debugging information entry
using this abbreviation is a sibling of that entry. (Either
Finally, the child encoding is followed by a series of
attribute specifications. Each attribute specification
consists of two parts. The first part is an unsigned LEB128
-number representing the attribute’s name. The second part
-is an unsigned LEB128 number representing the attribute’s
+number representing the attribute\textquoteright s name. The second part
+is an unsigned LEB128 number representing the attribute\textquoteright s
form. The series of attribute specifications ends with an
entry containing 0 for the name and 0 for the form.
\textit{For a reference from one executable or shared object to
another, the reference is resolved by the debugger to identify
the shared object or executable and the offset into that
-object’s \addtoindex{.debug\_info}
+object\textquoteright s \addtoindex{.debug\_info}
section in the same fashion as the run
time loader, either when the debug information is first read,
or when the reference is used.}
that an additional byte follows.
-The encoding for signed, two’s complement LEB128 (SLEB128)
+The encoding for signed, two\textquoteright s complement LEB128 (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
\item If the debugging information entry represents a type that
is nested inside another type or a namespace, append to S
-the type’s context as follows: For each surrounding type
+the type\textquoteright s context as follows: For each surrounding type
or namespace, beginning with the outermost such construct,
append the letter 'C', the DWARF tag of the construct, and
the name (taken from
\vspace{0.01cm}
\hrule
2
-“char”
+\doublequote{char}
\livelink{chap:DWATEunsignedchar}{DW\-\_ATE\-\_unsigned\-\_char}
1
\vspace{0.01cm}
\vspace{0.01cm}
\hrule
4
-“POINTER”
+\doublequote{POINTER}
e2
\vspace{0.01cm}
\hrule
\vspace{0.01cm}
\hrule
4
-“strp”
+\doublequote{strp}
e2
\vspace{0.01cm}
\hrule
\end{figure}
-In practice, of course, a “real” descriptor will have
+In practice, of course, a \doublequote{real} descriptor will have
dimension substructures only for as many dimensions as are
specified in the num\_dims component. Let us use the notation
\texttt{desc\textless n\textgreater}
Because the arrays considered here come in two parts, it is
necessary to distinguish the parts carefully. In particular,
-the “address of the variable” or equivalently, the “base
-address of the object” \emph{always} refers to the descriptor. For
+the \doublequote{address of the variable} or equivalently, the \doublequote{base
+address of the object} \emph{always} refers to the descriptor. For
arrays that do not come in two parts, an implementation can
provide a descriptor anyway, thereby giving it two parts. (This
may be convenient for general runtime support unrelated to
debugging.) In this case the above vocabulary applies as
stated. Alternatively, an implementation can do without a
-descriptor, in which case the “address of the variable”,
-or equivalently the “base address of the object”, refers
-to the “raw data” (the real data, the only thing around
+descriptor, in which case the \doublequote{address of the variable},
+or equivalently the \doublequote{base address of the object}, refers
+to the \doublequote{raw data} (the real data, the only thing around
that can be the object).
If an object has a descriptor, then the DWARF type for that
\item the lower bounds of the array \\
% Using plain [] here gives trouble.
\lbrack To check that 2 is within bounds we would require the upper
-%bound too, but we’ll skip that for this example \rbrack
+%bound too, but we\textquoteright ll skip that for this example \rbrack
\item the stride
\livelink{chap:DWATupperbound}{DW\-\_AT\-\_upper\-\_bound}(reference to member N at 27\$)
30\$: \livelink{chap:DWTAGmember}{DW\-\_TAG\-\_member}
\livelink{chap:DWATname}{DW\-\_AT\-\_name}("VEC2")
- \livelink{chap:DWATtype}{DW\-\_AT\-\_type}(reference to array “subtype” at 28\$)
+ \livelink{chap:DWATtype}{DW\-\_AT\-\_type}(reference to array \doublequote{subtype} at 28\$)
\livelink{chap:DWATdatamemberlocation}{DW\-\_AT\-\_data\-\_member\-\_location}(machine=
\livelink{chap:DWOPlit}{DW\-\_OP\-\_lit}<n> ! where n == offset(REC2, VEC2)
\livelink{chap:DWOPplus}{DW\-\_OP\-\_plus})
namespace B {
int j;
int myfunc (int a);
- float myfunc (float f) { return f – 2.0; }
+ float myfunc (float f) { return f \textendash 2.0; }
int myfunc2(int a) { return a + 2; }
}
}
in that INNER lacks a
\livelink{chap:DWATinline}{DW\-\_AT\-\_inline} attribute
and therefore is not a distinct abstract instance. INNER
-is merely an out\dash of\dash line routine that is part of OUTER’s
+is merely an out\dash of\dash line routine that is part of OUTER\textquoteright s
abstract instance. This is reflected in the Figure by
\addtoindexx{abstract instance!example}
the fact that the labels for INNER use the substring OUTER
The most distinctive aspect of that Figure is that subprogram
INNER exists only within the abstract instance of OUTER,
-and not in OUTER’s concrete instance. In the abstract
+and not in OUTER\textquoteright s concrete instance. In the abstract
\addtoindexx{concrete instance!example}
\addtoindexx{abstract instance!example}
instance of OUTER, the description of INNER has the full
\end{dwflisting}
\caption{C++ template alias example \#2: DWARF description}
\label{fig:ctemplatealiasexample2dwarf}
-\end{figure}
\ No newline at end of file
+\end{figure}
If any substantive descrepancies are discovered between these two documents,
please bring them to the attention of the DWARF Information Format Committee.
-\end{abstract}
\ No newline at end of file
+\end{abstract}
\textit{%
A variety of needs can be met by permitting a single
\addtoindexx{debugging information entry!ownership relation}
-debugging information entry to “own” an arbitrary number
+debugging information entry to \doublequote{own} an arbitrary number
of other debugging entries and by permitting the same debugging
information entry to be one of many owned by another debugging
information entry.
The \livelink{chap:DWOPfbreg}{DW\-\_OP\-\_fbreg} operation provides a signed LEB128 offset
from the address specified by the location description in the
\livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} attribute of the current function. (This
-is typically a “stack pointer” register plus or minus
+is typically a \doublequote{stack pointer} register plus or minus
some offset. On more sophisticated systems it might be a
location list that adjusts the offset according to changes
in the stack pointer as the PC changes.)
provide consumers a way to find
the location of program variables, determine the bounds
of dynamic arrays and strings, and possibly to find the
-base address of a subroutine’s stack frame or the return
+base address of a subroutine\textquoteright s stack frame or the return
address of a subroutine. Furthermore, to meet the needs of
recent computer architectures and optimization techniques,
debugging information must be able to describe the location of
-an object whose location changes over the object’s lifetime.}
+an object whose location changes over the object\textquoteright s lifetime.}
Information about the location of program objects is provided
by location descriptions. Location descriptions can be either
Interpretation of the
offset depends on the kind of location description. If the
-location description is empty, the offset doesn’t matter and
+location description is empty, the offset doesn\textquoteright t matter and
the \livelink{chap:DWOPbitpiece}{DW\-\_OP\-\_bit\-\_piece} operation describes a piece consisting
of the given number of bits whose values are undefined. If
the location is a register, the offset is from the least
\livelink{chap:DWOPbreg1}{DW\-\_OP\-\_breg1} 0 \livetarg{chap:DWOPbreg2}{DW\-\_OP\-\_breg2} 0 \livelink{chap:DWOPplus}{DW\-\_OP\-\_plus} \livelink{chap:DWOPstackvalue}{DW\-\_OP\-\_stack\-\_value}
\begin{myindentpara}{1cm}
Add the contents of r1 and r2 to compute a value. This value is the
-“contents” of an otherwise anonymous location.
+\doublequote{contents} of an otherwise anonymous location.
\end{myindentpara}
\livelink{chap:DWOPlit1}{DW\-\_OP\-\_lit1} \livelink{chap:DWOPstackvalue}{DW\-\_OP\-\_stack\-\_value} \livelink{chap:DWOPpiece}{DW\-\_OP\-\_piece} 4 \\
is common to all encodings, and means that no address class
has been specified.
-\textit {For example, the Intel386 ™ processor might use the following values:}
+\textit {For example, the Intel386 \texttrademark\ processor might use the following values:}
\begin{table}[here]
\caption{Example address class codes}
capture or freeze the value of a variable at a particular
point in the program.
\addtoindex{Ada} 95 has package elaboration routines,
-type descriptions of the form typename’Class, and
+type descriptions of the form typename\textquoteright Class, and
``access typename'' parameters. }
Generally, any debugging information
for their work, while not being considered responsible for
modifications made by others.
-This License is a kind of “copyleft”, which means that
+This License is a kind of \doublequote{copyleft}, which means that
derivative works of the document must themselves be free in
the same sense. It complements the GNU General Public License,
which is a copyleft license designed for free software.
holder saying it can be distributed under the terms of this
License. Such a notice grants a world-wide, royalty-free
license, unlimited in duration, to use that work under
-the conditions stated herein. The “Document”, below,
+the conditions stated herein. The \doublequote{Document}, below,
refers to any such manual or work. Any member of the public
-is a licensee, and is addressed as “you”. You accept the
+is a licensee, and is addressed as \doublequote{you}. You accept the
license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
-A “Modified Version” of the Document means any work
+A \doublequote{Modified Version} of the Document means any work
containing the Document or a portion of it, either copied
verbatim, or with modifications and/or translated into
another language.
-A “Secondary Section” is a named appendix or a
+A \doublequote{Secondary Section} is a named appendix or a
front-matter section of the Document that deals exclusively
with the relationship of the publishers or authors of the
-Document to the Document’s overall subject (or to related
+Document to the Document\textquoteright s overall subject (or to related
matters) and contains nothing that could fall directly
within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not
matters, or of legal, commercial, philosophical, ethical or
political position regarding them.
-The “Invariant Sections” are certain Secondary Sections
+The \doublequote{Invariant Sections} are certain Secondary Sections
whose titles are designated, as being those of Invariant
Sections, in the notice that says that the Document is
released under this License. If a section does not fit the
Invariant Sections. If the Document does not identify any
Invariant Sections then there are none.
-The “Cover Texts” are certain short passages of text
+The \doublequote{Cover Texts} are certain short passages of text
that are listed, as Front-Cover Texts or Back-Cover Texts,
in the notice that says that the Document is released under
this License. A Front-Cover Text may be at most 5 words,
and a Back-Cover Text may be at most 25 words.
-A “Transparent” copy of the Document means a
+A \doublequote{Transparent} copy of the Document means a
machine-readable copy, represented in a format whose
specification is available to the general public, that is
suitable for revising the document straightforwardly with
of markup, has been arranged to thwart or discourage subsequent
modification by readers is not Transparent. An image format is
not Transparent if used for any substantial amount of text. A
-copy that is not “Transparent” is called “Opaque”.
+copy that is not \doublequote{Transparent} is called \doublequote{Opaque}.
Examples of suitable formats for Transparent copies include
plain ASCII without markup, Texinfo input format, LaTeX
HTML, PostScript or PDF produced by some word processors for
output purposes only.
-The “Title Page” means, for a printed book, the title
+The \doublequote{Title Page} means, for a printed book, the title
page itself, plus such following pages as are needed to hold,
legibly, the material this License requires to appear in the
title page. For works in formats which do not have any title
-page as such, “Title Page” means the text near the most
-prominent appearance of the work’s title, preceding the
+page as such, \doublequote{Title Page} means the text near the most
+prominent appearance of the work\textquoteright s title, preceding the
beginning of the body of the text.
-The “publisher” means any person or entity that distributes
+The \doublequote{publisher} means any person or entity that distributes
copies of the Document to the public.
-A section “Entitled XYZ” means a named subunit of the
+A section \doublequote{Entitled XYZ} means a named subunit of the
Document whose title either is precisely XYZ or contains
XYZ in parentheses following text that translates XYZ in
another language. (Here XYZ stands for a specific section
-name mentioned below, such as “Acknowledgements”,
-“Dedications”, “Endorsements”, or “History”.) To
-“Preserve the Title” of such a section when you modify
-the Document means that it remains a section “Entitled
-XYZ” according to this definition.
+name mentioned below, such as \doublequote{Acknowledgements},
+\doublequote{Dedications}, \doublequote{Endorsements}, or \doublequote{History}.) To
+\doublequote{Preserve the Title} of such a section when you modify
+the Document means that it remains a section \doublequote{Entitled
+XYZ} according to this definition.
The Document may include Warranty Disclaimers next to
the notice which states that this License applies to the
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100,
-and the Document’s license notice requires Cover Texts,
+and the Document\textquoteright s license notice requires Cover Texts,
you must enclose the copies in covers that carry, clearly and
legibly, all these Cover Texts: Front-Cover Texts on the front
cover, and Back-Cover Texts on the back cover. Both covers
\item Preserve in that license notice the full lists of
Invariant Sections and required Cover Texts given in the
-Document’s license notice.
+Document\textquoteright s license notice.
\item Include an unaltered copy of this License.
-\item Preserve the section Entitled “History”, Preserve
+\item Preserve the section Entitled \doublequote{History}, Preserve
its Title, and add to it an item stating at least the title,
year, new authors, and publisher of the Modified Version
as given on the Title Page. If there is no section Entitled
-“History” in the Document, create one stating the title,
+\doublequote{History} in the Document, create one stating the title,
year, authors, and publisher of the Document as given on its
Title Page, then add an item describing the Modified Version
as stated in the previous sentence.
the Document for public access to a Transparent copy of the
Document, and likewise the network locations given in the
Document for previous versions it was based on. These may be
-placed in the “History” section. You may omit a network
+placed in the \doublequote{History} section. You may omit a network
location for a work that was published at least four years
before the Document itself, or if the original publisher of
the version it refers to gives permission.
-\item For any section Entitled “Acknowledgements”
-or “Dedications”, Preserve the Title of the section,
+\item For any section Entitled \doublequote{Acknowledgements}
+or \doublequote{Dedications}, Preserve the Title of the section,
and preserve in the section all the substance and tone of
each of the contributor acknowledgements and/or dedications
given therein.
unaltered in their text and in their titles. Section numbers or
the equivalent are not considered part of the section titles.
-\item Delete any section Entitled “Endorsements”. Such
+\item Delete any section Entitled \doublequote{Endorsements}. Such
a section may not be included in the Modified Version.
\item Do not retitle any existing section to be Entitled
-“Endorsements” or to conflict in title with any Invariant
+\doublequote{Endorsements} or to conflict in title with any Invariant
Section.
\item Preserve any Warranty Disclaimers.
no material copied from the Document, you may at your option
designate some or all of these sections as invariant. To do
this, add their titles to the list of Invariant Sections in
-the Modified Version’s license notice. These titles must
+the Modified Version\textquoteright s license notice. These titles must
be distinct from any other section titles.
-You may add a section Entitled “Endorsements”, provided
+You may add a section Entitled \doublequote{Endorsements}, provided
it contains nothing but endorsements of your Modified Version
-by various parties—for example, statements of peer review
+by various parties\textemdash for example, statements of peer review
or that the text has been approved by an organization as the
authoritative definition of a standard.
the license notice of the combined work.
In the combination, you must combine any sections Entitled
-“History” in the various original documents, forming
-one section Entitled “History”; likewise combine any
-sections Entitled “Acknowledgements”, and any sections
-Entitled “Dedications”. You must delete all sections
-Entitled “Endorsements.”
+\doublequote{History} in the various original documents, forming
+one section Entitled \doublequote{History}; likewise combine any
+sections Entitled \doublequote{Acknowledgements}, and any sections
+Entitled \doublequote{Dedications}. You must delete all sections
+Entitled \doublequote{Endorsements.}
\section{COLLECTIONS OF DOCUMENTS}
A compilation of the Document or its derivatives with
other separate and independent documents or works, in
or on a volume of a storage or distribution medium, is
-called an “aggregate” if the copyright resulting from
+called an \doublequote{aggregate} if the copyright resulting from
the compilation is not used to limit the legal rights of
-the compilation’s users beyond what the individual works
+the compilation\textquoteright s users beyond what the individual works
permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate
which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to
these copies of the Document, then if the Document is less
-than one half of the entire aggregate, the Document’s Cover
+than one half of the entire aggregate, the Document\textquoteright s Cover
Texts may be placed on covers that bracket the Document within
the aggregate, or the electronic equivalent of covers if the
Document is in electronic form. Otherwise they must appear
version will prevail.
If a section in the Document is Entitled
-“Acknowledgements”, “Dedications”, or “History”,
+\doublequote{Acknowledgements}, \doublequote{Dedications}, or \doublequote{History},
the requirement (section 4) to Preserve its Title (section 1)
will typically require changing the actual title.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
-version of this License “or any later version” applies to
+version of this License \doublequote{or any later version} applies to
it, you have the option of following the terms and conditions
either of that specified version or of any later version
that has been published (not as a draft) by the Free Software
of this License, you may choose any version ever published
(not as a draft) by the Free Software Foundation. If the
Document specifies that a proxy can decide which future
-versions of this License can be used, that proxy’s public
+versions of this License can be used, that proxy\textquoteright s public
statement of acceptance of a version permanently authorizes
you to choose that version for the Document.
\section{RELICENSING}
-“Massive Multiauthor Collaboration Site” (or “MMC
-Site”) means any World Wide Web server that publishes
+\doublequote{Massive Multiauthor Collaboration Site} (or \doublequote{MMC
+Site}) means any World Wide Web server that publishes
copyrightable works and also provides prominent facilities for
anybody to edit those works. A public wiki that anybody can
-edit is an example of such a server. A “Massive Multiauthor
-Collaboration” (or “MMC”) contained in the site means
+edit is an example of such a server. A \doublequote{Massive Multiauthor
+Collaboration} (or \doublequote{MMC}) contained in the site means
any set of copyrightable works thus published on the MMC site.
-“CC-BY-SA” means the Creative Commons Attribution-Share
+\doublequote{CC-BY-SA} means the Creative Commons Attribution-Share
Alike 3.0 license published by Creative Commons Corporation, a
not-for-profit corporation with a principal place of business
in San Francisco, California, as well as future copyleft
versions of that license published by that same organization.
-“Incorporate” means to publish or republish a Document,
+\doublequote{Incorporate} means to publish or republish a Document,
in whole or in part, as part of another Document.
-An MMC is “eligible for relicensing” if it is licensed
+An MMC is \doublequote{eligible for relicensing} if it is licensed
under this License, and if all works that were first
published under this License somewhere other than this MMC,
and subsequently incorporated in whole or in part into the
\end{myindentpara}
If you have Invariant Sections, Front-Cover Texts and
-Back-Cover Texts, replace the “with…Texts.” line
+Back-Cover Texts, replace the \doublequote{with\dots Texts.} line
with this:
object file section called
\addtoindex{.debug\_aranges}. The table consists
of sets of variable length entries, each set describing the
-portion of the program’s address space that is covered by
+portion of the program\textquoteright s address space that is covered by
a single compilation unit.
Each set begins with a header containing five values:
\item \textbf{DW\-\_LNE\-\_end\-\_sequence} \\
The \livetarg{chap:DWLNEendsequence}{DW\-\_LNE\-\_end\-\_sequence} opcode takes no operands. It sets the
\addtoindex{end\_sequence}
-register of the state machine to “true” and
+register of the state machine to \doublequote{true} and
appends a row to the matrix using the current values of the
state-machine registers. Then it resets the registers to the
initial values specified above
given compilation unit is represented in the
\addtoindex{.debug\_macinfo}
section of an object file. The macro information for each
-compilation unit is represented as a series of “macinfo”
-entries. Each macinfo entry consists of a “type code” and
+compilation unit is represented as a series of \doublequote{macinfo}
+entries. Each macinfo entry consists of a \doublequote{type code} and
up to two additional operands. The series of entries for a
given compilation unit ends with an entry containing a type
code of 0.
saves the value that the register had at entry time in its call
frame and restores it on exit. The code that allocates space
on the call frame stack and performs the save operation is
-called the subroutine’s \addtoindex{prologue}, and the code that performs
+called the subroutine\textquoteright s \addtoindex{prologue}, and the code that performs
the restore operation and deallocates the frame is called its
\addtoindex{epilogue}. Typically, the
\addtoindex{prologue} code is physically at the
it finds the activation of interest. A debugger unwinds
a stack in steps. Starting with the current activation it
virtually restores any registers that were preserved by the
-current activation and computes the predecessor’s CFA and
+current activation and computes the predecessor\textquoteright s CFA and
code location. This has the logical effect of returning from
the current subroutine to its predecessor. We say that the
debugger virtually unwinds the stack because the actual state
of the target process is unchanged.}
\textit{The unwinding operation needs to know where registers are
-saved and how to compute the predecessor’s CFA and code
+saved and how to compute the predecessor\textquoteright s CFA and code
location. When considering an architecture-independent way
of encoding this information one has to consider a number of
special things.}
The \livetarg{chap:DWCFAadvanceloc}{DW\-\_CFA\-\_advanceloc} instruction takes a single operand (encoded
with the opcode) that represents a constant delta. The required
action is to create a new table row with a location value that
-is computed by taking the current entry’s location value
+is computed by taking the current entry\textquoteright s location value
and adding the value of
\textit{delta * \addtoindex{code\_alignment\_factor}}.
All
\item \textit{Initialize a register set by reading the
initial\_instructions field of the associated CIE.}
-\item \textit{Read and process the FDE’s instruction
+\item \textit{Read and process the FDE\textquoteright s instruction
sequence until a \livelink{chap:DWCFAadvanceloc}{DW\-\_CFA\-\_advance\-\_loc},
\livelink{chap:DWCFAsetloc}{DW\-\_CFA\-\_set\-\_loc}, or the
end of the instruction stream is encountered.}
which is used
to specify and provide a user\dash specified name for the main
subroutine of a program.
-\addtoindex{C} uses the name “main” to identify
+\addtoindex{C} uses the name \doublequote{main} to identify
the main subprogram of a program. Some other languages provide
similar or other means to identify the main subprogram of
a program.}
\textit{An imported unit entry does not necessarily correspond to
any entity or construct in the source program. It is merely
-“glue” used to relate a partial unit, or a compilation
+\doublequote{glue} used to relate a partial unit, or a compilation
unit used as a partial unit, to a place in some other
compilation unit.}
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
-is the actual constant value of the module’s priority,
+is the actual constant value of the module\textquoteright s priority,
represented as it would be on the target architecture.
\subsection{Namespace Entries}
\textit{A \addtoindex{Fortran} use statement
\addtoindexx{Fortran!use statement}
-with a “rename list” may be
+with a \doublequote{rename list} may be
represented by an imported module entry with an import
attribute referring to the module and owned entries
corresponding to those entities that are renamed as part of
\textit{A \addtoindex{Fortran} use statement
\addtoindexx{Fortran!use statement}
-with neither a “rename list” nor
-an “only list” may be represented by an imported module
+with neither a \doublequote{rename list} nor
+an \doublequote{only list} may be represented by an imported module
entry with an import attribute referring to the module and
no owned child entries.
}
-\textit{A use statement with an “only list” is represented by a
+\textit{A use statement with an \doublequote{only list} is represented by a
series of individual imported declaration entries as described
in Section \refersec{chap:importedorrenameddeclarationentries}.
}
\addtoindexx{frame base attribute}
a
\livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} attribute, whose value is a location
-description that computes the “frame base” for the
+description that computes the \doublequote{frame base} for the
subroutine or entry point. If the location description is
a simple register location description, the given register
contains the frame base address. If the location description is
\textit{The frame base for a procedure is typically an address fixed
relative to the first unit of storage allocated for the
-procedure’s stack frame. The \livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} attribute
+procedure\textquoteright s stack frame. The \livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} attribute
can be used in several ways:}
\begin{enumerate}[1.]
\item \textit{In procedures that need
\addtoindexx{location list}
location lists to locate local
variables, the \livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} can hold the needed location
-list, while all variables’ location descriptions can be
+list, while all variables\textquoteright\ location descriptions can be
simpler ones involving the frame base.}
\item \textit{It can be used in resolving ``up\dash level'' addressing
\item The computed value should be unique among instances of
the same subroutine. (For typical \livelink{chap:DWATframebase}{DW\-\_AT\-\_frame\-\_base} use, this
-means that a recursive subroutine’s stack frame must have
+means that a recursive subroutine\textquoteright s stack frame must have
non\dash zero size.)
\end{enumerate}
\textit{For example, the
\addtoindex{C} type int on a machine that uses 32\dash bit
integers is represented by a base type entry with a name
-attribute whose value is “int”, an encoding attribute
+attribute whose value is \doublequote{int}, an encoding attribute
whose value is \livelink{chap:DWATEsigned}{DW\-\_ATE\-\_signed}
and a byte size attribute whose value is 4.}
ISO/IEC 10646\dash 1:1993). For example, the
\addtoindex{C++} type char16\_t is
represented by a base type entry with a name attribute whose
-value is “char16\_t”, an encoding attribute whose value
+value is \doublequote{char16\_t}, an encoding attribute whose value
is \livelink{chap:DWATEUTF}{DW\-\_ATE\-\_UTF} and a byte size attribute whose value is 2.}
The
appropriately in different languages. For example, in
\addtoindex{C} and \addtoindex{C++}
the language implementation can provide an unspecified type
-entry with the name “void” which can be referenced by the
+entry with the name \doublequote{void} which can be referenced by the
type attribute of pointer types and typedef declarations for
'void' (see
% FIXME: the following reference was wrong in DW4 so DavidA guessed
\livelink{chap:DWATcount}{DW\-\_AT\-\_count} attribute
\addtoindexx{count attribute}
whose value is a constant expressing the blocksize of the
-type. If no count attribute is present, then the “infinite”
+type. If no count attribute is present, then the \doublequote{infinite}
blocksize is assumed.
When multiple type modifiers are chained together to modify
first, next to leftmost second, and so on).
\textit{In languages, such as C, in which there is no concept of
-a “multidimensional array”, an array of arrays may
+a \doublequote{multidimensional array}, an array of arrays may
be represented by a debugging information entry for a
multidimensional array.}
\addtoindexx{structure type entry}
components.
In \addtoindex{C} and \addtoindex{C++}, these collections are called
-“structures.”
-In \addtoindex{Pascal}, they are called “records.”
+\doublequote{structures.}
+In \addtoindex{Pascal}, they are called \doublequote{records.}
The components may be of different types. The components are
-called “members” in \addtoindex{C} and
-\addtoindex{C++}, and “fields” in \addtoindex{Pascal}.}
+called \doublequote{members} in \addtoindex{C} and
+\addtoindex{C++}, and \doublequote{fields} in \addtoindex{Pascal}.}
\textit{The components of these collections each exist in their
own space in computer memory. The components of a C or C++
-“union” all coexist in the same memory.}
+\doublequote{union} all coexist in the same memory.}
\textit{\addtoindex{Pascal} and
-other languages have a “discriminated union,”
+other languages have a \doublequote{discriminated union,}
\addtoindex{discriminated union|see {variant entry}}
-also called a “variant record.” Here, selection of a
-number of alternative substructures (“variants”) is based
+also called a \doublequote{variant record.} Here, selection of a
+number of alternative substructures (\doublequote{variants}) is based
on the value of a component that is not part of any of those
-substructures (the “discriminant”).}
+substructures (the \doublequote{discriminant}).}
\textit{\addtoindex{C++} and
\addtoindex{Java} have the notion of ``class'', which is in some
-ways similar to a structure. A class may have “member
-functions” which are subroutines that are within the scope
+ways similar to a structure. A class may have \doublequote{member
+functions} which are subroutines that are within the scope
of a class or structure.}
\textit{The \addtoindex{C++} notion of
\addtoindexx{data member|see {member entry (data)}}
member declarations occurring within
the declaration of a structure, union or class type are
-considered to be “definitions” of those members, with
-the exception of “static” data members, whose definitions
+considered to be \doublequote{definitions} of those members, with
+the exception of \doublequote{static} data members, whose definitions
appear outside of the declaration of the enclosing structure,
union or class type. Function member declarations appearing
within a structure, union or class type declaration are
a ``level\dash 88 condition'' that
associates a data item, called the conditional variable, with
a set of one or more constant values and/or value ranges.
-Semantically, the condition is ‛true’ if the conditional
+Semantically, the condition is \textquoteleft true\textquoteright if the conditional
variable's value matches any of the described constants,
-and the condition is ‛false’ otherwise.}
+and the condition is \textquoteleft false\textquoteright otherwise.}
The \livetarg{chap:DWTAGcondition}{DW\-\_TAG\-\_condition}
debugging information entry\addtoindexx{condition entry}
describes a
-logical condition that tests whether a given data item’s
+logical condition that tests whether a given data item\textquoteright s
value matches one of a set of constant values. If a name
has been given to the condition, the condition entry has a
\livelink{chap:DWATname}{DW\-\_AT\-\_name} attribute
the parent
entry has an array type, the condition can test any individual
element, but not the array as a whole. The condition entry
-implicitly specifies a “comparison type” that is the
+implicitly specifies a \doublequote{comparison type} that is the
type of an array element if the parent has an array type;
otherwise it is the type of the parent entry.
a \livelink{chap:DWATtype}{DW\-\_AT\-\_type} attribute,
that attribute should describe a type
compatible with the comparison type (according to the source
-language); otherwise the child’s type is the same as the
+language); otherwise the child\textquoteright s type is the same as the
comparison type.
\textit{For conditional variables with alphanumeric types, COBOL
\section{Enumeration Type Entries}
\label{chap:enumerationtypeentries}
-\textit{An “enumeration type” is a scalar that can assume one of
+\textit{An \doublequote{enumeration type} is a scalar that can assume one of
a fixed number of symbolic values.}
An enumeration type is represented by a debugging information
\section{Set Type Entries}
\label{chap:settypeentries}
-\textit{\addtoindex{Pascal} provides the concept of a “set,” which represents
+\textit{\addtoindex{Pascal} provides the concept of a \doublequote{set,} which represents
a group of values of ordinal type.}
A set is represented by a debugging information entry with
DWARF Git Projects / dwarf-doc.git / commitdiff